Skip to content
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

Support backslashes in solution paths #2963

Merged
merged 3 commits into from
Feb 20, 2018

Conversation

rainersigwald
Copy link
Member

Add a test that will fail on forward-slash OSes when reading a
backslash-containing relative path from a solution file.

Regression test for #2022.

Add a test that will fail on forward-slash OSes when reading a
backslash-containing relative path from a solution file.

Regression test for dotnet#2022.
@rainersigwald rainersigwald changed the title WIP: Support backslashes in solution paths Support backslashes in solution paths Feb 13, 2018
@rainersigwald
Copy link
Member Author

@radical Do you mind me taking the core of your change from mono/msbuild@86adc96 like this? I was hoping to be able to just cherry-pick or merge it but it has mono-only tests that would make that inconvenient.

@radical
Copy link
Member

radical commented Feb 13, 2018

@rainersigwald go ahead!

@rainersigwald rainersigwald merged commit 4b35f73 into dotnet:master Feb 20, 2018
@rainersigwald rainersigwald deleted the solution-slashes branch February 20, 2018 23:37
rainersigwald added a commit to rainersigwald/msbuild that referenced this pull request May 9, 2018
We started (transitively) requiring
System.Runtime.InteropServices.RuntimeInformation when using
`SolutionFile.Parse` after dotnet#2963. The assembly-level dependency is
longstanding. But since it wasn't needed in NuGet's calling pattern,
many versions of NuGet are broken on older (pre-4.7.1) .NET Frameworks.

Work around the assembly load by avoiding the adjustment filepath on
full-Framework MSBuild (where it's not necessary anyway).

Closes dotnet#3282.
rainersigwald added a commit that referenced this pull request May 11, 2018
We started (transitively) requiring
System.Runtime.InteropServices.RuntimeInformation when using
`SolutionFile.Parse` after #2963. The assembly-level dependency is
longstanding. But since it wasn't needed in NuGet's calling pattern,
many versions of NuGet are broken on older (pre-4.7.1) .NET Frameworks.

Work around the assembly load by avoiding the adjustment filepath on
full-Framework MSBuild (where it's not necessary anyway).

Closes #3282.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants