-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Port CSharpSymbolTests to run on Desktop and CoreCLR. #18471
Changes from 10 commits
37456ea
5a3e9ed
24774d2
fcc972c
06a168b
e731a54
a58fabc
da5ba75
7250fc2
21ddbe5
d3e41e1
0e641fb
7494b9e
fce3879
ffd5ac8
3838d1b
d497f24
bf9cc72
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -453,6 +453,19 @@ | |
TargetMonikers=".NETFramework,Version=v4.6"> | ||
<Output TaskParameter="ResolvedCopyLocalItems" ItemName="ReferenceCopyLocalPaths" /> | ||
</ResolveNuGetPackageAssets> | ||
|
||
<!-- Desktop tests need to load the Desktop version of the TestUtilities via reflection at runtime without | ||
referencing the assembly at compile time. However, it looks like adding a project-to-project reference | ||
with ReferenceOutputputAssembly=false and Private=true does not copy the assembly to the output | ||
(https://github.com/Microsoft/msbuild/issues/1916). Therefore, we reference the assembly but do the | ||
copying ourselves, by adding the output path of the project (GetTargetPath) manually to the set of copied | ||
assemblies (ReferenceCopyLocalPaths) --> | ||
<MSBuild Projects="$(MSBuildThisFileDirectory)..\..\src\Test\Utilities\Desktop\TestUtilities.Desktop.csproj" | ||
Targets="GetTargetPath" | ||
BuildInParallel="true"> | ||
|
||
<Output TaskParameter="TargetOutputs" ItemName="ReferenceCopyLocalPaths" /> | ||
</MSBuild> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I was wondering how you would work around this problem. Can you add a comment documenting what this accomplishes? |
||
</Target> | ||
|
||
<!-- Returns the current build version. Used in .vsixmanifests to substitute our build version into them --> | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -31,6 +31,9 @@ | |
<BaseIntermediateOutputPath Condition="'$(BaseIntermediateOutputPath)' == ''">$(RepoRoot)Binaries\Obj\</BaseIntermediateOutputPath> | ||
<IntermediateOutputPath>$(BaseIntermediateOutputPath)$(Configuration)\$(MSBuildProjectName)\</IntermediateOutputPath> | ||
|
||
<NetStandard20RefPath>$(NuGetPackageRoot)/NETStandard.Library/$(NETStandardLibraryVersion)/build/netstandard2.0/ref/</NetStandard20RefPath> | ||
<MicrosoftCSharpRefPath>$(NuGetPackageRoot)/Microsoft.CSharp/$(MicrosoftCSharpVersion)/ref/netstandard1.0/</MicrosoftCSharpRefPath> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why are we specifying thes properties here? Shouldn't they be generated into Dependencies.props? |
||
|
||
<!-- Workaround until we move to Microsoft.Net.Compilers.nupkg with this fix: https://github.com/dotnet/roslyn/commit/05c12ebfcdd08a02dbceded5327a8da7a7df23be: | ||
Use the Microsoft.Net.Compilers.props file with the fix checked into the repo instead of the one that comes along with the nuget package: | ||
$(NuGetPackageRoot)\Microsoft.Net.Compilers\$(ToolsetCompilerPackageVersion)\build\Microsoft.Net.Compilers.props --> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you know why this changed?