VS2022 - latest version 17.7.4

[dpmurphy]

Installed product versions

Microsoft Visual Studio Community 2022 Version 17.7.4 VisualStudio.17.Release/17.7.4+34031.279

Description

Install of vsix fails on newest (only) version of VS2022 community.

Steps to recreate

1. Download vsix from market place (2022 version)
2. Install and it fails with attached error message
3. Log sent via email

[tonyhallett]

Did you successfully install other extensions ?

[tonyhallett]

I have just updated visual studio to your version. FCC continues to work, though of course this is different to your scenario.

I would suggest repeating the install. I very much doubt this is any way related to FCC and is a VSIX installer issue.

[dpmurphy]

Tony, Yes I’ve just installed two extensions….

Code converter and rainbow braces without issue.

Dan.

From: Tony Hallett @.> Date: Thursday, September 28, 2023 at 4:34 PM To: FortuneN/FineCodeCoverage @.> Cc: Daniel Murphy @.>, Author @.> Subject: Re: [FortuneN/FineCodeCoverage] VS2022 - latest version 17.7.4 (Issue #352)

Did you successfully install other extensions ?

— Reply to this email directly, view it on GitHubhttps://github.com/FortuneN/FineCodeCoverage/issues/352#issuecomment-1739967124, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABEDFACFKPEYF7PEWDUHIBDX4XNNXANCNFSM6AAAAAA5LDQQLI. You are receiving this because you authored the thread.Message ID: @.***>

[dpmurphy]

Tony, I uninstalled and did a complete reinstall no change.

I downloaded the vs zip file and tried to compile the solution myself I get warnings in the compile, could be the same issue though.

I attached build log. I will continue to probe. I’m on a vmware fusion m2 mac running win 11 arm in case that might be adding to the issue.

Thanks.

Dan.

Rebuild started... Restored C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage-1.1.194\ReportGeneratorPlugins\ReportGeneratorPlugins.csproj (in 27 ms). Restored C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage-1.1.194\FineCodeCoverage2022\FineCodeCoverage2022.csproj (in 231 ms). 1>------ Rebuild All started: Project: ReportGeneratorPlugins, Configuration: Release Any CPU ------ Restored C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage-1.1.194\FineCodeCoverage\FineCodeCoverage.csproj (in 232 ms). 1>ReportGeneratorPlugins -> C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage-1.1.194\ReportGeneratorPlugins\bin\Release\netstandard2.0\ReportGeneratorPlugins.dll 2>------ Rebuild All started: Project: FineCodeCoverage2022, Configuration: Release Any CPU ------ 2> FineCodeCoverage2022 -> C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage-1.1.194\FineCodeCoverage2022\bin\Release\FineCodeCoverage2022.dll 2> FineCodeCoverage2022 -> C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage-1.1.194\FineCodeCoverage2022\bin\Release\FineCodeCoverage2022.vsix 2>C:\Users\dan_p.nuget\packages\microsoft.vssdk.compatibilityanalyzer\17.7.2196\build\Microsoft.VsSDK.CompatibilityAnalyzer.targets(36,5): warning VSIXCompatibility1001: The extension is incompatible with the targeted version of Visual Studio. More info at https://aka.ms/ExtensionSdkErrors. 2>C:\Users\dan_p.nuget\packages\microsoft.vssdk.compatibilityanalyzer\17.7.2196\build\Microsoft.VsSDK.CompatibilityAnalyzer.targets(36,5): warning VSIXCompatibility1001: Following references are incompatible. 2>C:\Users\dan_p.nuget\packages\microsoft.vssdk.compatibilityanalyzer\17.7.2196\build\Microsoft.VsSDK.CompatibilityAnalyzer.targets(36,5): warning VSIXCompatibility1001: Microsoft.VisualStudio.TestWindow.Interfaces.dll -> Microsoft.VisualStudio.Shell.Interop 2>C:\Users\dan_p.nuget\packages\microsoft.vssdk.compatibilityanalyzer\17.7.2196\build\Microsoft.VsSDK.CompatibilityAnalyzer.targets(36,5): warning VSIXCompatibility1001: Microsoft.VisualStudio.Web.BrowserLink.12.0.dll -> envdte ========== Rebuild All: 2 succeeded, 0 failed, 0 skipped ========== ========== Rebuild started at 7:23 AM and took 15.492 seconds ==========

From: Tony Hallett @.> Date: Thursday, September 28, 2023 at 4:53 PM To: FortuneN/FineCodeCoverage @.> Cc: Daniel Murphy @.>, Author @.> Subject: Re: [FortuneN/FineCodeCoverage] VS2022 - latest version 17.7.4 (Issue #352)

I have just updated visual studio to your version. FCC continues to work, though of course this is different to your scenario.

I would suggest repeating the install. I very much doubt this is any way related to FCC and is a VSIX installer issue.

— Reply to this email directly, view it on GitHubhttps://github.com/FortuneN/FineCodeCoverage/issues/352#issuecomment-1739987856, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABEDFABSQKQE2WSHPRGJ4ALX4XPTJANCNFSM6AAAAAA5LDQQLI. You are receiving this because you authored the thread.Message ID: @.***>

[tonyhallett]

I don't think that this is FCC related.

Microsoft.VisualStudio.Web.BrowserLink.12.0.dll -> envdte

FCC uses a some of the interfaces from Microsoft.VisualStudio.TestWindow.Interfaces.dll for extending with the test explorer. One interface that we do not use has a dependency on Microsoft.VisualStudio.Shell.Interop 7.1.40304.0 as it uses IVsHierarchy.

If it is the cause of the problem I could remove the dependency and just copy the interfaces that we use.

[dpmurphy]

I reverted the version of vssdk back to 17.6 from the Sept 17.7 and the incompatibility warnings went away.

I still need to get the manifest correct for this version as it still won’t install

On Sep 29, 2023, at 9:41 AM, Tony Hallett @.***> wrote:



I don't think that this is FCC related.

Microsoft.VisualStudio.Web.BrowserLink.12.0.dll -> envdte

FCC uses a some of the interfaces from Microsoft.VisualStudio.TestWindow.Interfaces.dll for extending with the test explorer. One interface that we do not use has a dependency on Microsoft.VisualStudio.Shell.Interop 7.1.40304.0 as it uses IVsHierarchy.

If it is the cause of the problem I could remove the dependency and just copy the interfaces that we use.

— Reply to this email directly, view it on GitHubhttps://github.com/FortuneN/FineCodeCoverage/issues/352#issuecomment-1740917536, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABEDFAFJYACYQKEB55JTDJ3X43FZFANCNFSM6AAAAAA5LDQQLI. You are receiving this because you authored the thread.Message ID: @.***>

[tonyhallett]

From what I remember Microsoft.VisualStudio.SDK is the version of visual studio that the extension supports.

It should be aligned with the manifest.

( FCC should update to below - although given all new installs of vs will be greater I have not changed )

The only change that could be applied to the manifest is adding x86 as product architecture.

Is this necessary for

vmware fusion m2 mac running win 11 arm

[tonyhallett]

If it helps https://learn.microsoft.com/en-us/visualstudio/install/visual-studio-on-arm-devices?view=vs-2022

[dpmurphy]

So reverted to the latest 17.7.4 version of vssdk and changed the manifest to point to arm64 (only). selecting multiple versions caused issues upon installation.

These settings will compile and install, however you get an exception while building the fcc output frame. This exception seems to come from the excss package. this package was updated yesterday.......This error is while using all the latest updates

so the situation is evolving.

An exception was encountered while constructing the content of this frame. This information is also logged in "C:\Users\dan_p\AppData\Roaming\Microsoft\VisualStudio\17.0_440cd417\ActivityLog.xml".

Exception details: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IndexOutOfRangeException: Index was outside the bounds of the array. at ExCSS.PeriodicValueConverter.PeriodicValue..ctor(IPropertyValue[] options, IEnumerable1 tokens, String[] labels) at ExCSS.PeriodicValueConverter.Construct(Property[] properties) at ExCSS.StartsWithValueConverter.Construct(Property[] properties) at ExCSS.OptionValueConverter.Construct(Property[] properties) at ExCSS.ConstraintValueConverter.Construct(Property[] properties) at ExCSS.OrderedOptionsConverter.Construct(Property[] properties) at ExCSS.UnorderedOptionsConverter.Construct(Property[] properties) at ExCSS.OrValueConverter.Construct(Property[] properties) at ExCSS.OrValueConverter.Construct(Property[] properties) at ExCSS.StyleDeclaration.ToCss(TextWriter writer, IStyleFormatter formatter) at ExCSS.CompressedStyleFormatter.ExCSS.IStyleFormatter.Style(String selector, IStyleFormattable rules) at ExCSS.StyleRule.ToCss(TextWriter writer, IStyleFormatter formatter) at ExCSS.CompressedStyleFormatter.WriteJoined(StringBuilder sb, IEnumerable1 elements, String separator, Boolean first) at ExCSS.CompressedStyleFormatter.ExCSS.IStyleFormatter.Sheet(IEnumerable1 rules) at ExCSS.Stylesheet.ToCss(TextWriter writer, IStyleFormatter formatter) at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.SetInitialTheme(HtmlDocument document) at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.<>c__DisplayClass57_0.<ProcessUnifiedHtml>b__1() at FineCodeCoverage.Core.Utilities.AssemblyUtil.RunInAssemblyResolvingContext[T](Func1 func) at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.Handle(ReadyForReportMessage message) --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at FineCodeCoverage.Core.Utilities.EventAggregator.HandleMethodWrapper.TryHandle[TListener](Object target, Object message, Boolean& wasHandled) at FineCodeCoverage.Core.Utilities.EventAggregator.ListenerWrapper.TryHandle[TListener](Object message, Boolean& wasHandled) at FineCodeCoverage.Core.Utilities.EventAggregator.<>cDisplayClass6_01.<Call>b__0() at FineCodeCoverage.Core.Utilities.EventAggregator.Call[TListener](Object message, Action1 marshaller) at FineCodeCoverage.Output.OutputToolWindowControl..ctor(IEventAggregator eventAggregator) at FineCodeCoverage.Output.OutputToolWindow.Initialize(OutputToolWindowContext context) --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark) at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) at System.Activator.CreateInstance(Type type, Object[] args) at Microsoft.VisualStudio.Shell.Package.InstantiateToolWindow(Type toolWindowType, Object context) at Microsoft.VisualStudio.Shell.Package.<>c__DisplayClass87_0.gCreateToolWindowWorker|1() at Microsoft.VisualStudio.Shell.Package.CreateToolWindow(Type toolWindowType, Int32 id, UInt32 flags, Object context, Guid persistenceGuid) at Microsoft.VisualStudio.Shell.Package.CreateToolWindow(Type toolWindowType, Int32 id, Object context) at Microsoft.VisualStudio.Shell.AsyncPackage.d__40.MoveNext()

[tonyhallett]

Assuming that you have followed the docs correctly https://learn.microsoft.com/en-us/visualstudio/extensibility/arm64/target-arm64-visual-studio-extension?view=vs-2022 the exception suggests that there is an issue with dummyReportToProcess.html

Is there any reason that this would be different on ARM64 ?

[tonyhallett]

If your current issue can be resolved there will be further issues with the Shared files/ZippedTools.

[dpmurphy]

I’ve recompiled the vsix multiple times. Latest was editing the xml files as the gui suggests different versions than the document. Editing does allow multiple architectures to be defined, compiled and no issues upon install. Whereas the gui version will compile but will not install.

I’ve no idea what could be specific to arm64 for the dummyReportToProcess.html. I can preview that file in browser and it looks fine and no errors are produced in the logs.

D.

From: Tony Hallett @.> Date: Monday, October 2, 2023 at 4:03 AM To: FortuneN/FineCodeCoverage @.> Cc: Daniel Murphy @.>, Author @.> Subject: Re: [FortuneN/FineCodeCoverage] VS2022 - latest version 17.7.4 (Issue #352)

Assuming that you have followed the docs correctly https://learn.microsoft.com/en-us/visualstudio/extensibility/arm64/target-arm64-visual-studio-extension?view=vs-2022 the exception suggests that there is an issue with dummyReportToProcess.html [image]https://user-images.githubusercontent.com/11292998/271914322-a8216131-4323-44c7-ac25-b22e3f12c7c9.png

Is there any reason that this would be different on ARM64 ?

— Reply to this email directly, view it on GitHubhttps://github.com/FortuneN/FineCodeCoverage/issues/352#issuecomment-1742566738, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABEDFAFKNQ3G7SQMPJALLXLX5JYLVANCNFSM6AAAAAA5LDQQLI. You are receiving this because you authored the thread.Message ID: @.***>

[dpmurphy]

I get an error even if I make a new console solution.

Fine Code Coverage 10/2/2023 7:45:01 AM: Initializing Fine Code Coverage 10/2/2023 7:45:02 AM: Failed Initialization System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IndexOutOfRangeException: Index was outside the bounds of the array. at ExCSS.PeriodicValueConverter.PeriodicValue..ctor(IPropertyValue[] options, IEnumerable1 tokens, String[] labels) at ExCSS.PeriodicValueConverter.Construct(Property[] properties) at ExCSS.StartsWithValueConverter.Construct(Property[] properties) at ExCSS.OptionValueConverter.Construct(Property[] properties) at ExCSS.ConstraintValueConverter.Construct(Property[] properties) at ExCSS.OrderedOptionsConverter.Construct(Property[] properties) at ExCSS.UnorderedOptionsConverter.Construct(Property[] properties) at ExCSS.OrValueConverter.Construct(Property[] properties) at ExCSS.OrValueConverter.Construct(Property[] properties) at ExCSS.StyleDeclaration.ToCss(TextWriter writer, IStyleFormatter formatter) at ExCSS.CompressedStyleFormatter.ExCSS.IStyleFormatter.Style(String selector, IStyleFormattable rules) at ExCSS.StyleRule.ToCss(TextWriter writer, IStyleFormatter formatter) at ExCSS.CompressedStyleFormatter.WriteJoined(StringBuilder sb, IEnumerable1 elements, String separator, Boolean first) at ExCSS.CompressedStyleFormatter.ExCSS.IStyleFormatter.Sheet(IEnumerable1 rules) at ExCSS.Stylesheet.ToCss(TextWriter writer, IStyleFormatter formatter) at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.SetInitialTheme(HtmlDocument document) at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.<>c__DisplayClass57_0.<ProcessUnifiedHtml>b__1() at FineCodeCoverage.Core.Utilities.AssemblyUtil.RunInAssemblyResolvingContext[T](Func1 func) at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.Handle(ReadyForReportMessage message) --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at FineCodeCoverage.Core.Utilities.EventAggregator.HandleMethodWrapper.TryHandle[TListener](Object target, Object message, Boolean& wasHandled) at FineCodeCoverage.Core.Utilities.EventAggregator.ListenerWrapper.TryHandle[TListener](Object message, Boolean& wasHandled) at FineCodeCoverage.Core.Utilities.EventAggregator.<>cDisplayClass6_01.<Call>b__0() at FineCodeCoverage.Core.Utilities.EventAggregator.Call[TListener](Object message, Action1 marshaller) at FineCodeCoverage.Output.OutputToolWindowControl..ctor(IEventAggregator eventAggregator) at FineCodeCoverage.Output.OutputToolWindow.Initialize(OutputToolWindowContext context) --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark) at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) at System.Activator.CreateInstance(Type type, Object[] args) at Microsoft.VisualStudio.Shell.Package.InstantiateToolWindow(Type toolWindowType, Object context) at Microsoft.VisualStudio.Shell.Package.<>c__DisplayClass87_0.gCreateToolWindowWorker|1() at Microsoft.VisualStudio.Shell.Package.CreateToolWindow(Type toolWindowType, Int32 id, UInt32 flags, Object context, Guid persistenceGuid) at Microsoft.VisualStudio.Shell.Package.CreateToolWindow(Type toolWindowType, Int32 id, Object context) at Microsoft.VisualStudio.Shell.AsyncPackage.d40.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Shell.AsyncPackage.d39.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Shell.AsyncPackage.d38.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Shell.AsyncPackage.<>cDisplayClass47_0.<b0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Shell.ToolWindowCollection.ToolWindowListener.<>cDisplayClass1_0.<<-ctor>b0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Threading.AwaitExtensions.ExecuteContinuationSynchronouslyAwaiter1.GetResult() at Microsoft.VisualStudio.Threading.AsyncLazy1.<>cDisplayClass13_0.<b0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Shell.AsyncPackage.d47.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Shell.AsyncPackage.d48.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at FineCodeCoverage.Output.OutputToolWindowCommand.d13.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at FineCodeCoverage.Impl.PackageInitializer.d3.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at FineCodeCoverage.Impl.Initializer.d13.MoveNext()

From: Tony Hallett @.> Date: Saturday, September 30, 2023 at 11:20 AM To: FortuneN/FineCodeCoverage @.> Cc: Daniel Murphy @.>, Author @.> Subject: Re: [FortuneN/FineCodeCoverage] VS2022 - latest version 17.7.4 (Issue #352)

Do you get the same exception with the most minimal of test / sut ?

— Reply to this email directly, view it on GitHubhttps://github.com/FortuneN/FineCodeCoverage/issues/352#issuecomment-1741788618, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABEDFADGIOYY6422U6I4Z6LX5A2E7ANCNFSM6AAAAAA5LDQQLI. You are receiving this because you authored the thread.Message ID: @.***>

[tonyhallett]

Can you debug the ReportGeneratorUtil SetInitialTheme method to see if the style properties are being set to odd values. Excss cannot be usefully debugged "breakpoint failed to bind in an optimized module.", but hopefully debugging SetInitialTheme is sufficient.

[dpmurphy]

I’m in new territory here ….

But it fails before SetInitialTheme gets called…

System.BadImageFormatException HResult=0x8007000B Message=Could not load file or assembly 'DevZH.HtmlAgilityPack, Version=1.4.9.4, Culture=neutral, PublicKeyToken=bd319b19eaf3b43a' or one of its dependencies. An attempt was made to load a program with an incorrect format. Source=FineCodeCoverage StackTrace: at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.<>c__DisplayClass57_0.b__1() in C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage-1.1.194\SharedProject\Core\ReportGenerator\ReportGeneratorUtil.cs:line 1550 at FineCodeCoverage.Core.Utilities.AssemblyUtil.RunInAssemblyResolvingContext[T](Func`1 func) in C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage-1.1.194\SharedProject\Core\Utilities\AssemblyUtil.cs:line 32 at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.ProcessUnifiedHtml(String htmlForProcessing, String reportOutputFolder) in C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage-1.1.194\SharedProject\Core\ReportGenerator\ReportGeneratorUtil.cs:line 889 at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.BlankReport(Boolean withHistory) in C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage-1.1.194\SharedProject\Core\ReportGenerator\ReportGeneratorUtil.cs:line 1677 at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.Handle(ReadyForReportMessage message) in C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage-1.1.194\SharedProject\Core\ReportGenerator\ReportGeneratorUtil.cs:line 1719

Inner Exception 1: BadImageFormatException: Could not load file or assembly 'DevZH.HtmlAgilityPack.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format.

Inner Exception 2: BadImageFormatException: Could not load file or assembly 'DevZH.HtmlAgilityPack.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format.

From: Tony Hallett @.> Date: Monday, October 2, 2023 at 12:46 PM To: FortuneN/FineCodeCoverage @.> Cc: Daniel Murphy @.>, Author @.> Subject: Re: [FortuneN/FineCodeCoverage] VS2022 - latest version 17.7.4 (Issue #352)

Can you debug the ReportGeneratorUtil SetInitialTheme method to see if the style properties are being set to odd values. Excss cannot be usefully debugged breakpoint failed to bind in an optimized module., but hopefully debugging SetInitialTheme is sufficient.

— Reply to this email directly, view it on GitHubhttps://github.com/FortuneN/FineCodeCoverage/issues/352#issuecomment-1743367617, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABEDFAEINO2B5WFX2DKXSB3X5LVUFAVCNFSM6AAAAAA5LDQQLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBTGM3DONRRG4. You are receiving this because you authored the thread.Message ID: @.***>

[dpmurphy]

Details………

System.BadImageFormatException HResult=0x8007000B Message=Could not load file or assembly 'DevZH.HtmlAgilityPack, Version=1.4.9.4, Culture=neutral, PublicKeyToken=bd319b19eaf3b43a' or one of its dependencies. An attempt was made to load a program with an incorrect format. Source=FineCodeCoverage StackTrace: at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.<>c__DisplayClass57_0.b__1() in C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage-1.1.194\SharedProject\Core\ReportGenerator\ReportGeneratorUtil.cs:line 1550 at FineCodeCoverage.Core.Utilities.AssemblyUtil.RunInAssemblyResolvingContext[T](Func`1 func) in C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage-1.1.194\SharedProject\Core\Utilities\AssemblyUtil.cs:line 32 at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.ProcessUnifiedHtml(String htmlForProcessing, String reportOutputFolder) in C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage-1.1.194\SharedProject\Core\ReportGenerator\ReportGeneratorUtil.cs:line 889 at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.BlankReport(Boolean withHistory) in C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage-1.1.194\SharedProject\Core\ReportGenerator\ReportGeneratorUtil.cs:line 1677 at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.Handle(ReadyForReportMessage message) in C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage-1.1.194\SharedProject\Core\ReportGenerator\ReportGeneratorUtil.cs:line 1719

Inner Exception 1: BadImageFormatException: Could not load file or assembly 'DevZH.HtmlAgilityPack.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format.

Inner Exception 2: BadImageFormatException: Could not load file or assembly 'DevZH.HtmlAgilityPack.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format.

From: Tony Hallett @.> Date: Monday, October 2, 2023 at 12:46 PM To: FortuneN/FineCodeCoverage @.> Cc: Daniel Murphy @.>, Author @.> Subject: Re: [FortuneN/FineCodeCoverage] VS2022 - latest version 17.7.4 (Issue #352)

Can you debug the ReportGeneratorUtil SetInitialTheme method to see if the style properties are being set to odd values. Excss cannot be usefully debugged breakpoint failed to bind in an optimized module., but hopefully debugging SetInitialTheme is sufficient.

— Reply to this email directly, view it on GitHubhttps://github.com/FortuneN/FineCodeCoverage/issues/352#issuecomment-1743367617, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABEDFAEINO2B5WFX2DKXSB3X5LVUFAVCNFSM6AAAAAA5LDQQLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBTGM3DONRRG4. You are receiving this because you authored the thread.Message ID: @.***>

[dpmurphy]

Tony, I found the ReportGeneratorForkFCC Repository, cloned it and tried to recreate the ReportGenerator zip file.

Since I’m pattern matching what was in the original file and trying to reproduce, it’s highly Error prone.

I get further with this approach, but it will be hard to determine if the new errors are issues with the arm64 compile or just not knowing what’s required to properly update the zipped files. I’ve only touched the ReportGenerator zip file.

D.

@.***

System.IndexOutOfRangeException HResult=0x80131508 Message=Index was outside the bounds of the array. Source=ExCSS StackTrace: at ExCSS.PeriodicValueConverter.PeriodicValue..ctor(IPropertyValue[] options, IEnumerable1 tokens, String[] labels) at ExCSS.PeriodicValueConverter.Construct(Property[] properties) at ExCSS.StartsWithValueConverter.Construct(Property[] properties) at ExCSS.OptionValueConverter.Construct(Property[] properties) at ExCSS.ConstraintValueConverter.Construct(Property[] properties) at ExCSS.OrderedOptionsConverter.Construct(Property[] properties) at ExCSS.UnorderedOptionsConverter.Construct(Property[] properties) at ExCSS.OrValueConverter.Construct(Property[] properties) at ExCSS.OrValueConverter.Construct(Property[] properties) at ExCSS.StyleDeclaration.ToCss(TextWriter writer, IStyleFormatter formatter) at ExCSS.CompressedStyleFormatter.ExCSS.IStyleFormatter.Style(String selector, IStyleFormattable rules) at ExCSS.StyleRule.ToCss(TextWriter writer, IStyleFormatter formatter) at ExCSS.CompressedStyleFormatter.WriteJoined(StringBuilder sb, IEnumerable1 elements, String separator, Boolean first) at ExCSS.CompressedStyleFormatter.ExCSS.IStyleFormatter.Sheet(IEnumerable1 rules) at ExCSS.Stylesheet.ToCss(TextWriter writer, IStyleFormatter formatter) at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.SetInitialTheme(HtmlDocument document) in C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage\SharedProject\Core\ReportGenerator\ReportGeneratorUtil.cs:line 299 at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.<>c__DisplayClass57_0.<ProcessUnifiedHtml>b__1() in C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage\SharedProject\Core\ReportGenerator\ReportGeneratorUtil.cs:line 904 at FineCodeCoverage.Core.Utilities.AssemblyUtil.RunInAssemblyResolvingContext[T](Func1 func) in C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage\SharedProject\Core\Utilities\AssemblyUtil.cs:line 32 at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.ProcessUnifiedHtml(String htmlForProcessing, String reportOutputFolder) in C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage\SharedProject\Core\ReportGenerator\ReportGeneratorUtil.cs:line 889 at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.BlankReport(Boolean withHistory) in C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage\SharedProject\Core\ReportGenerator\ReportGeneratorUtil.cs:line 1677 at FineCodeCoverage.Engine.ReportGenerator.ReportGeneratorUtil.Handle(ReadyForReportMessage message) in C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage\SharedProject\Core\ReportGenerator\ReportGeneratorUtil.cs:line 1719 From: Tony Hallett @.> Date: Monday, October 2, 2023 at 12:46 PM To: FortuneN/FineCodeCoverage @.> Cc: Daniel Murphy @.>, Author @.> Subject: Re: [FortuneN/FineCodeCoverage] VS2022 - latest version 17.7.4 (Issue #352)

Can you debug the ReportGeneratorUtil SetInitialTheme method to see if the style properties are being set to odd values. Excss cannot be usefully debugged breakpoint failed to bind in an optimized module., but hopefully debugging SetInitialTheme is sufficient.

— Reply to this email directly, view it on GitHubhttps://github.com/FortuneN/FineCodeCoverage/issues/352#issuecomment-1743367617, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABEDFAEINO2B5WFX2DKXSB3X5LVUFAVCNFSM6AAAAAA5LDQQLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBTGM3DONRRG4. You are receiving this because you authored the thread.Message ID: @.***>

[dpmurphy]

@.***

From: Tony Hallett @.> Date: Monday, October 2, 2023 at 12:46 PM To: FortuneN/FineCodeCoverage @.> Cc: Daniel Murphy @.>, Author @.> Subject: Re: [FortuneN/FineCodeCoverage] VS2022 - latest version 17.7.4 (Issue #352)

Can you debug the ReportGeneratorUtil SetInitialTheme method to see if the style properties are being set to odd values. Excss cannot be usefully debugged breakpoint failed to bind in an optimized module., but hopefully debugging SetInitialTheme is sufficient.

— Reply to this email directly, view it on GitHubhttps://github.com/FortuneN/FineCodeCoverage/issues/352#issuecomment-1743367617, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABEDFAEINO2B5WFX2DKXSB3X5LVUFAVCNFSM6AAAAAA5LDQQLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBTGM3DONRRG4. You are receiving this because you authored the thread.Message ID: @.***>

[tonyhallett]

I would not bother with the zip files yet as they are executables that have not been executed and cannot be the cause of the exception encountered.

Do visual studio extension nuget dependencies need to be of a specific framework version ? https://devblogs.microsoft.com/visualstudio/arm64-visual-studio-is-officially-here/

Arm64 support for managed developers .NET 6 has had native support for Arm64 from day one, and we are extending native Arm64 support for the .NET Framework in the form of .NET Framework 4.8.1 runtime and SDK. You can now build managed Arm desktop applications using both .NET 7/6, and .NET Framework 4.8.1.

The 17.4 GA release supports Windows Forms, WPF, Win UI 3, Win UI 2 and Universal Windows Platform (UWP). Support for.NET MAUI will be available in a future Visual Studio preview.

When you start with the Arm64 version of Visual Studio, before rebuilding your application make sure you update references to NuGet packages to their latest versions supporting Arm64. The vast majority of NuGet packages already work on Arm64 with no additional changes needed.

Although this is not mentioned in

Check out this blog post for more details

https://devblogs.microsoft.com/visualstudio/now-introducing-arm64-support-for-vs-extensions/

If it is the case that all dependencies need to be .Net Framwork 4.8.1 then this is an issue.

[dpmurphy]

Do visual studio extension nuget dependencies need to be of a specific framework version ?

I’ve updated all packages to the latest version. It just won’t compile without that step. I’ve checked the dependencies on every installed package and they claim the max required .net is 4.7.2

Has Microsoft a dependency in the system for 4.8.1, I can’t tell but even their installed packages declare the 4.7.2 dependency.

The documentation says you must install this package….Microsoft.VSSDK.BuildTools -Version 17.7.2196 This package install causes warnings in the build output that doesn’t exist otherwise….

Rebuild started... Restored C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage\ReportGeneratorPlugins\ReportGeneratorPlugins.csproj (in 5 ms). Restored C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage\FineCodeCoverage2022\FineCodeCoverage2022.csproj (in 168 ms). Restored C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage\FineCodeCoverage\FineCodeCoverage.csproj (in 168 ms). 1>------ Rebuild All started: Project: ReportGeneratorPlugins, Configuration: Debug Any CPU ------ 1>ReportGeneratorPlugins -> C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage\ReportGeneratorPlugins\bin\Debug\netstandard2.0\ReportGeneratorPlugins.dll 2>------ Rebuild All started: Project: FineCodeCoverage2022, Configuration: Debug Any CPU ------ 2> FineCodeCoverage2022 -> C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage\FineCodeCoverage2022\bin\Debug\FineCode 2> Coverage2022.dll 2> FineCodeCoverage2022 -> C:\Users\dan_p\source\repos\Not Used\FineCodeCoverage\FineCodeCoverage2022\bin\Debug\FineCode 2> Coverage2022.vsix 2>C:\Users\dan_p.nuget\packages\microsoft.vssdk.compatibilityanalyzer\17.7.2196\build\Microsoft.VsSDK.CompatibilityAnaly 2>zer.targets(36,5): warning VSIXCompatibility1001: The extension is incompatible with the targeted version of Visual Stu 2>dio. More info at https://aka.ms/ExtensionSdkErrors. 2>C:\Users\dan_p.nuget\packages\microsoft.vssdk.compatibilityanalyzer\17.7.2196\build\Microsoft.VsSDK.CompatibilityAnaly 2>zer.targets(36,5): warning VSIXCompatibility1001: Following references are incompatible. 2>C:\Users\dan_p.nuget\packages\microsoft.vssdk.compatibilityanalyzer\17.7.2196\build\Microsoft.VsSDK.CompatibilityAnaly 2>zer.targets(36,5): warning VSIXCompatibility1001: Microsoft.VisualStudio.TestWindow.Interfaces.dll -> Microsoft.VisualS 2>tudio.Shell.Interop 2>C:\Users\dan_p.nuget\packages\microsoft.vssdk.compatibilityanalyzer\17.7.2196\build\Microsoft.VsSDK.CompatibilityAnaly 2>zer.targets(36,5): warning VSIXCompatibility1001: Microsoft.VisualStudio.Web.BrowserLink.12.0.dll -> envdte ========== Rebuild All: 2 succeeded, 0 failed, 0 skipped ========== ========== Rebuild started at 8:04 AM and took 10.705 seconds ==========

This maybe the crux of the problem.

Dan.

From: Tony Hallett @.> Date: Wednesday, October 4, 2023 at 6:33 AM To: FortuneN/FineCodeCoverage @.> Cc: Daniel Murphy @.>, Author @.> Subject: Re: [FortuneN/FineCodeCoverage] VS2022 - latest version 17.7.4 (Issue #352)

I would not bother with the zip files yet as they are executables that have not been executed and cannot be the cause of the exception encountered.

Do visual studio extension nuget dependencies need to be of a specific framework version ? https://devblogs.microsoft.com/visualstudio/arm64-visual-studio-is-officially-here/

Arm64 support for managed developers .NET 6 has had native support for Arm64 from day one, and we are extending native Arm64 support for the .NET Framework in the form of .NET Framework 4.8.1 runtime and SDK. You can now build managed Arm desktop applications using both .NET 7/6, and .NET Framework 4.8.1.

The 17.4 GA release supports Windows Forms, WPF, Win UI 3, Win UI 2 and Universal Windows Platform (UWP). Support for.NET MAUI will be available in a future Visual Studio preview.

When you start with the Arm64 version of Visual Studio, before rebuilding your application make sure you update references to NuGet packages to their latest versions supporting Arm64. The vast majority of NuGet packages already work on Arm64 with no additional changes needed.

Although this is not mentioned in

Check out this blog post for more details

https://devblogs.microsoft.com/visualstudio/now-introducing-arm64-support-for-vs-extensions/

If it is the case that all dependencies need to be .Net Framwork 4.8.1 then this is an issue.

— Reply to this email directly, view it on GitHubhttps://github.com/FortuneN/FineCodeCoverage/issues/352#issuecomment-1746599666, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABEDFAAIEDBNZ6WEPFQFTJLX5U3PVAVCNFSM6AAAAAA5LDQQLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBWGU4TSNRWGY. You are receiving this because you authored the thread.Message ID: @.***>

[tonyhallett]

The extension is incompatible with the targeted version of Visual Studio

Have you updated the vsix to match the version of the sdk that you have updated to ?

[dpmurphy]

Yes.

@.***

From: Tony Hallett @.> Date: Wednesday, October 4, 2023 at 8:39 AM To: FortuneN/FineCodeCoverage @.> Cc: Daniel Murphy @.>, Author @.> Subject: Re: [FortuneN/FineCodeCoverage] VS2022 - latest version 17.7.4 (Issue #352)

The extension is incompatible with the targeted version of Visual Studio

Have you updated the vsix to match the version of the sdk that you have updated to ? [image]https://user-images.githubusercontent.com/11292998/272576196-af9c6fd3-118d-4dda-a7ee-55337b31f76c.png

— Reply to this email directly, view it on GitHubhttps://github.com/FortuneN/FineCodeCoverage/issues/352#issuecomment-1746795332, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABEDFAFJSHIDNPD27XEYT6TX5VKJJAVCNFSM6AAAAAA5LDQQLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBWG44TKMZTGI. You are receiving this because you authored the thread.Message ID: @.***>

[tonyhallett]

As mentioned. You can copy the test window interfaces used. No idea where the webbrowserlink issue is coming from.

[tonyhallett]

I don't think resolution of these warnings will effect the Excss issue or the BadImageException.

[tonyhallett]

Closing as this is not an issue with FCC as we do not support ARM.
Until I have the hardware to build myself, ARM will continue to be unsupported. https://github.com/FortuneN/FineCodeCoverage/issues/322

If you do get your fork to run successfully please let us know.