I have a project developed in VB.NET 1.1 (using VS 2003). The project has forms developed using the DataForm wizard (Connecting to Access Database, having a dataset and couple of adapter as automatically generated through the wizard - See attached screenprint "Original Form In VS 2003.PNG").

I converted the project to VB.NET 2.0 using VS2005 Express Edition.

Now when I tried to open the form from the converted project in Designer mode in VS2005 Express Edition, the form is not displayed, instead a text line similar to below (also see the screenprint "Converted Form To VS2005 Express Edition.png" attached below) is shown

<html><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8"><title></title><style>.ErrorStyle { font-family: tahoma; font-size: 11 pt; text-align: left}.DetailsStyle { font-family: tahoma; font-size: 10pt; text-align: left;text-indent: 0; word-spacing: 0; line-height: 100%; float: left; margin-top: 0; margin-bottom: 0}.StackStyleVisible { font-family: tahoma; font-size: 10pt; text-align: left; margin-left: 20; text-indent: 0}.StackStyleHidden { display:none; font-family: tahoma; font-size: 10pt; text-align: left; margin-left: 20; text-indent: 0}</style></head><body><DIV class="DetailsStyle" width="100%"><table border="0" width="100%" id="table1" height="100%" cellspacing="0" cellpadding="0"><tr><td height="40" bgcolor="#FF9999" width="8%" style="letter-spacing: 0" align="center"><img border="0" src="C:\Documents and Settings\Umesh\Local Settings\Temp\13622E.tmp" width="35" height="35" alt="ErrorImage" ></td><td height="40" bgcolor="#FF9999" width="91%" style="vertical-align: top; letter-spacing: 0" align="left"><b><font size="2" face="Arial" fontsize="70%">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.</font><font size="2" face="Arial"></font></b></td></tr><tr><td colspan="2" align="left" valign="top"><DIV id="div1" class="ErrorStyle" width="100%"><span style="font-weight: 600"><br>Object reference not set to an instance of an object. </span><br><a href="" id="details0">Hide</a><font color="#0000FF">&nbsp;&nbsp;&nbsp;&nbsp</font></DIV> </td> </tr> <tr><td colspan="2" align="left" valign="top"><DIV id="div20" class="StackStyleVisible" width="100%"><br>   at CustomBaseForm.CommonFunctions.GetApplicationFont(OleDbConnection OleDbConnection1)<br>   at CustomBaseForm.BaseForm.frmSupplierDetails_Load(Object sender, EventArgs e)<br>   at System.Windows.Forms.Form.OnLoad(EventArgs e)<br>   at System.Windows.Forms.Form.OnCreateControl()<br>   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)<br>   at System.Windows.Forms.Control.CreateControl()<br>   at System.Windows.Forms.Control.SetVisibleCore(Boolean value)<br>   at System.Windows.Forms.Form.SetVisibleCore(Boolean value)<br>   at System.Windows.Forms.Control.set_Visible(Boolean value)<br>   at System.Windows.Forms.Design.DesignerFrame.Initialize(Control view)<br>   at System.Windows.Forms.Design.DocumentDesigner.Initialize(IComponent component)<br>   at System.Windows.Forms.Design.FormDocumentDesigner.Initialize(IComponent component)<br>   at System.ComponentModel.Design.DesignerHost.AddToContainerPostProcess(IComponent component, String name, IContainer containerToAddTo)<br>   at System.ComponentModel.Design.DesignerHost.Add(IComponent component, String name)<br>   at System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesignerHost.CreateComponent(Type componentType, String name)<br>   at System.ComponentModel.Design.Serialization.DesignerSerializationManager.CreateInstance(Type type, ICollection arguments, String name, Boolean addToContainer)<br>   at System.ComponentModel.Design.Serialization.DesignerSerializationManager.System.ComponentModel.Design.Serialization.IDesignerSerializationManager.CreateInstance(Type type, ICollection arguments, String name, Boolean addToContainer)<br>   at System.ComponentModel.Design.Serialization.TypeCodeDomSerializer.Deserialize(IDesignerSerializationManager manager, CodeTypeDeclaration declaration)<br>   at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager manager)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager)<br>   at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.DeferredLoadHandler.Microsoft.VisualStudio.TextManager.Interop.IVsTextBufferDataEvents.OnLoadCompleted(Int32 fReload)</DIV></td></tr></table></div></body></html>

When I execute the converted project (Application), it executes perfectly and the form is also shown correctly.

How can I open the form in the designer so that I can modify the same?

Thanks in advance!!

Edited by __avd: Added [code] tags. For easy readability, always wrap programming code within posts in [code] (code blocks).

Attachments Converted_Form_To_VS_2005_Express_Edition.PNG 57.07 KB Original_Form_In_VS_2003.PNG 53.24 KB
7 Years
Discussion Span
Last Post by ukshir

>How can I open the form in the designer so that I can modify the same?

Unfortunately, you can't do anything.


So does that mean I cannot upgrade my application from .Net1.1 to .Net 2.0 anyway?? That's not good. I was planning to move my applications to .Net 2.0 so as to have more functionality included in the Project.


Please check the code of frmdetailsdesign.vb of application written in 1.1 (old one).

I am sorry but I didn't get what you are suggesting?? :confused: :confused:


Now there is some interesting thing regarding VB.NET 1.1 to VB.NET2.0 conversion I came across today. When I converted the same project from 1.1 to 2.0 on a machine where I have only VS2005(prof) installed the newly converted project is working fine. i.e. I can open the form in the designer and make changes. I dont know how it worked .... I am trying to figure it out and trying to understand what worked in the converted project and what not worked in previos conversion

This article has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.