.NET and VB6: Interacting with a viable development strategy?

Is the interplay between VB6 and .NET a viable development strategy?

I am working on a VB6 application that interacts with some .NET assemblies, but a combination of "cold start" and other cohesion issues leads to a non-smooth result.

+5
source share
7 answers

EDIT - shortened my answer a bit.

Is it possible? Yes of course.

Would I recommend this? Of course not!

( ) , , VB6 . , , , , ; , / .

, - VB6 .NET. MarkJ , , .

MS: -

http://msdn.microsoft.com/en-gb/dd408373.aspx#migrate3

MS , , ( ). , , Visual Basic, , #, VB.NET. - VB.NET.

: -

[] , :

  • , , / . , .
  • . , . , .
  • .NET, .
  • .

, - , , , , VB6, - , , , .NET. , , ( ).

, . ? VB6? .NET?

+6

, .NET 5 , . , - .NET :

  • VB6 , (, CI).
  • .NET , VB6.
  • .NET, .

.NET( #), , # ( interop # Interop toolkit), WPF. , , ( ) (sendMessage , LockWindowUpdate ) . APP, , , WPF, , , ( ) VB6 Com/.NET, Microsoft (heck Visual Studio 2010 - Franken, ++ Com/#/ WPF).

+4

VB6 .NET ?

"", "!". .Net vb6 . , vb6, , vb6 Microsoft, vb6 , , . . , .

:

VB6 .NET ?

, . , - vb6, vb6, , .Net, . , .Net 4.0, , .

.

+3

VB6 .NET ( ).

. .NET interop .

, VB6 #, ( , ), Interop , , () , , ( #).

, , . VB6- exe ActiveX exe, .NET, VB6 Interop .NET. , , , , !

, Interop, ghonnosyphiherpilitis.

+2

VB6 .NET ?

, - , . VB6 .

0

, .NET, COM- VB6, .

.NET, Office. .NET, , Office , KB.

VB6, Office, API - Office.

0

COM .NET,

" VB6, .NET"

"".

- " ", . . , COM- .NET. CCW, , .

, VB6 . , VB6 . VB6 , VB6/COM - , . VB6 , , . .

Take a VB6 application in .NET (and minimize the direct use of COM from your application level there); You will not regret it. I also found that rewriting large VB6 / ASP.COM applications for .NET can be done much more efficiently when you use a methodology that balances manual work with automatic conversions rather than insisting that you should completely ignore legacy code and do everything from scratch. "

0
source

All Articles