Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
/ corefx Public archive

Add dll to netfx references to force bindingRedirects #18300

Merged
merged 2 commits into from
Apr 13, 2017

Conversation

ericstj
Copy link
Member

@ericstj ericstj commented Apr 12, 2017

This dll has a reference to the earliest version of every contract
desktop ever shipped.

This will ensure that RAR sees conflicts and adds binding redirects.

Fixes #7702

/cc @weshaggard

This dll has a reference to the earliest version of every contract
desktop ever shipped.

This will ensure that RAR sees conflicts and adds binding redirects.
</ItemGroup>

<Target Name="DumpVersions" DependsOnTargets="ResolveReferences">
<Message Text="%(ReferencePath.FusionName)" />
Copy link
Member

Choose a reason for hiding this comment

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

Did this list of versions look correct?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes. Everything followed the 4.0.n0.0 pattern.

<Project ToolsVersion="14.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<Import Project="..\dir.props" />
<PropertyGroup>
<AssemblyVersion>0.0.0.0</AssemblyVersion>
Copy link
Member

Choose a reason for hiding this comment

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

Any particular reason you are given this assembly version 0?

Copy link
Member Author

Choose a reason for hiding this comment

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

Because we should not version it. It won't show up in any typerefs.

<Import Project="..\dir.props" />
<PropertyGroup>
<AssemblyVersion>0.0.0.0</AssemblyVersion>
<AssemblyKey>MSFT</AssemblyKey>
Copy link
Member

Choose a reason for hiding this comment

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

Why not the open key?

Copy link
Member Author

Choose a reason for hiding this comment

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

I can do that. I didn't want to add a new signing problem.

Copy link
Member

Choose a reason for hiding this comment

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

The signing problem exists regardless of this assembly.

@ericstj ericstj merged commit a6f97f6 into dotnet:master Apr 13, 2017
@karelz karelz modified the milestone: 2.0.0 Apr 15, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants