A different approach to .NET Standard #78
Merged
Conversation
This file contains 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
separate because both flavors of csproj apparently cannot coexist in one sln
tpluscode
force-pushed
the
netstandard-lite
branch
from
a6bfa05 to
1f0718b
Compare
|
Hm, any idea why AppVeyor only reports 40 tests. In Visual Studio and Release build that number is doubled? |
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.
Another attempt to fix #65 and fix #69
Instead of switching all projects, I only created the reference assembly and the assembly to process targetting .NET Standard/Core. Apparently both types of csproj cannot exist beside each other in a single solution. Is it a fact or just me? To overcome that I created a second sln and
Fody.csprojcallsdotnetto build the new stuff. Ugly but works.