Upgrading to .NET

[HighlandJinx]

Just started to upgrade our product from VB6 to .NET.

When the wizard has finished its work i can edit any of my forms in .NET.

When i try to open a form it says that there is no editor available, yet when i upgraded a smaller package earlier, i was able to edit the forms perfectly ok.

Any advice?
Thanks folks.

 

[HighlandJinx]

I have also found that the project doesnt build at all, i think its because of a large error that occurs.

"The ResolveComReference Failed Unexpectadly" is the main heading of the error, followed by a huge list of errors.

Anyone have any ideas about this, or is able to point me in the right direction to getting this fixed?
Im updating from VB6 to VB.NET using Visual Studio 2005.

Thanks.

 

[chrissie1]

resolvecomreference makes me think it is a com object that is ausing the error but without more info we can not help you any further.

Christiaan Baes
Belgium

I just like this --> [Wiggle] [Wiggle]

 

[HighlandJinx]

What kind of info do you need? The full Test of the error is:

Error	59	The "ResolveComReference" task failed unexpectedly.
System.SystemException: The type library importer encountered an error during type verification. Try importing without class members. ---> System.MissingMethodException: Method not found: 'Void VB._PictureBox.set__Default(System.Object)'.
   at System.Reflection.Module.InternalLoadInMemoryTypeByName(String className)
   at System.Runtime.InteropServices.TypeLibConverter.TypeResolveHandler.ResolveEvent(Object sender, ResolveEventArgs args)
   at System.AppDomain.OnTypeResolveEvent(String typeName)
   --- End of inner exception stack trace ---

Server stack trace: 
   at System.Runtime.InteropServices.TypeLibConverter.nConvertTypeLibToMetadata(Object typeLib, AssemblyBuilder asmBldr, ModuleBuilder modBldr, String nameSpace, TypeLibImporterFlags flags, ITypeLibImporterNotifySink notifySink, ArrayList& eventItfInfoList)
   at System.Runtime.InteropServices.TypeLibConverter.ConvertTypeLibToAssembly(Object typeLib, String asmFileName, TypeLibImporterFlags flags, ITypeLibImporterNotifySink notifySink, Byte[] publicKey, StrongNameKeyPair keyPair, String asmNamespace, Version asmVersion)
   at Microsoft.Build.Tasks.TlbReference.GenerateWrapper(ComReferenceWrapperInfo& wrapperInfo)
   at Microsoft.Build.Tasks.ResolveComReference.ResolveComReferenceTlb(ComReferenceInfo referenceInfo, String outputDirectory, String refName, Boolean topLevelRef, ComReferenceWrapperInfo& wrapperInfo)
   at Microsoft.Build.Tasks.ResolveComReference.ResolveComClassicReference(ComReferenceInfo referenceInfo, String outputDirectory, String wrapperType, String refName, Boolean topLevelRef, ComReferenceWrapperInfo& wrapperInfo)
   at Microsoft.Build.Tasks.ResolveComReference.Microsoft.Build.Tasks.IComReferenceResolver.ResolveComClassicReference(TYPELIBATTR typeLibAttr, String outputDirectory, String wrapperType, String refName, ComReferenceWrapperInfo& wrapperInfo)
   at Microsoft.Build.Tasks.TlbReference.System.Runtime.InteropServices.ITypeLibImporterNotifySink.ResolveRef(Object objTypeLib)
   at System.Runtime.InteropServices.TypeLibConverter.TypeResolveHandler.ResolveRef(Object typeLib)
   at System.Runtime.InteropServices.TypeLibConverter.nConvertTypeLibToMetadata(Object typeLib, AssemblyBuilder asmBldr, ModuleBuilder modBldr, String nameSpace, TypeLibImporterFlags flags, ITypeLibImporterNotifySink notifySink, ArrayList& eventItfInfoList)
   at System.Runtime.InteropServices.TypeLibConverter.ConvertTypeLibToAssembly(Object typeLib, String asmFileName, TypeLibImporterFlags flags, ITypeLibImporterNotifySink notifySink, Byte[] publicKey, StrongNameKeyPair keyPair, String asmNamespace, Version asmVersion)
   at Microsoft.Build.Tasks.TlbReference.GenerateWrapper(ComReferenceWrapperInfo& wrapperInfo)
   at Microsoft.Build.Tasks.ResolveComReference.ResolveComReferenceTlb(ComReferenceInfo referenceInfo, String outputDirectory, String refName, Boolean topLevelRef, ComReferenceWrapperInfo& wrapperInfo)
   at Microsoft.Build.Tasks.ResolveComReference.ResolveComClassicReference(ComReferenceInfo referenceInfo, String outputDirectory, String wrapperType, String refName, Boolean topLevelRef, ComReferenceWrapperInfo& wrapperInfo)
   at Microsoft.Build.Tasks.ResolveComReference.ResolveReference(ComReferenceInfo referenceInfo, String outputDirectory, ITaskItem& referencePathItem)
   at Microsoft.Build.Tasks.ResolveComReference.ResolveReferenceAndAddToList(ComReferenceInfo projectRefInfo, ArrayList resolvedReferenceList, ArrayList moduleList)
   at Microsoft.Build.Tasks.ResolveComReference.Execute()
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.Build.Framework.ITask.Execute()
   at Microsoft.Build.BuildEngine.TaskEngine.ExecuteTask(ExecutionMode howToExecuteTask, Hashtable projectItemsAvailableToTask, BuildPropertyGroup projectPropertiesAvailableToTask, Boolean& taskClassWasFound)	TRExT

Sorry for the large entry.

This is the first time i've come across this, but the only other application i have upgraded was quiet small in comparison and used minimal ActiveX components.

Thanks again.

 

[chrissie1]

Why do you want to convert to .net?

You should try to find .net equivalants of the activex components if possible. Most activex will work with .net but some can give strange results and will be diffcult to manage at best.

Seems to me that he can't find a certain method.

Method not found: 'Void VB._PictureBox.set__Default

but it's hard to say. What activex is causing the problem and why did you use it.

Anyway, the wizard will try but it is ver doubtfull that it will do a good job, most of the times we suggest starting from scratch, don't forget vb.net is not vb7 it is very different from vb6.

Christiaan Baes
Belgium

I just like this --> [Wiggle] [Wiggle]

 

[HighlandJinx]

So rather than try to upgrade our application using the Visual Studio wizard, you're suggesting its better to start from scratch?

All we wanted to do was upgrade to VB.NET to take advantage of some of the new features it provides, we thought upgrading with the wizard wouldn't be to bad a process, is it better all round just to work from the ground up when all we are doing is modernising?

 

[chrissie1]

uhm, yep. I thing you will find that anybody who has done it will tell you the same thing.

And better still if your app works fine in vb6 just keep it there.

if you want to take advantage of the best features of .net you will have to learn OOP and use it.

Christiaan Baes
Belgium

I just like this --> [Wiggle] [Wiggle]

 

[HighlandJinx]

Ok thanks for the advice. I learned OOP before i became a VB programmer so i'll suggest that the product is redeveloped rather than upgraded.

Thanks again.