Sie sind aktuell nicht angemeldet.

Funktionen: Einloggen  |  Neu registrieren  |  Suchen

Re: Vb6 project to VB.Net Problems
Autor: DaveS (Moderator)
Datum: 02.05.11 13:21
Yep, for anything other than trivial programs it is generally better to start anew. Mostly it's also a chance to improve the basic architecture and remove various maybe poorly implemented "fixes" and "improvements" which have built up over the years. Although there are certain compatibility functions (e.g. FileOpen()), the awful On Error and GoTo still work and data access methods like AdoDB along with the COM controls for things like Datagrids, Winsock etc. can still function (very inefficiently) under .Net, .Net itself has completely different and generally better and more consistent methods for implementing these things, as well as having highly advanced capabilities such as Linq, WPF, WCF and Entity Framework from which no advantage can then be drawn. Even if one can get the converted VB6 code to run, the result is a mess of things which should not be part of a .Net program in the first place, and has not provided any experience in learning .Net correctly (i.e., as it is intended to be used). ________ Alle Angaben ohne Gewähr. Keine Haftung für Vorschläge, Tipps oder sonstige Hilfe, falls es schiefgeht, nur Zeit verschwendet oder man sonst nicht zufrieden ist

Vb6 project to VB.Net Problems	1.339	einet	29.04.11 19:22
Re: Vb6 project to VB.Net Problems	804	Manfred X	30.04.11 01:03
Re: Vb6 project to VB.Net Problems	807	einet	30.04.11 19:15
Re: Vb6 project to VB.Net Problems	762	Granny	02.05.11 10:56
Re: Vb6 project to VB.Net Problems	760	DaveS	02.05.11 13:21
Re: Vb6 project to VB.Net Problems	753	einet	02.05.11 17:08
Re: Vb6 project to VB.Net Problems	739	RalfE	02.05.11 20:01

Sie sind nicht angemeldet! Um auf diesen Beitrag zu antworten oder neue Beiträge schreiben zu können, müssen Sie sich zunächst anmelden. Einloggen  |  Neu registrieren

Funktionen:  Zum Thema  |  Gesamtübersicht

Suchen