Visual Studio and VB.Net Relationship 1

[Skittle]

I'm just starting to learn about VB.Net.

Visual Studio and VB.Net seems to be seperate entities.
What are the differences between these two entities?
In other words, where does one enad and the other start?

Is VB just the code standard and Visual Studio the GUI interface to enter the code?



Dazed and confused

 

[chrissie1]

visual studio is a collection of programming languages wich include c#, VC++ and VB.net and other tools.
VB.net is part of that collection. but can be bought on it's own and then its called vb.net standard edition.

Christiaan Baes
Belgium

If you want to get an answer read this FAQ faq796-2540
There's no such thing as a winnable war - Sting

 

[Skittle]

I see.

Is Visual Studio and the SDK ( Software Development Kit ) therefore the same thing?


Dazed and confused

 

[chrissie1]

nope

the SDK can be installed without visual studio and it has all the tools to create c# and vb.net programs however it has no IDE to work with you have to do everything via the commandline and notepad.

Visual studio needs the sdk to be installed because it uses some or all of its components.


Christiaan Baes
Belgium

If you want to get an answer read this FAQ faq796-2540
There's no such thing as a winnable war - Sting

 

[Skittle]

Gotcha.

Many thanks.

Dazed and confused

 

[Skittle]

Hmm one more thought.

Is the following structure correct?


Top Level : IDE GUI front end

Middle Level : VB & C# Visual Studio Language for IDE

SDK : VB & C# Languages for use with notepad.

So..

SDK must be installed to create programs.

Visual Studio or a single .Net language version must be installed for IDE to interact with it. It acts as
the IDE to SDK bridge.

IDE makes use of a standard edition or installed Visual Studio multi language edition. With no 'middle level' of Visual Studio or a standard edition program, IDE has nothing to play with.


Dazed and confused

 

[shatch]

The one thing that must be installed to run any .net application is the .net framework. That is what everything sits on.

Everything which runs on the framework is converted into CLR (Common Language Runtime) at compliation

Then there is the actual language, written in a program such as visual studio

 

[chrissie1]

Then there is the actual language, written in a program such as visual studio

or not you don't need visual studio to write a program you can do that in notepad

but you do need the sdk with the compilers to compile it and so does visual studio.

Christiaan Baes
Belgium

If you want to get an answer read this FAQ faq796-2540
There's no such thing as a winnable war - Sting

 

[Skittle]

Hmm the plot thickens.....(scratches groin thoughtfully)...

Well confused. Take a deep breath.


SDK

I can see that the SDK must be fundementally compilers. But from what I've read, I see the SDK as converting language code ( C#, VB etc ) into MSIL
( Microsoft Intermediate Language ) that is then
converted/compiled again by the CLR at run time using JIT ( Just In Time ) compilation to make low level platform instructions.


.NET Framework

I think .Net Framework must be .dll language transparent classes that you must of course have to be able to inherit and use class's in your projects.


IDE

Must be the GUI bit.


Visual Studio

Is the language you edit via the IDE. It uses the .Net framework DLL's to create new executables. These new executables should to my mind be .DLL or executables in VB6 but in .Net could be MSIL's?


N.B.
I only have one source for MSIL which is the Que Book, 'MCAD/MSCD Exam 70-306 Developing and Implementing Windows Based Applications With Visual Basic.Net'.







Dazed and confused

 

[chrissie1]

youre pretty much there

except visual studio is the IDE and it make .exe's and dll's wich are a bit different from vb6 they are more like what java does

Christiaan Baes
Belgium

If you want to get an answer read this FAQ faq796-2540
There's no such thing as a winnable war - Sting

 

[Skittle]

OK I think I get it.

Many thanks.

Dazed and confused