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

Fix issues with using dogfood compilers #31779

Merged
merged 2 commits into from
Dec 18, 2018
Merged

Fix issues with using dogfood compilers #31779

merged 2 commits into from
Dec 18, 2018

Conversation

tmat
Copy link
Member

@tmat tmat commented Dec 14, 2018

Infrastructure only change.

@tmat tmat requested a review from a team as a code owner December 14, 2018 00:22
@tmat tmat changed the title WIP: Wpf temp nu get WIP: @tmat Fix issues with using dogfood compilers Dec 14, 2018
@tmat tmat changed the title WIP: @tmat Fix issues with using dogfood compilers WIP: Fix issues with using dogfood compilers Dec 14, 2018
@tmat tmat added PR For Personal Review Only The PR doesn’t require anyone other than the developer to review it. Area-Infrastructure labels Dec 14, 2018
Copy link
Member

@Pilchie Pilchie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please stop mucking with $(MSBuildAllProjects), but otherwise looks good.

<Project>

<PropertyGroup>
<MSBuildAllProjects>$(MSBuildAllProjects);$(MSBuildThisFileFullPath)</MSBuildAllProjects>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If/when dev16 is a requirement, you can stop adding this. MSBuild now handles it for you, and adding it just leads to annoying LOH allocations.

cc @rainersigwald @drewnoakes

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yup.

Property _TargetAssemblyProjectName is set by GenerateTemporaryTargetAssembly task.
-->
<PropertyGroup Condition="'$(IsWpfTempProject)' == 'true'">
<_WpfTempProjectNuGetFileNameNoExt>$(ArtifactsObjDir)$(_TargetAssemblyProjectName)\$(_TargetAssemblyProjectName)$(MSBuildProjectExtension).nuget.g</_WpfTempProjectNuGetFileNameNoExt>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmarolf Looks like we can/should add this workaround to project-system too (until we get to arcade, where I'm sure @tmat will fix it as well)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmarolf You can copy the following 2 commits to Arcade SDK:
dotnet/arcade@3d88163
dotnet/arcade@ad721e6

The changes in this PR are Roslyn specific and not needed for Project System.

@tmat tmat closed this Dec 16, 2018
@tmat tmat reopened this Dec 16, 2018
@tmat tmat changed the title WIP: Fix issues with using dogfood compilers Fix issues with using dogfood compilers Dec 17, 2018
Run-MSBuild sets various properties based on global variables that were not set in Restore-Project.
@tmat tmat merged commit 3c64d34 into dotnet:master Dec 18, 2018
@tmat tmat deleted the WpfTempNuGet branch December 18, 2018 01:20
@tmat tmat removed the PR For Personal Review Only The PR doesn’t require anyone other than the developer to review it. label Dec 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants