-
Notifications
You must be signed in to change notification settings - Fork 930
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to Visual Studio 2017 + csproj tooling #406
Conversation
Version issue is tracked in NuGet/Home#4337. Will need to work around it. |
…en restoring NuGet packages)
This builds on my computer and mostly seems to work, but is broken on AppVeyor |
11fa5dc
to
93751ee
Compare
…net/cli/issues/6561 and dotnet/msbuild#406), and run correct test command
Thanks! When will this be published to Nuget? :) |
I didn't have any immediate plans to push these changes to NuGet, as the only real user-facing change is moving from .NET Core 1.0 to 1.1. I'll probably at least split the middleware out into a separate NuGet package (#388) before pushing. |
@defcon84 - I'm going to publish this to NuGet tomorrow. You can use the dev server in the meantime. |
This is included in the 3.1 release: https://reactjs.net/2017/07/3.1.0-release.html |
Upgrades ReactJS.NET to use Visual Studio 2017 and the newer csproj tooling.
There's some issues that need to be fixed:
1.0
).ps1
files in the wrong place ("Issue: PowerShell file outside tools folder" with migrated VS2017 project NuGet/Home#5176)