Minimal Deployment in ASP.Net

Is it possible to do minimal deployment so that there would be minimum interference the solution ... in order to explain it better rather then deploying whole solution only one part can be deployed using .Net Framework 2.0 / 3.0 and Visual Studio 2010

Is it feasible? if feasible then what could be the best way to achieve this?

Hai Vivek,If you already deployed the solution earlier then you don't need to re=deploy whole solution again, instead, you can deploy on the part which got modified.Let's say, if there is some changes in the class library project, then you just need to build the class library and replace its .dll with the deployment folder.If you have made some UI changes like in .aspx or in .cshtml, just replace that file to the deployment server as it will not affect other functionality.But make sure, that it is not affecting other things. Like if you create an additional method in the Data Access layer or in Model and then you are calling it from the Business Logic layer or from controller then you need to replace all those files or dll's which got modified otherwise the solution will not work.Hope it will be helpful to you.Regards,Pawan Awasthi(DNS MVM)+91 8123489140 (whatsApp), +60 14365 1476(Malaysia)pawansoftit@gmail.com

Thanks Pawan, We are not using MVC architecture but its traditional web form architecture multi layer/tier.

Like the it happened, any change in DAL and BAL will create only 1 DLL per BAL and DALAny change in code behind of Aspx will create only one DLL corresponding to presentation as its web application...

Let's say, if there is some changes in the class library project, then you just need to build the class library and replace its .dll with the deployment folder.If you have made some UI changes like in .aspx or in .cshtml, just replace that file to the deployment server as it will not affect other functionality.But make sure, that it is not affecting other things. Like if you create an additional method in the Data Access layer or in Model and then you are calling it from the Business Logic layer or from controller then you need to replace all those files or dll's which got modified otherwise the solution will not work.

If there is any changes in your dll then only you need to redeploy other wise no need to deploy all the solutions, check your code base if it is really changes happen then you should redeploy without redeploy the latest changes are not reflected in your production.--------------------------------------------------------------------------------Give respect to your work, Instead of trying to impress your boss.