How to properly move an ASP.NET website to a VS2013 website project or website application?

I am looking for how to properly move an ASP.NET website to a VS2013 website project or website application?

Thanks,
Andrew
AhelblingAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Miguel OzSoftware EngineerCommented:
My suggestion is to move to VS 2013 website project, the pro/cons are explained here:
https://msdn.microsoft.com/en-us/library/dd547590(v=vs.110).aspx

Regarding migrating to VS2013, it depends  how the security is setup and also how old is your site,(e.g. pre .NET 2.0??), For a realtive new site (VS 2008/2010) my suggestion will be:
1. Create a new VS 2013 website project with the correct security defaults.
2. Check that default libraries (versions) are compatible with your current code base. Not only .NET but also say Jquery.
3. Add any third party libraries (C#, JS, CSS that you use in your site
4. Move all your files to your new project. This is the tricky part when versioning becomes an issue and you need to evaluate whe
5. Compile and build.
6. Troubleshoot and update any issues found in 5.

Assumption: You must do a code audit to determine what versions of C#, JS, CSS etc. you are using and identify any dependencies. If you have not done it before a consultant will be needed as it is a big project. Some projects could be upgraded directly but VS upgrade is not that clever to update all dependencies and you may miss the new enhancements.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
AhelblingAuthor Commented:
Thanks.  Do I move all files AND folders?  Web.config too?

ss
0
Miguel OzSoftware EngineerCommented:
Only files and folders. Web config contents have to be merged, so you can benefit from the new references tools that comes with it, please check link below for more details:
https://msdn.microsoft.com/en-us/library/aa983476.aspx
0
JavaScript Best Practices

Save hours in development time and avoid common mistakes by learning the best practices to use for JavaScript.

Dirk StraussSenior Full Stack DeveloperCommented:
In what version of Visual Studio was this ASP.NET Website created? The new Web project will also need the web.config file.
0
AhelblingAuthor Commented:
The website was built using vs2013 and I will be using vs2013 to create the project as well.
0
Miguel OzSoftware EngineerCommented:
In that case, the link I sent you in my previous comment is fully relevant. It is an step by step procedure on how to do it, but as always they do not take in account every possible scenario, thus the reason to to a third party/feature code audit before conversion starts
https://msdn.microsoft.com/en-us/library/aa983476.aspx
0
Dirk StraussSenior Full Stack DeveloperCommented:
Miguel's solution was very well researched.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ASP.NET

From novice to tech pro — start learning today.