You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2022-12-14 12:25:11 PM - Found installed product - Visual Studio Community 2022
2022-12-14 12:25:12 PM - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
at VSIXInstaller.ExtensionService.GetInstallableDataImpl(IInstallableExtension extension, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable1& skuData) at VSIXInstaller.ExtensionService.GetInstallableData(String vsixPath, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable1& skuData)
at VSIXInstaller.ExtensionPackService.IsExtensionPack(IStateData stateData, Boolean isRepairSupported)
at VSIXInstaller.ExtensionPackService.ExpandExtensionPackToInstall(IStateData stateData, Boolean isRepairSupported)
at VSIXInstaller.App.Initialize(Boolean isRepairSupported)
at VSIXInstaller.App.Initialize()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)
Any way to get around this?
I know they made it hard for ASM highlighting as well and asmDude made a workaround so I presume there's a way to get this going as well?
The text was updated successfully, but these errors were encountered:
Oh, that's not good. Thanks for the heads up. I've not yet tested this app for VS2022.
Did you get this error from the MarketPlace install?
The first place I'd check for a manual install is the manifest file, specifically the InstallationTarget version.... It may be possible to simply update the version to [14.0,18.0) and compile again.
I do recall there being some issue about 32bit vs 64bit for distribution. I'll take a look as soon as I can.
Oh, that's not good. Thanks for the heads up. I've not yet tested this app for VS2022.
Did you get this error from the MarketPlace install?
The first place I'd check for a manual install is the manifest file, specifically the InstallationTarget version.... It may be possible to simply update the version to [14.0,18.0) and compile again.
I do recall there being some issue about 32bit vs 64bit for distribution. I'll take a look as soon as I can.
For VS2022 if you search for extensions in the "Manage Extensions" subwindow you find nothing at all for Verilog. "VS Code" has extensions but I need something capable of printing :)
Only way I found is to right click on the .vsix file and run it with the "version selector", which produces the previously listed error.
VSIX installer responds with:
2022-12-14 12:25:11 PM - Found installed product - Visual Studio Community 2022
2022-12-14 12:25:12 PM - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
at VSIXInstaller.ExtensionService.GetInstallableDataImpl(IInstallableExtension extension, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable
1& skuData) at VSIXInstaller.ExtensionService.GetInstallableData(String vsixPath, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable
1& skuData)at VSIXInstaller.ExtensionPackService.IsExtensionPack(IStateData stateData, Boolean isRepairSupported)
at VSIXInstaller.ExtensionPackService.ExpandExtensionPackToInstall(IStateData stateData, Boolean isRepairSupported)
at VSIXInstaller.App.Initialize(Boolean isRepairSupported)
at VSIXInstaller.App.Initialize()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)
Any way to get around this?
I know they made it hard for ASM highlighting as well and asmDude made a workaround so I presume there's a way to get this going as well?
The text was updated successfully, but these errors were encountered: