Welcome to Dream.In.Code
	Become an Expert! Join 340,162 Programmers for FREE! Get instant access to thousands of experts, tutorials, code snippets, and more! There are 4,038 people online right now. Registration is fast and FREE... Join Now! Chat LIVE With a Expert

vb6 support in vb.net?

Page 1 of 1

vb6 support in vb.net?

Poll: vb6 support in vb.net? (14 member(s) have cast votes)

Should Microsift ditch vb6 support in vb.net

Yes (11 votes [78.57%])
Percentage of vote: 78.57%
No (3 votes [21.43%])
Percentage of vote: 21.43%

If so, when?

Next framework release 4.0 (10 votes [71.43%])
Percentage of vote: 71.43%
1st release after 4.0 (2 votes [14.29%])
Percentage of vote: 14.29%
2nd release after 4.0 (2 votes [14.29%])
Percentage of vote: 14.29%

Vote Guests cannot vote

#1 AdamSpeight2008

The Bandido Coder

Group: Moderators
Posts: 3,289
Joined: 29-May 08

Windows Favorite Browser Favorite Processor Favorite Gaming Platform Your Car
Dream Kudos: 4050
Expert In: vb.net, LINQ

Posted 07 May 2009 - 12:32 AM

I think its about time Microsoft killed the support for vb6 in the vb.net langauge.
vb.net is consider to be runt of the programming languages (professionally) because it has the monkier VB.

vb.net <> vb6

if anything its vb.net > vb6

What are your views?

Was This Post Helpful? 0

Register for Free to Make These Ads Go Away!

#2 noorahmad

Author

Group: Author w/DIC++
Posts: 2,198
Joined: 12-March 09

Windows Favorite Browser Favorite Processor Favorite Gaming Platform Your Car
Dream Kudos: 1600

Posted 07 May 2009 - 12:41 AM

i don't know about VB6 but i know that the old versions are expiring and VB6 is about 1998 11 years ago and i think Microsoft will not Give Supports to VB.Net,
hmmmm.... maybe yes
but i'm 99% sure that No.

Was This Post Helpful? 0

#3 AdamSpeight2008

The Bandido Coder

Group: Moderators
Posts: 3,289
Joined: 29-May 08

Windows Favorite Browser Favorite Processor Favorite Gaming Platform Your Car
Dream Kudos: 4050
Expert In: vb.net, LINQ

Posted 07 May 2009 - 01:01 AM

You do know that vb.net its still possible to use vb6 functions and routines, through the Microsoft.VisualBasic Namespace.
I'm saying that this should be removed.
Also they should remove the vb migration functionality. The vb6 to vb.net code converter.

This post has been edited by AdamSpeight2008: 07 May 2009 - 01:02 AM

Was This Post Helpful? 0

#4 noorahmad

Author

Group: Author w/DIC++
Posts: 2,198
Joined: 12-March 09

Windows Favorite Browser Favorite Processor Favorite Gaming Platform Your Car
Dream Kudos: 1600

Posted 09 May 2009 - 10:44 PM

AdamSpeight2008, on 7 May, 2009 - 12:31 PM, said:

maybe yes! :blink:

Was This Post Helpful? 0

#5 PsychoCoder

apt-get install DIC.bin

Group: Admins
Posts: 16,214
Joined: 26-July 07

Windows Favorite Browser Favorite Processor Favorite Gaming Platform Your Car
Dream Kudos: 12400
Expert In: VB, VB.Net, C#, SQL, ASP, ASP.Net, Web Development, HTML, CSS, Win32 API, Javascript, mySQL, J#, Boo.Net, jQuery

Posted 14 May 2009 - 10:04 AM

I personally feel support for legacy VB6 functions should have ended with the release of .Net Framework 1.1. I feel that should have given programmers enough time to get used to using the new language and libraries. There's nothing more irritating than looking through someone's VB.NET code and seeing a ton of legacy functions being used (such as Mid, Left, Instr, etc).

Come on people, VB.NET has been out for quite some time now, and the native libraries have been there for a long time for a reason.

Was This Post Helpful? 0

#6 searockruz

D.I.C Regular

Group: Members
Posts: 459
Joined: 07-March 09

Who Cares Windows Favorite Browser Favorite Processor Favorite Gaming Platform Your Car
Dream Kudos: 0

Posted 14 May 2009 - 10:10 AM

PsychoCoder, on 14 May, 2009 - 10:04 AM, said:

no use of keeping old technologies ,its just a burden to students,some universities prefer to keep the old syllabus

Was This Post Helpful? 0

#7 SixOfEleven

XNA Developer

Group: Moderators
Posts: 4,015
Joined: 18-October 08

Windows Favorite Browser Favorite Processor Favorite Gaming Platform Your Car
Dream Kudos: 1100
Expert In: C, C#, XNA, Game Programming, Programming Concepts

Posted 14 May 2009 - 06:22 PM

AdamSpeight2008, on 7 May, 2009 - 02:32 AM, said:

Yes, vb.net > vb6

unless you want to write a native application for an older platform that does not support .NET. Why you would want to write for an older platform, I don't know.

So if you are targeting Windows you might as well use .NET and forget about vb6.

Was This Post Helpful? 0

#8 Core

Jasper

Group: Admins
Posts: 3,482
Joined: 08-December 08

Windows Favorite Browser Favorite Processor Favorite Gaming Platform Your Car
Dream Kudos: 975
Expert In: .NET Framework

Posted 14 May 2009 - 07:14 PM

I would completely agree that the legacy functions should be removed. There are already not that many developers who are switching from VB6 to VB.NET since .NET already became a industry standard, replacing the old versions of VB. Legacy functions just keep developers that used VB6 from learning the new .NET functions and classes.

Was This Post Helpful? 0

#9 AdamSpeight2008

The Bandido Coder

Group: Moderators
Posts: 3,289
Joined: 29-May 08

Windows Favorite Browser Favorite Processor Favorite Gaming Platform Your Car
Dream Kudos: 4050
Expert In: vb.net, LINQ

Posted 14 May 2009 - 08:12 PM

If want to see if using legacy code, remove the reference to Microsoft.VisualBasic namespace from your project.

Was This Post Helpful? 0

#10 BlueBoris

New D.I.C Head

Group: New Members
Posts: 2
Joined: 19-October 08

Windows Favorite Browser Favorite Processor Favorite Gaming Platform Your Car
Dream Kudos: 0

Posted 23 May 2009 - 02:14 AM

AdamSpeight2008, on 7 May, 2009 - 12:32 AM, said:

I couldn't disagree more! There are plenty of VB6ers out there who still have not migrated to .net. I think it might be a good idea to have this support as an option when installing. Guys that have made the switch sucessfully don't need it. I am only just getting to grips with VS2005. You wouldn't deprive me of an income would you ?

Regards
Boris

Was This Post Helpful? 0

#11 PsychoCoder

apt-get install DIC.bin

Group: Admins
Posts: 16,214
Joined: 26-July 07

Posted 23 May 2009 - 04:14 AM

Well if you've made the jump to VB.NET then the need for legacy functions should be gone, and should have been gone with version 1.1. If you need legacy functions to make a living maybe you should look at why you need them

Was This Post Helpful? 0

#12 TechWar

D.I.C Regular

Group: Members
Posts: 469
Joined: 17-February 09

Linux Favorite Browser Favorite Processor Favorite Gaming Platform Your Car
Dream Kudos: 0

Posted 24 May 2009 - 12:51 PM

Maybe because his company does. Yes, there are some out there that still want vb6. Not the majority, but some. If removing the reference to it in your project properties ia all you need to do to make yourself happy, why mess with someone else's livelihood.

I don't use it (vb6) anymore, so I don't really care if it stays or not, but I guess I don't really see what the difference is.

Was This Post Helpful? 0

#13 CharlieMay

D.I.C Regular

Group: Contributors
Posts: 423
Joined: 25-September 09

Windows Favorite Browser Favorite Processor Favorite Gaming Platform Your Car
Dream Kudos: 25

Posted 02 February 2010 - 02:01 PM

I agree, Although I still struggle sometimes with things like Left, Mid etc... Just a habit to think of the legacy methods after doing them as far back as C=64 basic. But they are no longer needed.

I was one of the people that struggled with VB -> VB.NET it was so different and outside my Think-Box that I found it difficult to get a grip on it.

What I think really pushed me forward was that I had an application that I wrote in VB and was done with and I decided to start designing forms in vb.net to convert it just as a learning experience. For applications I needed to get written I kept jumping back to VB6 so that I could get them done quickly and not have to research the equivalent in .net. What I found was that I missed a lot of the built-in functionality of the controls in .NET and that kept pushing me to learn it.

Now that I'm capable of writing applications in .net I haven't looked back. I have even went back through earlier code and started removing legacy methods. So yea, it took a lot of words to get there, but I have to say Yes, remove the legacy equivalents.

Was This Post Helpful? 0

#14 hawkvalley1

D.I.C Head

Group: Contributors
Posts: 165
Joined: 02-July 08

Windows Favorite Browser Favorite Processor Favorite Gaming Platform Your Car
Dream Kudos: 25

Posted 03 February 2010 - 06:26 PM

I have decided not to use this namespace myself. But I have no ties to Legacy VB. Home grown .Net boy, 'cept when I was younger doing Fortran - not that I remember any of it.

Was This Post Helpful? 0