Visual Studio 2017 XSD descriptor error

I get the following error if I try to open the .xsd file or create a new .net 3.5 project in Visual Studio 2017 and it worked fine before reinstalling windows and updating to visual studio 2017.

This is similar to .net 3.5 as I opened another project which 4.0 and its .xsd was open in design.

To prevent possible data loss before loading the constructor, you should fix the following errors:

The value cannot be null. name: instance parameter

 Instances of this error (1)  

      

  • Hide the call stack at System.ComponentModel.TypeDescriptor.AddAttributes (Object Instance, Attribute []) at Microsoft.VisualStudio.Design.VSDesignSurface.CreateDesigner (IComponent Component, Boolean rootDesigner) (IComponent Component, Boolean rootDesigner) by System.ComponentModel.Design.DesignerHcess string name, IContainerToAddTo container) to System.ComponentModel.Design.DesignerHost.PerformAdd (IComponent component, string name) to System.ComponentModel.Design.DesignerHost.Add (IComponent component, String name) to System.ComponentModel.Container.Add (ICponentModel.Container.Add (ICponentModel.Container.Add component) in Microsoft.VSDesigner.DataSource.Designer.DataSourceDesignerLoader.HandleLoad (IDesignerSerializationManager serializationManager) in Microsoft.VSDesigner.DesignerFramework.BaseDesignerLoader.PerformLoad (IDesignerSerializationManager.DesignerFramework.BaseDesignerLoader.Microsoft.VisualStudio.TextManager.Interop.IVsTextBufferDataEvents.OnLoadCompleted (Int32 fReload)

Error screen link

+3


source to share


2 answers


Hy! Set up target project structure: 4.6 (Right click on ProjectName / Property Pages / Build / Target Framework ---> 4.6) I try and it works.



+1


source


I'm observing the same symptoms you describe and, as suggested by Tibi , also found that changing the Target Framework to 4.6 (via Website โ†’ Start Options โ†’ Build for ASP.NET projects) worked for projects where that was feasible.

I found two open issues for this behavior on the Visual Studio Developer Community website:



Also there is no solution (other than Target Framework 4.6 workaround) and official feedback after more than 6 months.

+1


source







All Articles