468,765 Members | 1,598 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,765 developers. It's quick & easy.

Best Practices Question...

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
Nov 19 '05 #1
3 1071
Why would you have to recompile? Just copy the DLLs and related changes over
to the production server.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.

"Derek Martin" <dm*****@DONTSPAMMEokstateDOT.edu> wrote in message
news:Oy**************@TK2MSFTNGP15.phx.gbl...
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

Nov 19 '05 #2
Hey Kevin, that's a very good question, one I have been asking myself
frequently these past few weeks. I suppose that I wouldn't and that would
actually save quite a bit of hassle because the code behind was chaning
(long story) in the move.

I will attempt the copy - that's be so freaking sweet if that worked!

Also, another question, if the DLL file that I have as an API is delay
signed, will the website code behind DLL file also need to be delay signed
and then final signed?

Thanks
Derek

"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:Ow**************@TK2MSFTNGP11.phx.gbl...
Why would you have to recompile? Just copy the DLLs and related changes
over to the production server.

--
HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
Neither a follower nor a lender be.

"Derek Martin" <dm*****@DONTSPAMMEokstateDOT.edu> wrote in message
news:Oy**************@TK2MSFTNGP15.phx.gbl...
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


Nov 19 '05 #3
Hi Derek,

X_Copy Deployment - one of the pillaras of .Net!
Also, another question, if the DLL file that I have as an API is delay
signed, will the website code behind DLL file also need to be delay signed
and then final signed?
That I don't know. I've never had to sign a DLL.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.

"Derek Martin" <dm*****@DONTSPAMMEokstateDOT.edu> wrote in message
news:u4**************@TK2MSFTNGP14.phx.gbl... Hey Kevin, that's a very good question, one I have been asking myself
frequently these past few weeks. I suppose that I wouldn't and that would
actually save quite a bit of hassle because the code behind was chaning
(long story) in the move.

I will attempt the copy - that's be so freaking sweet if that worked!

Also, another question, if the DLL file that I have as an API is delay
signed, will the website code behind DLL file also need to be delay signed
and then final signed?

Thanks
Derek

"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:Ow**************@TK2MSFTNGP11.phx.gbl...
Why would you have to recompile? Just copy the DLLs and related changes
over to the production server.

--
HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
Neither a follower nor a lender be.

"Derek Martin" <dm*****@DONTSPAMMEokstateDOT.edu> wrote in message
news:Oy**************@TK2MSFTNGP15.phx.gbl...
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



Nov 19 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

136 posts views Thread by Matt Kruse | last post: by
13 posts views Thread by john doe | last post: by
1 post views Thread by Vincent V | last post: by
10 posts views Thread by jojobar | last post: by
8 posts views Thread by SStory | last post: by
15 posts views Thread by Andrew Brampton | last post: by
17 posts views Thread by 2005 | last post: by
41 posts views Thread by Jim | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by Marin | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.