locked
Unanble to open .xsd file in VS 2008. RRS feed

  • Question

  • In Visual Studio 2008 when i open .xsd file (XSD Editor)  I am getting following error message. beacus of this I am not able to open any .xsd file but this file opens in Visual Studio 2005  very well. I also reinstalled VS 2008 to solve this issue. but no luck.

     

    An unexpected error has occurred.

    Source : Microsoft.VSDesigner

    Error Code : 61002

     

    Call Stack :

     

    at Microsoft.VSDesigner.Data.ProviderManager.GetVsProvider(String invariantName, String connectionString, Boolean encrypted)
    at Microsoft.VSDesigner.Data.ProviderManager.GetVsDataSource(String invariantName, String connectionString, Boolean encrypted)
    at Microsoft.VSDesigner.Data.ConnectionString..ctor(String providerName, String connectionString)
    at Microsoft.VSDesigner.DataSource.DesignConnection.Microsoft.VSDesigner.DataSource.IDataSourceInitAfterLoading.InitializeAfterLoading()
    at Microsoft.VSDesigner.DataSource.DataSourceXmlSerializer.InitializeObjects()
    at Microsoft.VSDesigner.DataSource.DesignDataSource.ReadXmlSchema(DataSourceXmlTextReader xmlReader)
    at Microsoft.VSDesigner.DataSource.DesignDataSource.ReadXmlSchema(TextReader textReader)
    at Microsoft.VSDesigner.DataSource.Designer.DataSourceSerializationService.DeserializeToDataSource(String filePath, Object serializationData)
    at Microsoft.VSDesigner.DataSource.ProjectDataSourceDescriptor.LoadDataSource()
    at Microsoft.VSDesigner.DataSource.ProjectDataSourceDescriptor.Init(IServiceProvider provider, IVsHierarchy primaryHierarchy, UInt32 primaryItemId, Object primaryDocDataObject, UInt32 docCookie, IVsInvisibleEditor invisibleEditor, IDesignerHost host)
    at Microsoft.VSDesigner.DataSource.ProjectDataSourceStorage.EnsureInvisibleEditor(ProjectItem dsProjectItem, Boolean ensureWritable, Boolean createInvisibleEditor, Boolean getUIInfo)
    at Microsoft.VSDesigner.DataSource.ProjectDataSourceStorage.GetDataSourceInternal(Object caller, ProjectItem dsProjectItem, Boolean ensureWritable, Boolean createInvisibleEditor, Boolean getUIInfo)
    at Microsoft.VSDesigner.DataSource.Designer.DataSourceDesignerLoader.HandleLoad(IDesignerSerializationManager serializationManager)

     

    Monday, April 7, 2008 5:37 AM

Answers

  • I reinstalled the VS 2008 many times but no luck but i solved the problem my creating my new windows profile.

     

    Tuesday, April 22, 2008 12:03 PM

All replies

  • I reinstalled the VS 2008 many times but no luck but i solved the problem my creating my new windows profile.

     

    Tuesday, April 22, 2008 12:03 PM
  • I know the original post is rather stale, but I found a working solution for a similar problem. I was receiving the vague Error Code 61001 whenever I would try to open any XSD in Visual Studio 2008, which was also tied to the Microsoft.VSDesigner component. To my knowledge I had done nothing that should have caused a VS2008 issue like this--I had merely been working in a straightforward web solution.
    Regardless, After poking around and confirming the error was indeed tied to my VS profile, I tried many things, including:
    • removing/re-adding the XSDs,
    • repairing Visual Studio 2008 via the install CD,
    • attempting to use the Windows system restore utility to go back to before the problems (and of course Windows said it couldn't successfully complete the restore...)
    • removing/renaming windows directories related to VS projects in C:\Documents and Settings\(user)\Local Settings\Application Data\Microsoft
    ...none of which worked.
    Then (after closing out VS) I went to the registry and deleted the entries/folders under HKEY_CURRENT_USER\Software\Microsoft\VSCommon and under HKEY_CURRENT_USER\Software\Microsoft\VisualStudio. Specifically, I removed the 8.0 and 9.0 entries, since I was seemed to have the problems with both VS2005 and VS2008. Upon restarting Visual Studio, it ran me through the 'first time' processes, which means my user profile was completely reset, and my errors were gone.

    Hope this helps--I didn't see much else out there on this error.

    ---

    WiredViews, Inc: Custom web applications
    • Proposed as answer by BigTimpton Tuesday, January 6, 2009 5:20 PM
    Tuesday, January 6, 2009 5:18 PM