[RESOLVED] Where has Visual Basic gone?

**dom_stapleton** · Sep 9th, 2005, 07:56 AM

OK... before you reply to this thread you have to understand that I am a total novice and have only just started using VB6. Is there a VB 7? If there isn't what have they renamed it to? Is it Visual Studio.NET? I would have thought that .NET meant it was related to the Internet in some way.

Please go easy on the idiot!

**Hack** · Sep 9th, 2005, 07:57 AM

VB.NET is the thing. And, the Visual Studio suites, after 6.0 were named after calendar years rather than using version numbers.

**RobDog888** · Sep 9th, 2005, 07:59 AM

But you can still see that VB 7 is named VB.NET 2002 and VB 7.1 is 2003 and VB 8 is 2005.

**dom_stapleton** · Sep 9th, 2005, 07:59 AM

Oh right. How come it is called .NET then? Does it mean that it is related to the Internet in some way, like for making HTML application or something?

**wiz126** · Sep 9th, 2005, 08:01 AM

had hack said vb 7 or 8 is named vb .net they got rid of the version number

P.S. the code had changed as well

**RobDog888** · Sep 9th, 2005, 08:01 AM

Nope, it has nothing to do with the internet. Just the name they choose. There is also the .NET Framework that VS (& VB) .NET run on. Maybe they had some meaning for .NET but its not Internet.

**RobDog888** · Sep 9th, 2005, 08:02 AM

Yes, its no longer considered any kind of upgrade from VB 6 but rather a new language thats all OOP based.

**Hack** · Sep 9th, 2005, 08:03 AM

Originally Posted by dom_stapleton

Oh right. How come it is called .NET then? Does it mean that it is related to the Internet in some way, like for making HTML application or something?

It is just Microsoft being clever.

Seriously though, the Visual Studio suite contains a variety of things, not just VB.NET and you can make web applications with this tool.

**wiz126** · Sep 9th, 2005, 08:05 AM

it has nothing to do with internet.
it has a diffrent lenguage as i said

i am pretty sure they choose the ".net" name b/c most buisness involved around the internet and a name like ".net" is just eye coughting

**RhinoBull** · Sep 9th, 2005, 08:05 AM

Originally Posted by dom_stapleton

Oh right. How come it is called .NET then? ...

Someone has just got a brilliant idea @MS I guess - it could be anything: get, set, let, wet, jet ... But silly part is that it sets the new style in the world of naming conventions.

**Jacob Roman** · Sep 9th, 2005, 08:09 AM

They could have called it VB#, but they chose .NET instead.

**NoteMe** · Sep 9th, 2005, 08:09 AM

AFAIK the name was choosen to reflect all the new technology in the framework geared towards facilitating rapid development of Internet and intranet applications. The new framework made it easier to program for Windows, and the web but also web services. And now also for other platforms sutch as Linux. but that has nothing to do with the .NET name..

- ØØ -

**Hack** · Sep 9th, 2005, 08:14 AM

Originally Posted by Jacob Roman

They could have called it VB#, but they chose .NET instead.

I've always wondered with they called it C# instead of C.NET *shrugs shoulders*

**Jacob Roman** · Sep 9th, 2005, 08:15 AM

I guess it would have been confusing to distinguish C++.NET from C.NET.

**RhinoBull** · Sep 9th, 2005, 08:15 AM

It keeps me (as well as everybody else) wonder too ...

**RobDog888** · Sep 9th, 2005, 08:17 AM

VB# would have been good to. They did do C# and J# so why not VB#?

**NoteMe** · Sep 9th, 2005, 08:23 AM

Originally Posted by RobDog888

VB# would have been good to. They did do C# and J# so why not VB#?

But C# is actualy called C# .NET, so then I guess VB would have been called VB# .NET..

. But to be honest, it actualy looks good..

- ØØ -

**Jacob Roman** · Sep 9th, 2005, 08:23 AM

Originally Posted by RobDog888

VB# would have been good to. They did do C# and J# so why not VB#?

Good question. Maybe someone oughta email MS and find out.

**RobDog888** · Sep 9th, 2005, 08:31 AM

I dont program in C# yet but I cant say that I have seen it referred that way - "C# .NET". All the jobs online just mention it as "C#" only but I'm sure there are some that may.

I know you program C# so I think you would know best.

**Hack** · Sep 9th, 2005, 08:34 AM

Interesting discussion.

Moved to General Developer.

**szlamany** · Sep 9th, 2005, 08:40 AM

The .NET craze at MS came along with VB.Net and ADO.Net - at the height of the XML-will-take-over the world moment.

We were all supposed to use disconnected recordsets - all of us start turning our ovens and DVD recorders at home on over the internet.

At the same time the very nature of security fell on it's face - SQL slammer - virus after virus after worm...

The "internet" revolution never materialized - we all still use intranet and VPN and anything else to keep the internet out of our networks.

XML never turned into anything more then a neat new way to store an .INI file. EDI was supposed to disappear with XML - but EDI is just as strong as ever, and even legally mandated for health-care transmissions!

Here's a quote from an MSDN archive...

CHARLES FITZGERALD: Yep, that's pretty close. The .NET platform is about helping people, through software technologies, build Web services, deploy them, operate them, aggregate and integrate them, and also consume. And that allows people to think about both exposing their capabilities in a standard way that other people can consume and embed those things into their environment, but also making it easy for the developer to consumer other Web services and leverage other intellectual property that's out there in the world.

Link to it: http://msdn.microsoft.com/archive/en...scriptText.asp

**RhinoBull** · Sep 9th, 2005, 08:53 AM

Originally Posted by szlamany

The .NET craze at MS came along with VB.Net and ADO.Net - at the height of the XML-will-take-over the world moment.

We were all supposed to use disconnected recordsets - all of us start turning our ovens and DVD recorders at home on over the internet.

At the same time the very nature of security fell on it's face - SQL slammer - virus after virus after worm...

The "internet" revolution never materialized - we all still use intranet and VPN and anything else to keep the internet out of our networks.

XML never turned into anything more then a neat new way to store an .INI file. EDI was supposed to disappear with XML - but EDI is just as strong as ever, and even legally mandated for health-care transmissions! ...

Can't say nothing but INDEED, INDEED and again INDEED as I just couldn't agree more. Crap is ... well ... crap - anyway you look at it.

**RobDog888** · Sep 9th, 2005, 09:02 AM

.NET is not "just about web services". It a total integration of suite apps all running on a common framework to say the least. Web services are a new feature but its not what .NET revolves around.

**szlamany** · Sep 9th, 2005, 09:07 AM

Originally Posted by RobDog888

.NET is not "just about web services". It a total integration of suite apps all running on a common framework to say the least. Web services are a new feature but its not what .NET revolves around.

RD - we know that's true, but that wasn't the MS marketing hype that they used to push this out with.

I believe that the new common framework - and the ultimate plans for the operating system related to the framework and file-storage system are great.

We had a common framework on our mainframes VAX machines back in 1980 - it's great that MS is finally thinking about losing the "reliance" on DOS as the backbone of the OS...

Why do we still have a CMD prompt?

**RobDog888** · Sep 9th, 2005, 09:09 AM

? I have a DOS prompt.

**NoteMe** · Sep 9th, 2005, 09:15 AM

It will even be a more advanced shell in Vista...I am looking forward to it. Makes certain things easier to do...

*walks back to his Linux machine*

**tr333** · Sep 9th, 2005, 09:42 AM

Originally Posted by NoteMe

It will even be a more advanced shell in Vista...I am looking forward to it. Makes certain things easier to do...

*walks back to his Linux machine*

until they implement symlinks in the windows console, it has nothing compared to linux.

**Hack** · Sep 9th, 2005, 09:51 AM

Lets not get into a Linux vs Windows debate.

The topic dejour is the .NET framework.

**RobDog888** · Sep 9th, 2005, 09:55 AM

I know

, they called it .NET because all the suite of apps are "networked" through the common framework.

**Jacob Roman** · Sep 9th, 2005, 10:23 AM

But if everything is gonna rely on the framework, even the Windows Vista OS, someone can easily create a virus that can destroy the framework, and not make anything work at all. Not exactly secure in my opinion.

**szlamany** · Sep 9th, 2005, 10:27 AM

Originally Posted by Jacob Roman

But if everything is gonna rely on the framework, even the Windows Vista OS, someone can easily create a virus that can destroy the framework, and not make anything work at all. Not exactly secure in my opinion.

Virus makers all exploit holes in the OS - holes is a nice way of saying untested buggy code.

Buffer overflows seem to be the target of most. That means the programmer did not check the size of data being moved to see if it's going to fit the memory spot it's going into. That's simply sloppy programming - today, yesterday, back in 1980 and back in 1960.

Allowing someone to "fashion" some data bigger then the buffer so that they can drop code into "execution space" is simply inexcusable.

**RobDog888** · Sep 9th, 2005, 10:30 AM

It should be no different then VB6 relying on the msvbvm60.dll runtime.

Thread: [RESOLVED] Where has Visual Basic gone?

Thread Tools

Display

[RESOLVED] Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Re: Where has Visual Basic gone?

Posting Permissions