cborn

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Debug settings -> Failed to load page #34922
    cborn
    Participant

    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.

    in reply to: Debug settings -> Failed to load page #34920
    cborn
    Participant

    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.
    in reply to: Debug settings -> Failed to load page #34914
    cborn
    Participant

    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)

     

     

Viewing 3 posts - 1 through 3 (of 3 total)