By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,422 Members | 1,323 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,422 IT Pros & Developers. It's quick & easy.

from staging to production

P: n/a
rom
what do i have to more from staging to production every
time i make changes? all the files only? what about the
dll in the bin directory? if i copy the dll file do i also
have to copy the aspx and aspx.vb files?

thanks.
Nov 19 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
rom wrote:
what do i have to more from staging to production every
time i make changes? all the files only? what about the
dll in the bin directory? if i copy the dll file do i also
have to copy the aspx and aspx.vb files?

thanks.


If the change is just in an aspx (or ascx, or config file)
then you can copy just that file.
If the change is in code(-behind) then you need to copy
the compiled dll. You do *not* need to copy .vb (or .cs) files.

Hans Kesting
Nov 19 '05 #2

P: n/a
"rom" <me****@ifat.com> wrote in message
news:08****************************@phx.gbl...
what do i have to more from staging to production every
time i make changes? all the files only? what about the
dll in the bin directory? if i copy the dll file do i also
have to copy the aspx and aspx.vb files?


If you're using Visual Studio.NET, you can use the Project->Copy Project
command, which has an option to only copy the files needed for the
application. I often use this command to copy to a dummy location, then
deploy the files from the dummy location to the staging or production
server.

John Saunders
Nov 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.