I am maintaining a VB6 application and we are studying how to migrate to .Net We are considering doing this gradually by implementing new features in COM visible .Net classes and migrating existing functionality slowly. I found some instructive 'Hello World' examples about how to do this and it works fine with our App. But how is the real world behaviour of these hybrid applications? Are they stable, maintainable? Particular of our program is that more users on the same computer will use it by switching user accounts.EDIT:The VB6 app reads data from a USB connection and stores it in an Access database. The user can call up various views on the data. The data is cached in a hardware device, so interuptions in the reading of it are not fatal.EDIT 4th Oct 2015:Time for a follow up: We still are in the process of replacing the existing VB6 code step by step to .Net. First we took on the data access routines, then the bussiness logic and currently one form after another is converted to WPF. We indeed ended up rewriting every piece of code we converted (in VB.Net), but we could do so slowly and on the same time improving functionality. The hybrid application survived the transition to Windows 8, 8.1 and 10.
How are hybrid VB6/.Net applications functioning in the Real World?
.net;migration;visual basic 6
I have had amazing success exposing .NET to VB6 via COM interfaces. By doing this we were able to initially refactor out a huge amount of VB6 code and set up an upgrade path to .NET. Just keep in mind that idiomatic VB6 does not translate well to C# or even VB.NET so you'll want to tread carefully.The one issue we had which was pretty annoying was the excessive amount of rebuilds we had to do because of changes to the public COM interface. This was alleviated by Visual Make.