You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgrade to Visual Studio 2017 + csproj tooling (#406)
* Upgrade to Visual Studio 2017 + csproj tooling
* Include workaround for NuGet/Home#4337 (explicitly specify version when restoring NuGet packages)
* Work around dotnet/cli-migrate#11
* Upgrade to .NET Core 1.1.x
* Remove VersionPrefix from all csproj files
* Legacy NuGet restore is no longer needed
* Disable CS1701 warning for sample projects
* Turns out we actually do need the legacy NuGet restore
* Use VS2017 AppVeyor image
* Remove project dependencies to work around NuGet/Home#5193 and NuGet/Home#4578
* Use MSBuild 15 on AppVeyor
* Enforce .NET Core tools 1.0.0 in global.json
* Use newer npm on AppVeyor (as a workaround for https://github.com/dotnet/cli/issues/6561 and dotnet/msbuild#406), and run correct test command
<Description>ReactJS and Babel tools for ASP.NET Core, including ASP.NET Core MVC. Please refer to project site (http://reactjs.net/) for full installation instructions, usage examples and sample code</Description>
0 commit comments