https://github.com/dazinator/aspnetsolutionupgradetool
A utility that can be used to upgrade an ASP.NET 5 RC1 or RC2 based solution to ASP.NET Core 1.0.0 RTM.
https://github.com/dazinator/aspnetsolutionupgradetool
Last synced: about 1 year ago
JSON representation
A utility that can be used to upgrade an ASP.NET 5 RC1 or RC2 based solution to ASP.NET Core 1.0.0 RTM.
- Host: GitHub
- URL: https://github.com/dazinator/aspnetsolutionupgradetool
- Owner: dazinator
- License: mit
- Created: 2016-05-20T13:51:56.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2016-07-08T11:48:49.000Z (almost 10 years ago)
- Last Synced: 2025-04-11T02:41:02.084Z (about 1 year ago)
- Language: C#
- Homepage:
- Size: 250 KB
- Stars: 5
- Watchers: 4
- Forks: 2
- Open Issues: 11
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# AspNetSolutionUpgradeTool
This tool upgrades RC1, or RC2 solution, to RTM
If this tool has helped you upgrade your project, please consider leaving an entry on the wiki - https://github.com/dazinator/AspNetSolutionUpgradeTool/wiki/Usages
```
AspNetUpgrade.exe --solutionDir "E:\\path\\to\\your\\solution" -r RTM
```
1. Upgrades the `project.json` files, `.xproj` files, `launchSettings.json` files and `global.json` file to the new schema's versions.
2. Upgrades `.cs` files, using Roslyn, to detect and replace old RC1 using statements.
3. Upgrades dependencies (NuGet packages) and commands, to the appropriate RTM dependencies / tools. (lot's of renaming occured).
NOTE: This tool only does some simple C# code refactoring at present - i.e using statement rewrites, all the rest is still left to you, however as this tool has access to the full `SyntaxTree` it's fairly easy to add new analysis / refactorings into the tool if you know what you are doing with Roslyn ;)
This tool doesn't currently correct Razor files, i;m investigating that at the moment, see [#41](https://github.com/dazinator/AspNetRC1toRC2UpgradeTool/issues/41)
Your mileage may vary.
This tool is `Idempotent` - which means you should be able to run it against the solution multiple times in a row without negative consequences. As I add new enhancements to this tool, you could run it against a solution you upgraded previosuly with the tool, and this time you should get the enhanced behaviour applied.
# Thanks
A variety of sources have been used to build this tool, inlcuding my own trial and error. Some noteable mentions:
1. Shaun's blog: https://wildermuth.com/2016/05/17/Converting-an-ASP-NET-Core-RC1-Project-to-RC2
2. @Pranavkm's tool that does project.json schema changes: https://github.com/pranavkm/FixProjectJsonWarnings