咨询将Visual Studio 2010项目迁移至Visual Studio 2017的可行方案

Hey there! Let’s walk through how to get your VS 2010 VB projects up and running smoothly in VS 2017 Pro—since you don’t need to maintain compatibility with VS 2010, this process can be straightforward with a few key steps.

• Backup everything first: Copy your entire VS 2010 project folders from your old Windows 7 laptop to the new Windows 10 machine (use a USB drive, cloud storage, or whatever works for you). Keep the original backup safe in case anything goes wrong during migration.
• Install VS 2017 with the right workloads: When setting up VS 2017 Professional, make sure to check these two critical workloads:
  • .NET Desktop Development (includes full support for VB WinForms)
  • ASP.NET and Web Development (for your VB ASP.NET projects)
    Also, don’t forget to enable support for older .NET Framework versions (2.0, 3.5) in the optional components section—VS 2017 doesn’t install these by default, and you’ll need them for your legacy projects.

• Open the VS 2010 solution directly in VS 2017: Double-click your .sln file or use VS 2017’s "Open Project/Solution" option. VS will automatically launch the Project Migration Wizard. Since you don’t need to keep VS 2010 compatibility, just follow the wizard’s prompts—you can skip any options that mention preserving old project formats.
• Handle .NET Framework versions:
  • For your priority .NET 4.0+ projects: You can either keep them on their current framework version (VS 2017 supports compiling 4.0+ perfectly) or upgrade to a newer, more stable version like 4.7.2 or 4.8 (both fully supported in VS 2017). Upgrading might give you access to newer APIs, but it’s optional.
  • For .NET 2.0/3.5 projects: As long as you installed the older framework support during VS setup, these will migrate without major issues. Since you don’t focus on these, you can leave them as-is for now, or revisit upgrading later if needed.
• Fix minor compatibility hiccups:
  • VB WinForms: Most native controls and code will work out of the box. The only common issues are with third-party controls—you’ll need to update them to versions that support VS 2017, or replace them with native alternatives if updates aren’t available. If the designer throws warnings when you open forms, follow the on-screen prompts to fix settings like outdated control properties.
  • VB ASP.NET: The migration wizard will automatically update your Web.config file to match VS 2017’s ASP.NET configuration format. Double-check any third-party web libraries or custom controls to ensure they’re compatible with VS 2017—you might need to reinstall or update those NuGet packages (if you used them).

• Compile projects one by one: Start with your priority .NET 4.0+ projects. Most compile errors will be missing references or minor syntax tweaks (VS 2017 has slightly stricter VB syntax checking, but old code usually passes with quick fixes).
• Test core functionality: Run each project to make sure WinForms UI interactions work, ASP.NET pages load correctly, and business logic behaves as expected.
• Clean up (optional): Once you confirm everything works, you can delete the old VS 2010 solution backups—since you don’t need compatibility, there’s no reason to keep them cluttering up your drive.

内容的提问来源于stack exchange，提问作者Max Tyack