search

microsoft / VS-PPT

Productivity Power Tools - a set of Visual Studio extensions improving developer productivity.
http://aka.ms/extendvs
Other
885 stars 146 forks source link

FixMixedTabs references Microsoft.VisualStudio.ExtensionManager, Version=15.0.0.0 on Visual Studio 2019 #221

Closed schuettecarsten closed 5 years ago

schuettecarsten commented 5 years ago

FixMixedTabs references Microsoft.VisualStudio.ExtensionManager, Version=15.0.0.0 on Visual Studio 2019. This causes an error message when VS2019 Preview 3 ist started:

  <entry>
    <record>2390</record>
    <time>2019/02/13 22:40:19.864</time>
    <type>Error</type>
    <source>Editor or Editor Extension</source>
    <description>System.IO.FileNotFoundException: Could not load file or assembly &apos;Microsoft.VisualStudio.ExtensionManager, Version=15.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a&apos; or one of its dependencies. Das System kann die angegebene Datei nicht finden.&#x000D;&#x000A;File name: &apos;Microsoft.VisualStudio.ExtensionManager, Version=15.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a&apos;&#x000D;&#x000A;   at FixMixedTabs.MarginFactory.CreateMargin(IWpfTextViewHost textViewHost, IWpfTextViewMargin containerMargin)&#x000D;&#x000A;   at Microsoft.VisualStudio.Text.Utilities.ContainerMargin.&lt;AddMargins&gt;b__27_1(IWpfTextViewMarginProvider mp)&#x000D;&#x000A;   at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.InstantiateExtension[TExtension,TMetadata,TExtensionInstance](Object errorSource, Lazy`2 provider, Func`2 getter)&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)&#x000D;&#x000A;&#x000D;&#x000A;WRN: Protokollierung der Assemblybindung ist AUS.&#x000D;&#x000A;Sie k&#x00F6;nnen die Protokollierung der Assemblybindungsfehler aktivieren, indem Sie den Registrierungswert [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) auf 1 festlegen.&#x000D;&#x000A;Hinweis: Die Protokollierung der Assemblybindungsfehler f&#x00FC;hrt zu einer gewissen Leistungseinbu&#x00DF;e.&#x000D;&#x000A;Sie k&#x00F6;nnen dieses Feature deaktivieren, indem Sie den Registrierungswert [HKLM\Software\Microsoft\Fusion!EnableLog] entfernen.&#x000D;&#x000A;</description>
  </entry>
ghost commented 5 years ago

@schuettecarsten beat me to it! This is raising the exception dialog every time I open a file. Disabling FixMixedTabs is a work-around for now, but I love this extension's functionality and would like to see it fixed asap!

DoCode commented 5 years ago

Any news here?

Parexus commented 5 years ago

I've got the same problem; here's what's in my ActivityLog.xml:

System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.ExtensionManager, Version=15.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'Microsoft.VisualStudio.ExtensionManager, Version=15.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' at FixMixedTabs.MarginFactory.CreateMargin(IWpfTextViewHost textViewHost, IWpfTextViewMargin containerMargin) at Microsoft.VisualStudio.Text.Utilities.ContainerMargin.b__27_1(IWpfTextViewMarginProvider mp) at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.InstantiateExtension[TExtension,TMetadata,TExtensionInstance](Object errorSource, Lazy2 provider, Func2 getter) --- End of stack trace from previous location where exception was thrown --- at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

IanKemp commented 5 years ago

I get this error only when opening a solution, thankfully.

TechWatching commented 5 years ago

Same error for me. I reported the problem to VS Team but they told me to give a feedback here. Is this repository still alive ? It seems that there is no activity on this repository.

DoCode commented 5 years ago

@TechWatching they told me the same.
But the repository seems to be dead!?

TechWatching commented 5 years ago

They might be doing some work on a private repository and this repo is just a remote to which they are pushing code from time to time. I don't know and neither do I know how to contact the team who builds the Productivity Power Tools directly.

DoCode commented 5 years ago

That's annoying... How to communicate and contribute to a team that's not contactable? :-(

ghost commented 5 years ago

Here are the top contributors of this repository: https://github.com/Microsoft/VS-PPT/graphs/contributors Bugging them would be a start.

DoCode commented 5 years ago

@DanVicarel thanks a lot!
So @olegtk can you please look at these issues OR tell us the current state with this repository?

ghost commented 5 years ago

Also pinging @dampir and @jakubsuchybio since you made commits in the FixMixedTabs folder

jakubsuchybio commented 5 years ago

Yeah, I think that has nothing to do with me :) I just commited change so that this extension would be compatible with VS2017 when 2017 was in the first few previews.

willl commented 5 years ago

I think the project needs to be updated to include the new Microsoft.VisualStudio.SDK mentioned here.

The extensions are currently trying to reference Microsoft.VisualStudio.ExtensionManager for VS 2015 (aka 15.0.0.0). So a PR just needs to be submitted referencing the nuget package I posted above.

jasonruz commented 5 years ago

It seems it might be fixed now, the extension just got updated to v15.0.6 and this is the Release Notes:

26-Mar-2019: v15.0.6 - Removed bad extension manager reference

IanKemp commented 5 years ago

It seems it might be fixed now, the extension just got updated to v15.0.6 and this is the Release Notes:

26-Mar-2019: v15.0.6 - Removed bad extension manager reference

Can confirm that 15.0.6 fixes the issue.

prnadago commented 5 years ago

Thanks for confirming the fix! I'll go ahead and close this issue.

ghost commented 5 years ago

Hm, don't understand how this issue was fixed if the last commit was 10 months ago... but whatever, I too confirm that its working in 15.0.6 on VS 2019 Preview 4.4 @prnadago after the confusion above, it would be nice to know the actual maintainers of this repo are.