Upgrading to a precompiled site

I have .NET 2.0, a precompiled and deployed website. I decompiled the site and added new functionality to the "dev branch" of the site. Now I need to upgrade the site to .NET 3.5 so that new functions can function and add new functions to the "production" site.

How can I combine this merging of functions on the production site? I have several C # classes, new pages and unrelated source code for existing pages.

+3
source share
3 answers

It is best to deploy a decompiled site under 3.5, but save most files with a decompiled version 2.0 and, above all, replace web.config with version 3.5. web.config rarely affects the maintenance of regular (aspx) pages, so replacing it with 3.5 will have very little effect.

0
source

If you recompile new features and thus get a new precompiled site running the new version of .Net, there will be nothing to merge if you do not complete the deployment, but if you do not complete the deployment, how can you upgrade to the new version .Net?

+1
source

Why not just recompile the entire site in .NET 3.5, install 3.5 runtimes on your target site, and just reinstall the new version 3.5 of your site?

0
source

Source: https://habr.com/ru/post/1708447/


All Articles