D
Derek Martin
Hi list, I have been doing VB.Net for quite a while now and just now getting
into the forray of ASP.Net using VS2003. I have created our development
website and now we are ready to start putting it into production.
I've messed around with a few different deployment scenarios but the one we
ended up with was two copies of the code, one on dev and one on prod and all
changes we make to code on dev have to be copied to the prod and then
recompiled - this seems dumb to me, and perhaps it is. To make matters
slightly more complex, the API behind the ASP.Net app (dll) is using delay
signing on our strong name key, which means, any time I build to go into
production, I have to re-final sign.
So, I was wondering if anyone could offer some suggestions on best practices
to make this process a little easier - I haven't tried it, but it'd be great
if I could do the release build on dev, final sign and then simply copy the
files over to production using a shared network drive as an intermediary.
Thanks all!
Derek
into the forray of ASP.Net using VS2003. I have created our development
website and now we are ready to start putting it into production.
I've messed around with a few different deployment scenarios but the one we
ended up with was two copies of the code, one on dev and one on prod and all
changes we make to code on dev have to be copied to the prod and then
recompiled - this seems dumb to me, and perhaps it is. To make matters
slightly more complex, the API behind the ASP.Net app (dll) is using delay
signing on our strong name key, which means, any time I build to go into
production, I have to re-final sign.
So, I was wondering if anyone could offer some suggestions on best practices
to make this process a little easier - I haven't tried it, but it'd be great
if I could do the release build on dev, final sign and then simply copy the
files over to production using a shared network drive as an intermediary.
Thanks all!
Derek