Is possible work with VB 6.0 ?

Hi:

I work with Visual Basic 6.0, is possible work with Blitz 3D SDK with VB 6 ?

Many thanks.

It should be possible, but you would need to create the function definition file. There is one for C# that could be used as a template on what needs done.

Visual Studio 2005 is free, just download it.

http://msdn.microsoft.com/vstudio/express

VB6 is different VB.net IMHO, the possible way I can think of is translate PureBasic include and use it.

I'd say make the move to .Net. Preferably C#, but VB.Net is a good starter platform.

The language is largely irrelevant, its the .NET Framework that takes the effort to learn.

Language feature-wise the gap (small though it is) is closing with each version of Visual Studio that MS release.

Maybe "feature-wise" the languages are very similar, but, the resulting IL code generated by C# is much more optimized than that of VB.Net. But, really it is just a matter of preference. I started out doing VB 5, moved to 6. When .Net came out I figured since I had to learn a whole new framework I'd take the time to learn C#. I haven't looked back since.

emphasis mine

'much more' is a bit strong, MS themselves say...

'There are almost no performance issues between Visual Basic .NET and Visual C# .NET' in "Differences Between Visual Basic .NET and Visual C# .NET" link-> http://support.microsoft.com/kb/308470

I'm not saying there are no differences - because there are, but they are not as big as you might have inferred.

If you want a comparison of the two:

1) the MS article above
2) Syntax/feature comparison- http://www.codeproject.com/dotnet/vbnet_c__difference.asp
3) MSIL comparison (geek-alert) http://www.codeproject.com/dotnet/vbvscsmsil.asp


btw, I'm not a VB.NET fanboy, I earn a living coding both VB.NET and C# - I personally actually prefer C#, but I just want to make sure people have the facts.

the only performance issue is regarding late binding, wich can be a little slow on visual basic .net and it is inexistant on C#. Disabling the late-binding mechanism in the preferences dialog of Visual Basic.net solves this issue.

the data structure is the same in C# and Visual Basic .net so things are well organized in both languages.

In fact is someone tries to decompile a not obfuscated vb.net program, the result is C# code.

That's all good to know. The articles are interesting.

But I still like C# better :P

-j9t

> But I still like C# better :P


There are cures for that. :)