I do know that visual studio.net when you compile your code,
it compiles directly into machine code, which makes your programs run just as fast as any oter program made by real programming busnesses.

So exactly what is .net? Is it basically VC++ 7.0, but they decided to stop using a numbering system to make it look more special?

VC++.net is VC++ 7. I supposed they named it .Net so you can tell that its part of the ''new'' package. Well, and the fact that it shares the same IDE with the other languages ( but they change depending on what language you are currently editing in ). There is a main interface, and then you install components when you install VS.Net (Like VB.net, C++.net, ect). Depending on which components you install, you can edit different languages.

Err Compfreak.. every compiler does that, otherwise you couldn''t even /run/ your program.

Oh and uh, ''real programming businesses'' have been using VC++ 6 for years, almost every game released has used it.

Cheers for that, I had a fair idea but wasn''t sure. Hmmm, I was gonna pick up on CoMpFreak''s comment too, but couldn''t be bothered. True tho.

Compiled languages (e.g. VC++) convert (compile) your code to machine code in one go, then creates an executable which you can run.

Interpreted langages (e.g. BASIC) take each line of your code in turn, translates it to machine code, then runs that line. This is why interpreted languages result in slower programs. Not always a problem, but not suitable for the latest FPS!

My bad sorry.

Yah if you know c++ you can do c++.net no difference, menus are a bit different though, and there are a few new features trhat i am trying to figure out what they are...

visual studio.net is just most all microsoft programming languages compact into one package included j#,C#,c\c++ ...etc with xtml asp and things included.

[edited by - CoMpFreaK on July 24, 2003 12:33:01 PM]

If VC++.net is just the next version up to VC++6.0, why has there been the need for NeHe''s tutorials to be "ported" to VC++.net? Surely code from VC++6.0 should work straight away in .net and therefore not need to be ported?!

The code itself should compile and run fine. However VC++.Net uses a different way of managing a "programming project" in VC++6.0 all the include files, headers, resource files were specified in VC++ project files.

Now they are called Studio.Net "solutions." This is where you specify all your files that are required to compile and run your code.

I had not problems copying and pasting the VC++6.0 code into my Visual Studio.Net interface. You just have to resepcify where the user defined headers, source files, and libraries are.

Hope this helps.

The best is yet to be

Cheers for the reply, all is clear now. Typical Microsoft, complicating things for all of us!

Heh ok no need to waste time to upgrade to .net

One improvement in .NET is that little pop up box that comes up when you type a ''.'' or -> or similar, that works a lot better in the new version. And the pop up that tells you variables are passed into a method, well that works for OpenGL methods now it never used to.

Kazade.

Hyperdev

"To err is human, to really mess up requires a computer"