[WIP] resolve issues with .NET Core dependency globbing #3151
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
Aaronontheweb
commented
Oct 12, 2017
| @@ -3,7 +3,7 @@ | |||
|
|
|||
| <PropertyGroup> | |||
| <AssemblyName>Akka.Streams.Tests</AssemblyName> | |||
| <TargetFrameworks>net452;netcoreapp1.1</TargetFrameworks> | |||
| <TargetFrameworks>net452;netcoreapp1.1.1</TargetFrameworks> | |||
There was a problem hiding this comment.
Testing a theory on the recent issues with .NET Core on Linux not being able to run specifications, based on what I read here: https://stackoverflow.com/a/43924403/377476
|
@Aaronontheweb this thing is obsolete now right? Im closing it. |
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.
Attempt at resolving #3150
Looks like something in the tooling we use changed suddenly, unrelated to our own changes, which has affected the way .NET Core projects copy their output to their respective bin folders from dependent DLLs.
switched to LTS .NET SDK channel to see if this helps.