Installed product versions

• Visual Studio: 2019 Preview (16.2.0 Preview 1)
• This extension: 1.4

Description

5/31/2019 9:41:43 AM - Skipping 'C:\Users\mdepouw\AppData\Local\Microsoft SDKs' as it doesn't exist
5/31/2019 9:41:43 AM - Beginning to install extension to Microsoft Visual Studio Enterprise 2019...
5/31/2019 9:41:43 AM - Upgrading 'Extensibility Logs', version 1.4 to version 1.5.0.
5/31/2019 9:41:44 AM - Install Error : Microsoft.VisualStudio.ExtensionManager.MissingReferencesException: This extension cannot be installed because the following references are missing:
-Microsoft.VisualStudio.Component.CoreEditor (Microsoft.VisualStudio.Component.CoreEditor)
at Microsoft.VisualStudio.ExtensionManager.EngineUtilities.EnsureNoMissingReferences(IEnumerable1 missingRefs) at Microsoft.VisualStudio.ExtensionManager.PackageInstaller.PrepareEngineInstall(IDependencyGraph dGraph, IDependencyComparisonSeed seed, Component vsixComponent, Boolean isProductComponent, Int32& totalInstallationSteps) at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.PerformSetupEngineInstall(InstallableExtensionImpl extension, Boolean installPerMachine, Boolean isPackComponent, IDictionary2 extensionsInstalledSoFar, List1 extensionsUninstalledSoFar, IInstalledExtensionList modifiedInstalledExtensionsList, IProgress1 progress, InstallFlags installFlags, AsyncOperation asyncOp, Version targetedVsVersion, IInstalledExtension& newExtension)
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.InstallInternal(InstallableExtensionImpl extension, InstallFlags installFlags, IDictionary2 extensionsInstalledSoFar, List1 extensionsUninstalledSoFar, IInstalledExtensionList modifiedInstalledExtensionsList, AsyncOperation asyncOp, IProgress`1 progress, Version targetedVsVersion)
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.BeginInstall(IInstallableExtension installableExtension, InstallFlags installFlags, AsyncOperation asyncOp, Version targetedVsVersion)
at Microsoft.VisualStudio.ExtensionManager.ExtensionEngineImpl.InstallWorker(IInstallableExtension extension, InstallFlags installFlags, AsyncOperation asyncOp)

Steps to recreate

1. Upgrade from 1.4 to 1.5 in VS 2019 Preview

Current behavior

Install error

Expected behavior

No exeception 😊

Installed product versions

• Visual Studio: 2019 v16.0.0 Preview 2.2
• This extension: v0.1.0

Description

Only the following two VS SDK package references have been added to the project:

Madskristensen.VisualStudio.SDK v16.0.81-pre 2
Microsoft.VSSDK.BuildTools v16.0.298

This causes two package-related conflict warnings to be emitted.

Current behavior

Warning MSB3277: Found conflicts between different versions of "Microsoft.VisualStudio.ComponentModelHost" that could not be resolved.

Warning MSB3277: Found conflicts between different versions of
"Microsoft.VisualStudio.Text.Data" that could not be resolved.

Expected behavior

No warning errors

1. Collage of various extensibility logs
2. Toolbar

For people who don't want to add more toolbars or don't have any visible toolbars at all, could we get a View -> Extensibility Logs -> <the log commands> flyout menu as well?

From: VsixCommunity/ExtensibilityEssentials#2

cc @madskristensen

@yannduran thanks for the ping.

Installed, I can see this being useful! 😄

It would be nice if it showed the current instance's folder somewhere. This is something I seem to need quite regularly. E.g. open the folder like this:
C:\Users\AppData\Local\Microsoft\VisualStudio\16.0_aabc1737\

Or simply output it on the Path Variables dump for copy/pasting?

Installed product versions

• Visual Studio: N/A
• This extension: N/A

Description

https://marketplace.visualstudio.com/items?itemName=YannDuran.ExtensibilityLogs

Steps to recreate

1. Go to the marketplace

Current behavior

Current link is to the developer-news repo

Expected behavior

Link to this repo

Installed product versions

• Visual Studio 2019 Enterprise Preview (16.0.0 Preview 2.1)
• This extension: v0.1.0

Description

If there's no trailing slash on the website page url, it results in a 404 error.

Steps to recreate

1. Type https://luminous-software.solutions/extensibility-logs into a browser, without a trailing slash (or click the link above).

Current behavior

https://luminous-software.solutions/extensibility-logs/ (with a trailing slash) opens the web page.
https://luminous-software.solutions/extensibility-logs (without a trailing slash) results in a 404 error.

Both https://luminous-software.solutions/time-savers/ (with a trailing slash) and https://luminous-software.solutions/time-savers (without a trailing slash) have always opened the web page.

Expected behavior

Both https://luminous-software.solutions/extensibility-logs/ (with a trailing slash) and https://luminous-software.solutions/extensibility-logs (without a trailing slash) should open the web page.

Installed product versions

• Visual Studio: 2019
• This extension: 1.6

Description

Error when clicking on VSIX Installer log

Steps to recreate

1. install the extension
2. click on VSIX Installer log from your extension

Current behavior

I get this exception:

System.TypeLoadException: Could not load type 'Luminous.Code.Extensions.Strings.StringExtensions' from assembly 'Luminous.Code.Core, Version=1.4.2.0, Culture=neutral, PublicKeyToken=null'.
   at ExtensibilityLogs.Commands.Logs.VsixInstallerLogCommand.<ExecuteAsync>d__2.MoveNext()
   at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
   at ExtensibilityLogs.Commands.Logs.VsixInstallerLogCommand.ExecuteAsync(OleMenuCmdEventArgs e)
   at Community.VisualStudio.Toolkit.BaseCommand`1.<>c__DisplayClass14_0.<<Execute>b__0>d.MoveNext()

Expected behavior

no exception

@madskristensen do you think enabling/disabling Fusion logging would be useful for extensibility authors? I haven't used it myself, but I thought you'd know better than most.

I saw it mentioned in the MEF Error Log:

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].