Deploying .NET components (upgrade the component for only a single client application)
Posted
by Vytas999
on Stack Overflow
See other posts from Stack Overflow
or by Vytas999
Published on 2010-03-31T10:42:15Z
Indexed on
2010/03/31
10:53 UTC
Read the original article
Hit count: 264
I use Visual Studio .NET to create a component that will be shared by two client applications. Eventually, I plan to deploy new version of this component. However, not all of the new versions will be compatible with both client applications. When I deploy component and the client applications, I must ensure that I can upgrade the component for a single client application. I must also minimize the need for configuration changes when I deploy new version of the component. What are possible ways to achieve this goal?
© Stack Overflow or respective owner