Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Open
  • Priority: Medium
  • Security: Public
  • Views: 22
  • Last Modified:

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
0
Ahelbling
Asked:
Ahelbling
  • 3
  • 2
6 Comments
 
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
 
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
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Dirk StraussC# Web 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

Join & Write a Comment

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now