Last post Apr 28, 2014 11:22 PM by Starain chen - MSFT
Apr 27, 2014 11:32 PM|JDEIntegrator|LINK
I found a similar post here (http://tinyurl.com/forum20392), and I think the most important question is from johnjohn123123 was "you mean to
republish the whole application ?". I complety understand the controller class is going to be embedded on an resulting assembly (dll), but in the case that web application has been decouple on a series of dlls let's say per module (profile.dll / security.dll
/ shopping.dll, etc), and a bug was found and fixed on security.dll assembly for instance, then best scenario is to be able to deploy the modified dll only, in order to reduce the QA process and have a better control of changes. So, my question is: Is there
a mechanism to deploy modified objects only via Web Deployment Package?
Apr 28, 2014 11:22 PM|Starain chen - MSFT|LINK
In my opinion, you should deploy the whole project. Because, the main application should be combined with the newer files (E.g. security.dll reference)
but in the case that web application has been decouple on a series of dlls let's say per module
I think they aren’t decouple. For that scenario, I think you’d better to use the WCF to decouple.
After that, you just need to deploy the WCF project if you change some logic.
If you change the interface of WCF, you need to update the reference and should redeploy the main application.