Debug settings -> Failed to load page

[PiN]

Hello!

We suddenly started seeing an error message in VisualGDB Project Properties window, in “Debug settings” pane (see attached screenshot).

The exception says:

System.Windows.Markup.XamlParseException: Provide value on 'System.Windows.Baml2006.TypeConverterMarkupExtension' threw an exception. ---> System.FormatException: NormalWithoutLocalHost is not a valid value for RenderingMode. ---> System.ArgumentException: Requested value 'NormalWithoutLocalHost' was not found.
at System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult)
at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)
at System.ComponentModel.EnumConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
--- End of inner exception stack trace ---
at System.ComponentModel.EnumConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.CallProvideValue(MarkupExtension me, IServiceProvider serviceProvider)
--- End of inner exception stack trace ---
at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
at VisualGDB.Common_GUI.WPF.Property_pages.EmbeddedDebugPropertyPage..ctor()
at VisualGDB.Common_GUI.WPF.Property_pages.EmbeddedDebugPropertyPage.Stub.CreatePropertyPage(tl2 newProjectContext, c81 ctx2)
at VisualGDB.Common_GUI.Configuration_editors.ProjectPropertiesEditModel.q1.CreatePageIfMissing(tl2 b, vg a, ProjectPropertiesEditModel c, c81 d)
at VisualGDB.Common_GUI.Configuration_editors.ProjectPropertiesEditModel.t(IOnDemandPropertyPage a)

Is there something wrong on our side? Can it be fixed?
Thanks!

Attachments:

You must be logged in to view attached files.

[support]

Hi,

Please try updating to the latest VisualGDB 6.0 Beta 2. If the problem persists, please let us know.

[hikingDev]

Hi,

I have upgraded to Version 6.0 (Beta 2, build 4949) and the same Stacktrace given by the Thread creator still appears when opening “Debug settings”.

 

[support]

Strange. Could you please share a screenshot of the Help->About VisualGDB window?

[hikingDev]

Sure. I have attached both, the screenshot of the About page and the Debug settings error.

 

 

Attachments:

You must be logged in to view attached files.

[support]

Thanks for verifying your license. This problem would normally be caused by a bug in the .Net image rendering logic that is triggered by some color profiles, although we have fixed it in the latest 6.0 branch.

You can try reverting to the default color profile via Windows Color Management -> Advanced -> Device Profile = System Default.

If it doesn’t help, please try creating a new project selecting the “full-custom” debug mode in the wizard. Does it show the Debug Settings page correctly? If yes, does switching to OpenOCD immediately show an exception?

[hikingDev]

Neither of the approaches helped.
The Device profile in Windows Color Management was already set to System Default.
Strangely using VisualGDBs Project wizard crashed right at the beginning with the following exception:

VisualGDB version: 6.0.2.4949
------------------ System.Windows.Markup.XamlParseException ------------------
System.Windows.Markup.XamlParseException: Provide value on 'System.Windows.Baml2006.TypeConverterMarkupExtension' threw an exception. ---> System.FormatException: NormalWithoutLocalHost is not a valid value for RenderingMode. ---> System.ArgumentException: Requested value 'NormalWithoutLocalHost' was not found.
at System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult)
at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)
at System.ComponentModel.EnumConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
--- End of inner exception stack trace ---
at System.ComponentModel.EnumConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.CallProvideValue(MarkupExtension me, IServiceProvider serviceProvider)
--- End of inner exception stack trace ---
at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
at VisualGDB.WPF.Wizards.Embedded.EmbeddedDebugSettingsPage..ctor()
at nu1.d(k6 b, String c, String a)
at nu1.DoRunWizardOrThrowException(f51 a, String c, String b)
at k91`1.Execute(Object e, IntPtr c, Object[]& a, Object[]& d, wizardResult& b)
trace=[System.Windows.Markup.XamlReader.RewrapException:0, System.Windows.Markup.WpfXamlLoader.Load:260, System.Windows.Markup.WpfXamlLoader.LoadBaml:20, System.Windows.Markup.XamlReader.LoadBaml:302, VisualGDB.WPF.Wizards.Embedded.EmbeddedDebugSettingsPage..ctor:12, nu1.d:206, nu1.DoRunWizardOrThrowException:40, k91`1.Execute:210]
------------------ Inner exception ------------------
------------------ System.FormatException ------------------
System.FormatException: NormalWithoutLocalHost is not a valid value for RenderingMode. ---> System.ArgumentException: Requested value 'NormalWithoutLocalHost' was not found.
at System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult)
at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)
at System.ComponentModel.EnumConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
--- End of inner exception stack trace ---
at System.ComponentModel.EnumConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.CallProvideValue(MarkupExtension me, IServiceProvider serviceProvider)
trace=[System.ComponentModel.EnumConverter.ConvertFrom:191, MS.Internal.Xaml.Runtime.ClrObjectRuntime.CallProvideValue:8]
------------------ Inner exception ------------------
------------------ System.ArgumentException ------------------
System.ArgumentException: Requested value 'NormalWithoutLocalHost' was not found.
at System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult)
at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)
at System.ComponentModel.EnumConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
trace=[System.Enum.TryParseEnum:397, System.Enum.Parse:16, System.ComponentModel.EnumConverter.ConvertFrom:18]

 

I then went on to uninstall VisualGDB completely and reinstalled it.
This didn’t help either. (Visual Studio 2022)

Then i proceeded and opened the Project with Visual Studio 2019 and indeed, the Debug Settings are available.
I changed the Debugging mode and went back to open the project with Visual Studio 2022.
The Error in Debug settings persists (VS 2022).

[cborn]

I can confirm this problem, I’ve just come back to a VisualGDB project using VS2022 and I get the “Failed to load page” message for both “Project Settings” and “Debug Settings”.

I updated VisualGDB to version 6.0 (Beta 2, build 4949) but the problem remains.

Opening the same project with VS2019 works correctly.

My VS2022 has updated since the last time I used it with this project, currently it is at version 17.7.4.

Details on the failed Project Settings page are:

System.Windows.Markup.XamlParseException: Provide value on 'System.Windows.Baml2006.TypeConverterMarkupExtension' threw an exception. ---> System.FormatException: BuildMachineSelector is not a valid value for RenderingMode. ---> System.ArgumentException: Requested value 'BuildMachineSelector' was not found.
at System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult)
at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)
at System.ComponentModel.EnumConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
--- End of inner exception stack trace ---
at System.ComponentModel.EnumConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.CallProvideValue(MarkupExtension me, IServiceProvider serviceProvider)
--- End of inner exception stack trace ---
at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
at VisualGDB.Common_GUI.WPF.Property_pages.Project.LinuxProjectPropertyPage..ctor()
at VisualGDB.Common_GUI.WPF.Property_pages.Project.LinuxProjectPropertyPage.Stub.CreatePropertyPage(az2 newProjectContext, jg2 ctx2)
at VisualGDB.Common_GUI.Configuration_editors.ProjectPropertiesEditModel.t.CreatePageIfMissing(az2 a, oi2 d, ProjectPropertiesEditModel b, jg2 c)
at VisualGDB.Common_GUI.Configuration_editors.ProjectPropertiesEditModel.c2(IOnDemandPropertyPage a)

 

 

[support]

Thanks for confirming this. It looks like a rather strange assembly load issue. Please try this build: VisualGDB-6.0.3.4993.msi

If the problem persists, please click Help->About VisualGDB while holding the Shift key. The About window will show one extra button called “Troubleshoot Assembly Errors”.

Once you click on it, VisualGDB will generate a detailed report showing possible conflicts. Please attach the report together with the updated call stack from the error message, and we will look further into it.

[cborn]

The updated version didn’t fix the problem, requested details attached.

Regards,

David

System.Windows.Markup.XamlParseException: Provide value on 'System.Windows.Baml2006.TypeConverterMarkupExtension' threw an exception. ---> System.FormatException: BuildMachineSelector is not a valid value for RenderingMode. ---> System.ArgumentException: Requested value 'BuildMachineSelector' was not found.
at System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult)
at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)
at System.ComponentModel.EnumConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
--- End of inner exception stack trace ---
at System.ComponentModel.EnumConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.CallProvideValue(MarkupExtension me, IServiceProvider serviceProvider)
--- End of inner exception stack trace ---
at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
at VisualGDB.Common_GUI.WPF.Property_pages.Project.LinuxProjectPropertyPage..ctor()
at VisualGDB.Common_GUI.WPF.Property_pages.Project.LinuxProjectPropertyPage.Stub.CreatePropertyPage(pu newProjectContext, cv ctx2)
at VisualGDB.Common_GUI.Configuration_editors.ProjectPropertiesEditModel.x.CreatePageIfMissing(pu b, hp3 a, ProjectPropertiesEditModel c, cv d)
at VisualGDB.Common_GUI.Configuration_editors.ProjectPropertiesEditModel.d(IOnDemandPropertyPage a)

Attachments:

You must be logged in to view attached files.

[cborn]

Quick follow-up, I just upgraded Visual Studio from 17.7.4 to 17.7.6, and now both the “Project Settings” and “Debug Settings” dialog pages are displaying correctly again.

[hikingDev]

For me the issue persists:

Visual Studio 17.7.6

VisualGDB version 6.0 (Beta 3, build 4993)

Attached the AssemblyLoadReport and the about dialog screnshots.

Attachments:

You must be logged in to view attached files.

[support]

@hikingDev

Thanks, the assemblies on your machine do match our test setup, however, it looks like you are using a couple of extra VS extensions that could be interfering with the WPF.

Please try disabling all other extensions via the Extensions->Manage Extensions command in Visual Studio. If it solves the problem, please try checking if enabling a particular extension triggers the problem, so that we could try installing it on our side and reproducing this.

Edit: for what it’s worth, you can try this build: VisualGDB-6.0.3.4994.msi. It has RemoteHostSelector.Mode renamed to RemoteHostSelector.HostSelectorMode, so if the old name was triggering some strange name collision, it should not happen anymore.

[hikingDev]

@support

Thank you for the support. The latest build fixed it!
Before i tried the latest build, i checked which plugin was causing the issue.
Disabling Github Copilot Chat was the root cause. By disabling it, the debug settings worked as expected.

Thanks again!

[support]

Hi,

OK, we’ve done some more investigation. It turns out the CoPilot extension pulls a dependency on the System.Windows.Interop.RenderingMode type, that somehow causes errors when trying to load XAML controls that have any non-dependency property called “Mode”.

There were a couple of more instances of these controls in VisualGDB code base, although they only affected a handful of settings pages.

We have fully resolved the issue to the following build: VisualGDB-6.0.4.5041.msi​. We renamed all conflicting properties and added an internal check for such conflicts to our build process.

[Author]

Posts