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

Properly declare NuGet dependencies on Humanizer and ICSharpCode.Decompiler #24162

Closed
KirillOsenkov opened this issue Jan 11, 2018 · 8 comments
Closed
Assignees
Labels
Area-IDE Area-Infrastructure Resolution-Fixed The bug has been fixed and/or the requested behavior has been implemented
Milestone

Comments

@KirillOsenkov
Copy link
Member

Version Used:
2.7.0-beta3-62509-03

I'm looking at this family of NuGets and I don't see a dependency on Humanizer and ICSharpCode.Decompiler. These need to be explicitly declared on the Roslyn NuGet packages that require them (EditorFeatures?)

@KirillOsenkov
Copy link
Member Author

Otherwise it's impossible to know which exact version of ICSharpCode.Decompiler to take and from where.

@KirillOsenkov
Copy link
Member Author

Also need to explicitly declare dependencies on VS Editor:

  <package id="Microsoft.VisualStudio.CoreUtility" version="15.6.161-preview" targetFramework="net45" />
  <package id="Microsoft.VisualStudio.Language.Intellisense" version="15.6.161-preview" targetFramework="net45" />
  <package id="Microsoft.VisualStudio.Language.StandardClassification" version="15.6.161-preview" targetFramework="net45" />
  <package id="Microsoft.VisualStudio.Text.Data" version="15.6.161-preview" targetFramework="net45" />
  <package id="Microsoft.VisualStudio.Text.Internal" version="15.6.161-preview" targetFramework="net45" />
  <package id="Microsoft.VisualStudio.Text.Logic" version="15.6.161-preview" targetFramework="net45" />
  <package id="Microsoft.VisualStudio.Text.UI" version="15.6.161-preview" targetFramework="net45" />
  <package id="Microsoft.VisualStudio.Text.UI.Wpf" version="15.6.161-preview" targetFramework="net45" />

@KirillOsenkov
Copy link
Member Author

And also check ManagedEsent.

@KirillOsenkov
Copy link
Member Author

As far as I can see the actual version is https://www.nuget.org/packages/ICSharpCode.Decompiler/3.0.0.3403-beta4

@KirillOsenkov
Copy link
Member Author

So this would be super nice to fix soon, because figuring out which Editor packages are needed for the Roslyn version is super hard.

@jinujoseph

@KirillOsenkov
Copy link
Member Author

Need to formalize dependencies on the Editor:

<MicrosoftVisualStudioTextDataVersion>15.0.26730-alpha</MicrosoftVisualStudioTextDataVersion>
<MicrosoftVisualStudioTextInternalVersion>15.0.26730-alpha</MicrosoftVisualStudioTextInternalVersion>
<MicrosoftVisualStudioTextLogicVersion>15.0.26730-alpha</MicrosoftVisualStudioTextLogicVersion>
<MicrosoftVisualStudioTextUIVersion>15.0.26730-alpha</MicrosoftVisualStudioTextUIVersion>
<MicrosoftVisualStudioTextUIWpfVersion>15.0.26730-alpha</MicrosoftVisualStudioTextUIWpfVersion>

@jinujoseph jinujoseph added this to the 15.7 milestone Mar 9, 2018
@jinujoseph
Copy link
Contributor

cc @jasonmalinowski

@KirillOsenkov
Copy link
Member Author

@jinujoseph Just to reiterate, this is very painful for us. Would be super nice to have a fix soon, so we can reliable tell for any given Roslyn build which Editor matches it. We're juggling 15.6, 15.7 and master, and we have a fork of VS Editor for each of those, it's a terrible mess. Very hard to keep track of bits.

@JieCarolHu JieCarolHu added the 4 - In Review A fix for the issue is submitted for review. label Mar 16, 2018
@jinujoseph jinujoseph modified the milestones: 15.7, 15.8 Apr 18, 2018
@JieCarolHu JieCarolHu added Resolution-Fixed The bug has been fixed and/or the requested behavior has been implemented and removed 4 - In Review A fix for the issue is submitted for review. labels May 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE Area-Infrastructure Resolution-Fixed The bug has been fixed and/or the requested behavior has been implemented
Projects
None yet
Development

No branches or pull requests

3 participants