能否用Visual Studio 15.7正式版替代预览版开发ASP.NET Core 2.1项目？

Absolutely! You can safely switch from Visual Studio 15.7.x Preview builds to the official 15.7 stable release for your ASP.NET Core 2.1 projects—this is actually the recommended path now that the stable version is available, especially since you’ve been dealing with frustrating preview-related issues.

Here’s what you need to know to make the transition smooth:

• Full compatibility with ASP.NET Core 2.1: The official 15.7 release is fully optimized to support ASP.NET Core 2.1. Your existing projects won’t require core code changes to run correctly; all the ASP.NET Core 2.1 features you used in the preview have been polished and finalized in the stable build.
• Fixes for preview-era bugs: The stable release addresses most of the instability issues present in the preview builds—things like random compilation errors, debugging glitches, slow project loading, or unexpected runtime crashes should be resolved once you switch.
• Step-by-step transition guide:
  1. Uninstall your current Visual Studio 15.7.x Preview version first. While Microsoft allows preview and stable versions to coexist, removing the preview eliminates potential environment conflicts that could cause odd behavior down the line.
  2. Download and install the official Visual Studio 15.7 release. Make sure to select the ASP.NET and Web Development workload during installation—this will automatically include all the necessary tools for ASP.NET Core 2.1 development.
  3. Open your ASP.NET Core 2.1 project. If you encounter project loading issues, try deleting the .vs hidden folder, plus the bin and obj directories in your project root, then reload the project. This clears cached build artifacts that might cause conflicts.
• Rare experimental feature check: If you happened to use any experimental, non-final features in the preview (which is unlikely for ASP.NET Core 2.1, as all core features were locked in before the stable release), double-check if those features are supported in the official build. But for most standard ASP.NET Core 2.1 projects, this won’t be a concern.

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