Conversation
Member
Author
|
Version issue is tracked in NuGet/Home#4337. Will need to work around it. |
…en restoring NuGet packages)
Member
Author
|
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? :) |
Member
Author
|
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. |
Member
Author
|
@defcon84 - I'm going to publish this to NuGet tomorrow. You can use the dev server in the meantime. |
Member
Author
|
This is included in the 3.1 release: https://reactjs.net/2017/07/3.1.0-release.html |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Upgrades ReactJS.NET to use Visual Studio 2017 and the newer csproj tooling.
There's some issues that need to be fixed:
1.0).ps1files in the wrong place ("Issue: PowerShell file outside tools folder" with migrated VS2017 project NuGet/Home#5176)