I just need to verify that I am doing the right thing. In my deployment project,
- non updatable
- merge all outputs into a single assembly caled "FOO"
I copied over the entire folder structure to the server the very first time after running the web deployment project.
Now when I have updates,
1) If I make a change to one single existing ASPX and it's codebehind, am I correct that with an update, I would only have to copy the FOO.DLL and the one *.compiled file for that aspx page? Or would I have to copy all the project's \bin\*.compiled files
and the FOO.DLL
For example, I have page1.aspx and page1dll. I am assuming I only have to copy over page1.*.compiled and FOO.DLL because the site is non-updatable. The previous page1.aspx file as is only a marker file. Are there there other files I have to copy over?
2) If I only change the web.config files, I only have to copy over the web.config AND the precompiled.config correct?
vamail2
Member
15 Points
4 Posts
Deploy files when code or UI changes?
Jun 12, 2006 06:51 PM|LINK
I just need to verify that I am doing the right thing. In my deployment project,
- non updatable
- merge all outputs into a single assembly caled "FOO"
I copied over the entire folder structure to the server the very first time after running the web deployment project.
Now when I have updates,
1) If I make a change to one single existing ASPX and it's codebehind, am I correct that with an update, I would only have to copy the FOO.DLL and the one *.compiled file for that aspx page? Or would I have to copy all the project's \bin\*.compiled files and the FOO.DLL
For example, I have page1.aspx and page1dll. I am assuming I only have to copy over page1.*.compiled and FOO.DLL because the site is non-updatable. The previous page1.aspx file as is only a marker file. Are there there other files I have to copy over?
2) If I only change the web.config files, I only have to copy over the web.config AND the precompiled.config correct?
Thanks for any help