Hi!
I moved my VB6 to VB.NET upgrade project to a new machine. I can compile the application (with many warnings), but I cannot open some forms in the Designer. It says:
And the first Call stack says:
At first I suspected the cause to be in "grid As AxDDSharpGridOLEDB2U.AxSGGrid", because this is the only visual element that differs from the forms which I can open. But even commenting out every use of this grid in the form.Designer.vb file kept the Call Stack from above. In the Error List those errors are listed as Messages and the referenced line ir 0 and column is 0.
While there are still many warnings in the error list, I believe the Designer cannot open the form due to some other issue, because no other of the warnings refers to the form.Desiger.vb file.
I get this problem on two machines, one Win 8 with VB Express 2008 and the other with Win 7 and VB Express 2012. Tomorrow I will try to comment out step by step everything on the form, maybe this will reveal the problem.
I moved my VB6 to VB.NET upgrade project to a new machine. I can compile the application (with many warnings), but I cannot open some forms in the Designer. It says:
Code:
To prevent possible data loss before loading the designer, the following errors must be resolved: Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))Code:
1. Hide Call Stack
at System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance(Guid& clsid, Object punkOuter, Int32 context, Guid& iid)
at System.Windows.Forms.AxHost.CreateInstanceCore(Guid clsid)
at System.Windows.Forms.AxHost.CreateInstance()
at System.Windows.Forms.AxHost.GetOcxCreate()
at System.Windows.Forms.AxHost.set_Site(ISite value)
at System.ComponentModel.Container.Add(IComponent component, String name)
at System.ComponentModel.Design.DesignerHost.PerformAdd(IComponent component, String name)
at System.ComponentModel.Design.DesignerHost.System.ComponentModel.Design.IDesignerHost.CreateComponent(Type componentType, String name)
at System.ComponentModel.Design.Serialization.DesignerSerializationManager.CreateInstance(Type type, ICollection arguments, String name, Boolean addToContainer)
at System.ComponentModel.Design.Serialization.DesignerSerializationManager.System.ComponentModel.Design.Serialization.IDesignerSerializationManager.CreateInstance(Type type, ICollection arguments, String name, Boolean addToContainer)
at System.ComponentModel.Design.Serialization.CodeDomSerializerBase.DeserializeInstance(IDesignerSerializationManager manager, Type type, Object[] parameters, String name, Boolean addToContainer)
at System.ComponentModel.Design.Serialization.ComponentCodeDomSerializer.DeserializeInstance(IDesignerSerializationManager manager, Type type, Object[] parameters, String name, Boolean addToContainer)
at System.ComponentModel.Design.Serialization.CodeDomSerializerBase.DeserializeExpression(IDesignerSerializationManager manager, String name, CodeExpression expression)
at System.ComponentModel.Design.Serialization.CodeDomSerializer.DeserializeStatementToInstance(IDesignerSerializationManager manager, CodeStatement statement)
at System.ComponentModel.Design.Serialization.CodeDomSerializer.Deserialize(IDesignerSerializationManager manager, Object codeObject)
at System.Windows.Forms.Design.ControlCodeDomSerializer.Deserialize(IDesignerSerializationManager manager, Object codeObject)
at System.ComponentModel.Design.Serialization.TypeCodeDomSerializer.DeserializeName(IDesignerSerializationManager manager, String name, CodeStatementCollection statements)While there are still many warnings in the error list, I believe the Designer cannot open the form due to some other issue, because no other of the warnings refers to the form.Desiger.vb file.
I get this problem on two machines, one Win 8 with VB Express 2008 and the other with Win 7 and VB Express 2012. Tomorrow I will try to comment out step by step everything on the form, maybe this will reveal the problem.