Last post Sep 05, 2016 01:55 PM by PatriceSc
Sep 04, 2016 09:31 AM|vivek_cs|LINK
Is it possible to do minimal deployment of Web form (multi tier) 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
Usually we deploy DLL related to Web application after publishing let say 1 dll for DAL, 1 for BAL and 1 for Presentation along with aspx files as this is web application.
Problem area is that as the solution is quite big with respect to 12 different modules which has been developed from last 10 years..
Pain Area 1. any small change in one module usually impact whole web site and then rigorous testing is required for all the modules as most of the times other modules used to break.
Pain Area 2: As using distributed deployment, there is no central deployment, solution need to be deployed at n no of places, given the magnitude, deployment and testing become painful.
So client is looking for the way as if there would be any change in one part of module then it would not impact other modules.. then only one module need to be deployed... or something similar which restrain and provide solution to both pain areas
Is it feasible? if feasible then what could be the best way to achieve this?
Sep 04, 2016 01:13 PM|HostingASPNet|LINK
You could use Publish Web site option, in this way the site will be precompiled and you will not publish the code behind files. If you need only part of some solution, you could create another solution only with it.
Sep 04, 2016 03:28 PM|vivek_cs|LINK
I am using publishing feature from last 8 -10 years.
Is it possible to deploy Visual Studio 2010 Web Application Solution... with minimum code base.. minimize dependencies... I mean let say if there would be Presentation Layer / BAL/ DAL then each part can be modularized within..
Deployment is very troublesome and painful as its impacting client due to due to distributed deployment at multiple locations for each small change
Its Deployment is very troublesome and painful due to distributed deployment at multiple locations for each small change
BAL - Module 1 BAL, Module 2 BAL.... i.e. each having its own DLL so that we don't need to disturb whole BAL at the time of deployment
DAL - Module 1 DAL, Module 2 DAL... i.e. each having its own DLL so that we don't need to disturb whole DAL at the time of deployment
Is it possible like this or other best way to bifurcate so that whole BAL, DAL as well as Presentation DLLs would not be impacted
Kindly suggest some workable solution which would work through Visual Studio or through existing solution... or any good suggestion would be really appreciated....
Sep 04, 2016 06:51 PM|PatriceSc|LINK
If it is compiled into multiple DLLs you could just copy the DLL file (using copy/robocopy etc...). Publishing is the easy no brainer option but you are not forced to use only that.
Unless you are 100% sure you analyzed your current issue currently, you may want to post about the problem rather than about a solution you thought about. You may have other options.
Not sure if the problem is that you have multiple sites on a single physical machine, or on multiple machines or already multiple tiers on distinct machines etc... but you may have some solution that could help maybe with your current design (file replications,
Sep 05, 2016 03:33 AM|vivek_cs|LINK
Sep 05, 2016 01:55 PM|PatriceSc|LINK
#1 You can break sometimes but if it breaks on a regular basis it seems you have a problem to solve even before the deployment step.
#2 Still a bit unclear WHY it is painful. What do you do beyond copying files? Is it done manually? You are shipping this to your client and he installs that or do you deploy on your own servers?
For now I would say:
- don't start from a blank page. See which problems you had, what caused them and how you could have avoided them. Don't try to solve them all at once especially if you really have numerous troubles.
- not sure what is the current situation. If they are really separate modules maybe you could handle them as such (for example having multiple mysite.com/modulename web sites ?). It is also possible to compile a single solution into multiple DLLs (we used a
batch file to do that) and so we were able to deploy that separately
- you have also MVC areas (it's MVC but it might worth a try to see how ASPX pages are handled inside an MVC area, I never tried to see how it behaves on my side)
- you have tools such as robocopy, msdeploy, file replication, dfs etc... and whole release management systems to automate your deployments and maybe reduce the number of issues you'll encounter during that step
- you could also use services etc.. maybe rather than sharing DLLs ?
Beyond a technical solution, make sure first to fully understand and analyze what caused those issues maybe starting with why changing a module breaks other modules (shared code changes, db schema change,, or some other unexpected failure, would versioning
help etc... etc...)