I have taken on a project of migrating a large VB6 application to .NET C#, I have spent the last year making updates and understanding how the application works. The company does not want to rely on Visual Studio 6 since it is technically no longer officially supported and they cite security concerns, also no one has had time/wanted to do it.
The question(s) I have are:
Should I begin picking apart modules and rewriting them in C# with the intent of COM-Interop and integrate them into the VB6 application?
OR
Should I begin the creation in C# and convert my existing libraries to a DLL and call/access them in .NET?
I have tested both ways(not forms yet) and made it work, however, I lack the knowledge of what would more compatible/least likely to experience interoperation errors. Also what is easier to debug, as I am not sure everything that can pass back and forth via COM.
Something similar may have been discussed before on this forum, however, what I found didn't seem close to applicable or it was more than 3 years old, so I didn't want to revive something so old.
The question(s) I have are:
Should I begin picking apart modules and rewriting them in C# with the intent of COM-Interop and integrate them into the VB6 application?
OR
Should I begin the creation in C# and convert my existing libraries to a DLL and call/access them in .NET?
I have tested both ways(not forms yet) and made it work, however, I lack the knowledge of what would more compatible/least likely to experience interoperation errors. Also what is easier to debug, as I am not sure everything that can pass back and forth via COM.
Something similar may have been discussed before on this forum, however, what I found didn't seem close to applicable or it was more than 3 years old, so I didn't want to revive something so old.