Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Build, protect and deploy apps across any platform and mobile device
Automate decision processes with a no-code business rules engine
A complete cloud platform for an app or your entire digital business
Deploy automated machine learning to accurately predict machine failures with technology optimized for Industrial IoT.
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
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.
Copyright © 2017 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.