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 NuGet PackageReference properly in WPF temporary assembly #2701

Closed
wants to merge 1 commit into from
Closed

Support NuGet PackageReference properly in WPF temporary assembly #2701

wants to merge 1 commit into from

Conversation

rrelyea
Copy link

@rrelyea rrelyea commented Nov 3, 2017

Support NuGet PackageReference properly in WPF temporary assembly by enabling .g.targets and .g.props to be properly included, despite the project file name change.

(Right now, just shopping the approach around, and looking for feedback. Need to coordinate with WPF team as well.)

Fixes: http://github.com/NuGet/Home/issues/5894

These changes react to _OriginalProjectName that is set by the new version of the temp assembly generator code. (see nuget change)

Support NuGet PackageReference properly in WPF temporary assembly by enabling .g.targets and .g.props to be properly included, despite the project file name change.

(Right now, just shopping the approach around, and looking for feedback. Need to coordinate with WPF team as well.)

Fixes: http://github.com/NuGet/Home/issues/5894

These changes react to _OriginalProjectName that is set by the new version of the temp assembly generator code. (see nuget change)
@AndyGerlicher
Copy link
Contributor

Just to clarify, is this for 15.5 or 15.6? master would be 15.6.


<Message Text="MSBuildProjectFile is $(MSBuildProjectFile)" Condition="'$(MSBuildTargetsVerbose)' == 'true'" />

<GenerateTemporaryTargetAssembly2
Copy link
Contributor

Choose a reason for hiding this comment

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

Why do we consume this Task in MSBuild but we don't define it in MSBuild? Isn't assuming that the nuget .targets defining this task a bit hazardous?
In particular, I think this sort of pattern bit us recently in the VS repo (Razzle) where we have the msbuild shipping .targets but not the nuget targets. It ended up breaking language services within VS.

Copy link
Author

Choose a reason for hiding this comment

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

Good catch. Will dig into this.

</GenerateTemporaryTargetAssembly2>

<CreateItem Include="$(IntermediateOutputPath)$(TargetFileName)" >
<Output TaskParameter="Include" ItemName="AssemblyForLocalTypeReference" />
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this just a fancy way to write:

<AssemblyForLocalTypeReference Include="$(IntermediateOutputPath)$(TargetFileName)" />

If so, why not use the simple syntax?

Copy link
Author

Choose a reason for hiding this comment

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

The goal was to copy winfx work identically, so that we have identical behavior ... with very low risk -- except for what we need to change.

@rrelyea
Copy link
Author

rrelyea commented Nov 14, 2017

@AndyGerlicher - targeting 15.6, not 15.5.

@clairernovotny
Copy link
Member

Is there any updates on this?

@JL2210
Copy link

JL2210 commented Jan 31, 2019

@rrelyea

@livarcocc
Copy link
Contributor

@rrelyea we have been looking at older PRs on the MSBuild repo. Is this PR something that you still plan on working on? It seems like there are some left over work here that we should address before we take this.

@rainersigwald
Copy link
Member

Team triage: closing. Let us know if you're interested in picking this up again.

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.

9 participants