This post originated from an RSS feed registered with .NET Buzz
by Paschal.
Original Post: Multi projects and deployment
Feed Title: help.net
Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/pleloup/Rss.aspx
Feed Description: .Net for mankind !
If I have to define a wish list wish for the next release Whidbey I would like surely to add this.
I have a web project A deployed on a production server. After few months of good services, the site needed some new features and improvements.
So I deployed another project A on another development server B to implement and test the changes.
The difficulty here is the site A in production must continue its life cycle with daily updates.
So I am stuck here by the fact that I can't have on my development machine twice the same project using the same name, for two different servers.
Of course I can change the name on the server B, but when I would like to put it in production, I will have a lot of issues with page inheritance because they refer to B and not A.
On my development PC, obviously my local IIS don't let me having twice the same name
So the solution could be something like:
Development: Test: Production:
Project A ------------------------------------------------[
Project A
Project B(copy of A)--------[ Project A ------------------[
The new project A obviously should be release on production after approval on the test platform.
IMHO I think the Copy Project button should be improve. I know that the notion of Project doesn't exist anymore on Whidbey, and maybe refactoring can also be an idea to dig.
But is it possible to make it simpler ?
I think this is one thing I dislike in the current VS version, the lack of global deployment environment. I would like to declare a set of servers rather than deploying to one machine at a time. I mean something to let me deploy the projects for test or production, VS knowing the details of my network.
Maybe the notion of relational links between the servers can also be a way to explore.
Previous Topic
