Skip to content

Conversation

@KevinRansom
Copy link
Contributor

The vsix was not correctly redirecting to all of the assemblies in the nightly vsix.

This change corrects a few assembly versions. And uses the project file mechanism to generate vsix bindingredirect and vsix codebase entries. And removed the hand coded incorrect ones.

Kevin

@KevinRansom KevinRansom requested a review from brettfo April 2, 2019 19:30
</AssemblyAttribute>
<AssemblyAttribute Include="Microsoft.VisualStudio.Shell.ProvideCodeBaseAttribute">
<AssemblyName>FSharp.Compiler.Private</AssemblyName>
<Version>$(FSProductVersion)$(_BuildNumberSuffix)</Version>
Copy link
Member

Choose a reason for hiding this comment

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

Why the difference in assembly suffix? $(VSAssemblyVersion) vs $(FSProductVersion)$(_BuildNumberSuffix).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

VSAssemblyVersion is 15.9.0.0
$(FSProductVersion)$(_BuildNumberSuffix) 10.2.3.0

@KevinRansom KevinRansom merged commit fdd1bbe into dotnet:master Apr 2, 2019
@KevinRansom KevinRansom deleted the vsixredirects branch July 2, 2019 22:37
nosami pushed a commit to xamarin/visualfsharp that referenced this pull request Jan 26, 2022
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.

2 participants