From our very successful webinar last week, over next few days, I'll post some of the questions and my answers that were asked by the attendees. If you have any follow-up questions, just drop me a note Question: If the provider install is responsible for updating machine.config, does that mean if we embed a provider in our application that our installer will now need to be responsible for updating the file? Answer: Actually, the installer holds the responsibility of modifying the machine.config file. There are, however a number of strategies each of which provider a reasonable path forward. If you are not coding to the common layer and not loading the provider via provider factories, the machine.config file does not play a role, so it can be safely ignored. If you are packaging the providers, you application is not required to modify the machine.config file. However, for many developers they already enjoy the common coding layer, so it
View all posts from Jonathan Bruce on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Let our experts teach you how to use Sitefinity's best-in-class features to deliver compelling digital experiences.Learn More
Subscribe to get all the news, info and tutorials you need to build better business apps and sites
You can also ask us not to share your Personal Information to third parties here: Do Not Sell or Share My Info
We see that you have already chosen to receive marketing materials from us. If you wish to change this at any time you may do so by clicking here.
Thank you for your continued interest in Progress. Based on either your previous activity on our websites or our ongoing relationship, we will keep you updated on our products, solutions, services, company news and events. If you decide that you want to be removed from our mailing lists at any time, you can change your contact preferences by clicking here.