Hi,

I was working on a simple Winforms C# project. I created a few of TableAdapters using the designer and attached them to datagridviews on my form. After realizing that i did not want one of the tables I went to the XSD designer and deleted it. After that the project still excutes ok but the form designer is unable to display the form in design view I get the following error:

One or more errors encountered while loading the designer. The errors are listed below. Some errors can be fixed by rebuilding your project, while others may require code changes. Clicking on each error will take you to the line of code that caused it. 

I am not looking for a response to this problem (creating prototype, kicking the tires ;-)) but hopefully Microsoft will address this issue with some sort of fix. The designer should probably utilize some referential integiry rules (cascade or restirct) before it allows one to remove items that will cause it not to function properly.

Regards

FredV

FredV -
Thanks for posting this issue on the forums.  Can you log this suggestion with additional details on the Product Feedback(http://lab.msdn.microsoft.com/productfeedback/) site so we can track it internally?

Thanks!
Karen

FredV -
Thanks for posting this issue on the forums.  Can you log this suggestion with additional details on the Product Feedback(http://lab.msdn.microsoft.com/productfeedback/) site so we can track it internally?

Thanks!
Karen

Thishas happened to me also, on more than one occasion.

Sometimes I am able to get around it by editing the designer code and removing the erroneous references.

Other times I wind up having to junk my form and start fresh. And the acceptability of doing that is inversely proportional to the amount of time you've spent customizing it.

So unlike the original poster, I really am looking for a solution to this problem.

I got the same problem when upgrading a functioning projectfrom Visual Studio .NET 2003 to Visual Studio 2005.

The upgrade wizard went through without errors, and the application can be executed normally, but none of my forms can be displayed in designer view.

I even get no error line number, only a line number 0, and a lot of details like:

at System.Resources.Tools.StronglyTypedResourceBuilder.DefineResourceFetchingProperty(String propertyName, String resourceName, ResourceData data, CodeTypeDeclaration srClass, Boolean internalClass, Boolean useStatic)
at System.Resources.Tools.StronglyTypedResourceBuilder.InternalCreate(Dictionary`2 resourceList, String baseName, String generatedCodeNamespace, String resourcesNamespace, CodeDomProvider codeProvider, Boolean internalClass, String[]& unmatchable)
at System.Resources.Tools.StronglyTypedResourceBuilder.Create(IDictionary resourceList, String baseName, String generatedCodeNamespace, String resourcesNamespace, CodeDomProvider codeProvider, Boolean internalClass, String[]& unmatchable)
at System.Resources.Tools.StronglyTypedResourceBuilder.Create(IDictionary resourceList, String baseName, String generatedCodeNamespace, CodeDomProvider codeProvider, Boolean internalClass, String[]& unmatchable)
at Microsoft.VisualStudio.Design.Serialization.ResXGlobalObject.BuildType()
at Microsoft.VisualStudio.Design.Serialization.ResXGlobalObject.GetObjectType()
at Microsoft.VisualStudio.Shell.Design.GlobalType.get_ObjectType()
at Microsoft.VisualStudio.Design.Serialization.ResXGlobalObject.get_Children()
at Microsoft.VisualStudio.Design.Serialization.ResXGlobalObjectProvider.CreateGlobalObjectsForItem(ProjectItem item, GlobalObjectCollection oldObjects, GlobalObjectCollection newObjects, ITypeResolutionService typeResolver)
at Microsoft.VisualStudio.Design.Serialization.ResXGlobalObjectProvider.CreateGlobalObjects(Project project)
at Microsoft.VisualStudio.Design.Serialization.ResXGlobalObjectProvider.GetGlobalObjectsCore(Project project, Type baseType)
at Microsoft.VisualStudio.Shell.Design.GlobalObjectProvider.GetGlobalObjects(Project project, Type baseType)
at Microsoft.VisualStudio.Shell.Design.GlobalObjectService.GetGlobalObjects(Type baseType)
at Microsoft.VisualStudio.Shell.Design.GlobalObjectService.GetGlobalObjects()
at Microsoft.VisualStudio.Design.Serialization.CodeDom.AggregateTypeResolutionService.GetTypeFromGlobalObjects(String name, Boolean throwOnError, Boolean ignoreCase)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.AggregateTypeResolutionService.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.AggregateTypeResolutionService.GetType(String name, Boolean throwOnError)
at System.ComponentModel.Design.Serialization.CodeDomSerializerBase.GetType(ITypeResolutionService trs, String name, Dictionary`2 names)
at System.ComponentModel.Design.Serialization.CodeDomSerializerBase.FillStatementTable(IDesignerSerializationManager manager, IDictionary table, Dictionary`2 names, CodeStatementCollection statements, String className)
at System.ComponentModel.Design.Serialization.TypeCodeDomSerializer.Deserialize(IDesignerSerializationManager manager, CodeTypeDeclaration declaration)
at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager manager)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.DeferredLoadHandler.Microsoft.VisualStudio.TextManager.Interop.IVsTextBufferDataEvents.OnLoadCompleted(Int32 fReload)

I also would really appreciate if Microsoft would fix that asap.

I have encountered this problem too. It seems that it was related to the user controls that I have created. When I created a temporary form and drag the user controls, a messagebox pops up and it tells me the following error:

Failed to create component 'TestControl'. The error message follows: System.NullReferenceException: Object reference not set to an instance of an object at System.Resources.Tools.StronglyTypedResourceBuilder.DefineResourceFetchingProperty(String propertyName, String resourceName, Resource Data, ...

)

The control has the following code:

Option Explicit On

Option Strict On

Public Class testcontrol

Inherits UserControl

Public Function CheckedRectangleF(ByVal x As Single, ByVal y As Single, ByVal width As Single, ByVal height As Single) As RectangleF

Return New RectangleF(x, y, CSng(IIf(width <= 0, 1, width)), CSng(IIf(height <= 0, 1, height)))

End Function

Private Sub testcontrol_Paint(ByVal sender As Object, ByVal e As System.Windows.Forms.PaintEventArgs) Handles Me.Paint

Dim recfBox As RectangleF

Dim lbr As LinearGradientBrush

recfBox = CheckedRectangleF(0, 0, Me.Width - 1, Me.Height - 1)

lbr = New LinearGradientBrush(recfBox, Color.CornflowerBlue, Color.DarkBlue, LinearGradientMode.Vertical)

End Sub

End Class

I get this error everytime I makea change to the .xsd file associated with the dataset used by the application. This is a native VS2005 app (not upgraded from 2003), there are no invalid references, so I'm not sure what is causing this, it is very frustrating because I am prevented from editing the form in design view.

In my case I have to restart VS to clear the errors and get back to editing. The app builds fine, runs fine and works great. That is until I edit the .xsd file again, then the cycle starts over.

Yep I also have this problem.

For me it is because I have a custom component and I have added it to several forms. When I make a change to the custom component the form designer will no longer load.

I may have made a mistake on my custom component ..not sure...but this is a major issue because I have at least 5 forms that won't load at all right now.

Hi, IT-Beratung,

Have you found any solution to your problem. I am having exactly the same problem when upgrading from vs2003 to vs2005. The project was built successfully. But the designer couldn't load the forms. The error I got was like:

at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.EnsureDocument(IDesignerSerializationManager manager)
at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager manager)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.DeferredLoadHandler.Microsoft.VisualStudio.TextManager.Interop.IVsTextBufferDataEvents.OnLoadCompleted(Int32 fReload)

I'd appreciate if anyone can help me to solve this.

Up to now I got no solution to the upgrading problem.

I filed the problem with Microsoft Support, but besides the advise to disable "Localization" in trhe forms before upgrading, which did not solve the problen, I got no further feedback from them. Seems as if Microsoft is not interested in helping to solveits client's problems!!

I finally found a solution (without any meaningful help from Microsoft Support - they urgently should improve their service to customers!!!!)

a) convert the old .resx files to .resources files via ResGen - after this you will be able to see your forms in Desiger mode again, but you cannot change or amend the resources

b) remove the old .resx files from your project

c) convert the (new) .resources files to new .resx files again with ResGen

d) remove the .resources files from you project and include the new .resx files

All should be functioning now.

I hope this helps also the others who had a similar problem.

I wonder however why this simple procedure cannot be performed by the "upgrade wizard" when opening an old .NET 2003 project the first time in VS 2005!!

I found this solution on some website, cannot find it now.

Close all the desinger forms in Visual Studio. Close Visual Studio. Delete all the 'bin' and 'obj' files of all projects in your solution.

Relaunch Visual studio and load the project, rebuild it and you can now should be able to see the designers.

As one evaluation step in our project I also tried to convert the VS 2003 project to VS 2005. I faced similar problems and tried the Sync Fusion Resx Converter as well as your solution. The Sync Fusion Converter malfunctions because of custom controls we developed for the VS 2003 project, Microsoft Visual Studio can't open the form and therefore cannot convert the resources and a manual conversion with the ResGen like you described works to view the form but when I try to change something the designer malfunctions again.

At some parts of the project we also needed to use Active X controls in the form. Somehow it isn't possible any more to add those controls to the new toolbar which might become another problem.

Isn't there some schema for the old and new resx - file format and a good professional converter for that? It seems that everybody creates his own small solutions now and the problems reappear. The msdata schema seems to be not accessable in the internet, is that true?

I have not found any new fixes related to this migration topic in the SP 1 of MS Visual Studio 2005. Does anyone know how to convert a bigger project?

Some very easy forms of the VS 2003 designer get converted by Microsoft's new designer but most of the time it just malfunctions with more complex forms.

Thank you all,

Bernhard

I have a custom component that I use on about 30 forms.

When I make a change to the custom component I receive this white screen of death on all of my forms that use the custom component.

Object of Type 'my type' cannot be converted to type 'same exact type'

this is reallllllllly bad.

If I close visual studio and re-open it..everything goes back to working again.

http://geekswithblogs.net/rupreet/archive/2005/12/14.aspx

with this Url it's Ok now for me.............................

bye from FRANCE

Hi IT-Beratung:

I have tried the way by using resgen.exe to convert old .resx file but still not working correctly. Do you have any other ways to fix the problem?

Thank you

Hi,

If you add a class in the windowform(forexamplefrmMain.cs), add the class below the form. because the IDE will process the winform first, that was a fix for me.

System.*

namespace EZPilotCouplerTest

public partial class frmMain : Form
{

} //end frmMain

public class SomeClass
{

}//end SomeClass

Me too faced the same problem.

I used to close the design window and open it by right-click the file from "Solution Explorer" and select "View Design" instead of using short-cut keys. This works for me several times. But if the design really has some bug, then you've to remove/edit the code manually to overcome this issue.

Regards,

Arunagiri GT

I have tried all the suggestions made on the previous posts, and unfortunately, none of them worked.

I just removed the form components which initialization depends on Resources content from InitializeComponent() to the form constructor section, right before the InitializeComponent() call.

Something like this:

For example, we have this code, at the Form1.Designer.cs file:

partial class Form1

{

...

private void InitializeComponent()

Although the resources items are not loaded, the Forms Designer loads the form. This is not a good solution though, but I found better than having nothing to see when I need to do some forms modeling.

This solution works for the designer - I will definitely try it for the same error when its related to a dataset. Last time, I had to revert to backup copy which wasted a lot of code.

Thank You!

I cant see my forms in Designer mode. I wanna try the solution u provided, but what's ResGen?? Howtoconvert the old .resx files to .resources files via ResGen?? I directly change the extensions from.resx to .resources, is it correct?

Hi,

I found this thread while searching for why I suddenly couldn't openseveral forms in design mode any more, so now that I havefound thesolution, I thought I'd mention it here in case somebody else accidentally does what I did.

I found that the cause, in my cases, was that I had inadvertently used a custom property in the "Load" event BEFORE I had initialised it anywhere. The forms ran ok, because I was initialising the property in a custom overloaded "New" proc, which all my calls to those formswere using, but the designer was,rather obviously in hindsight, instantiating the form with the "New" proc that had no parameters, and consequently not initialising the propertybefore attempting to use it.

The error message said something about "obejct not set to instantiated instance", or something similar, which once I discovered the problem became blindingly obvious, lol.

This may not be the answer those of you who are having problems after converting from one version of .NET to another, but it was what I needed, so I hope it will be of use to someone else as well..

Yann

Hi,

I tried turning off indexing, and deleting the obj and bin folders (but only of the project containing the problematic form), and converting the .resX files in the affected project to .resources files and back, with no effect. I found that I had inserted code to add an event handler for one of my classes between similar code for controls on the form. When I moved this code to the form constructor I could enter the designer without the error. I don't know if the other things I did contributed to the fix or not, but when I moved that code it worked.

==

Richard Lewis Haggard

Dear All,

While converting VS 2003 project into VS 2005, Im not able to open forms in form designer and i get this following warning message.Can anybodyhelp me in this regard? This is C# device application.

Thanks,

Ansar

Hello,

I just installed VS 2005 standard on my windows xp computer. and I get the following error when I try to look at my forms.

One or more errors encountered while loading the designer. The errors are listed below. Some errors can be fixed by rebuilding your project, while others may require code changes.

No more data is available.
Hide

at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str)
at Microsoft.Win32.RegistryKey.GetValueNames()
at Microsoft.VisualStudio.Shell.Design.WindowPaneProviderService.AppendWindowPanes(RegistryKey parentKey, ArrayList windowPanes)
at Microsoft.VisualStudio.Shell.Design.WindowPaneProviderService.GetRegisteredPanes(String extension)
at Microsoft.VisualStudio.Shell.Design.WindowPaneProviderService.CreateWindowPane(DesignSurface surface)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.DeferrableWindowPaneProviderService.CreateWindowPane(DesignSurface surface)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.DeferrableWindowPaneProviderService.DeferredWindowPane.EnsurePane()

I have tried the indexing thing but it didnt work for me.anyone have any ideas?

shut down visual studio and re-open it...the problem should go away and you should be able to view your forms again.

I was having the same problem for 2 reasons

1) I removed the default constructor from the user control and I added a few the expect parameters, therefore when I added the control VS wasn't able to create the control (...new UserControl()....) in the partial class.

2) In the constructor I was trying to read from the app.config file (for more information about this problem please check the following link http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2796462&SiteID=1) and to solve this problem I used the Setings file.

Good luck

Hi,

can you please contact me to my mail?

odedyh@walla.co.il

thanks,

Oded

Have you read the rest of this thread? It seems like it's different strokes for different folks. In my case, I have a reference to Interop.WMPLib.dll, which it says it can't find, although it is alive and well (well, my app works). I think I get the error after I build the first time after opening VS, or maybe it's the first time I close and reopen it after building. Anyway, what I do is remove and then re-add the reference to this DLL. I may have to rebuild after that, I haven't been working on it for a while. I can then usually keep VS opened and it seems to keep working. Your mileage will probably vary-- the details of your error are different than mine, so as I said, read the rest of the thread.

The above instructions worked for me. Thank you!

This worked for me! Thanks!!

Hi ev1,
Just see the warnings after rebuildon the file and u will get hint that where u r doing worng .

Regards,
Sameeullah Daris