Z
z. f.
Hi,
I have a deployment question for a migration from ASP to ASP.NET.
the application is an e-commerce web-site that have loadbalancing of 4 web
servers running (today) windows2000 with IIS5 and will run windows2003
server in the future.
3 developers working on the web app, and today when needs to change
something copying the relevant asp page from dev env to production.
when we migrate to asp.net, the development environment of a development
server, like in ASP might cause problems: when changing a page by one
developer, the app might not compile to reflect changes made by other
developer.
so we can work locally each developer, is this the only way?
should I separate the application to several DLLs for deployment reasons?
any information learned from experience of working on live e-commerce web
application in dot-net will help.
TIA,
z.
I have a deployment question for a migration from ASP to ASP.NET.
the application is an e-commerce web-site that have loadbalancing of 4 web
servers running (today) windows2000 with IIS5 and will run windows2003
server in the future.
3 developers working on the web app, and today when needs to change
something copying the relevant asp page from dev env to production.
when we migrate to asp.net, the development environment of a development
server, like in ASP might cause problems: when changing a page by one
developer, the app might not compile to reflect changes made by other
developer.
so we can work locally each developer, is this the only way?
should I separate the application to several DLLs for deployment reasons?
any information learned from experience of working on live e-commerce web
application in dot-net will help.
TIA,
z.