Hey, sorry immediately - this might be below the level of this forum.
Haven't done any games programming since the early 80s in Commodore's 6502 assembly lang.. which was fine when you knew the hardware spec and all the tricks to get what you wanted out of it (inspired by Yak) .. hey I was 13!
Anyway, purely for personal fun rather than anything remotely commercial, any Windows programmers out there who can advise whether it's worth using MS VB/C# 2005 w/DirectX to knock up some silly 2D game for fun or is it a bag of shite and not worth putting the effort in?
thanks
MS Visual Studio 2005 - personal projects?
- WiredWorm
- Baaaaaa!

- Posts: 3162
- Joined: Thu Dec 22, 2005 4:48 pm 0
- Location: Right here on the edge of my seat......
There's nothing stopping you from coding the framework of the game in VB and then using C# for the stuff which needs to be quick (graphics routines and the like).
I've a background in programming VB and C++ but to be honest i've started tinkering with BlitzMax now because it's relatively powerful and you can quickly get some good results using it.
I've a background in programming VB and C++ but to be honest i've started tinkering with BlitzMax now because it's relatively powerful and you can quickly get some good results using it.
GamerTag: WiredWorm
It's like another mouth - LamptonWorm
It's like another mouth - LamptonWorm
- moobaa
- Sheepie Whore

- Posts: 16118
- Joined: Sun Sep 29, 2002 8:08 am 0
- XBL Gamertag: petee moobaa
- PSN: moobaa
- Location: Sydney, Australia
You wouldn't necessarily see any speed improvement, since I think the two compilers are around about equivelant in terms of the speed of output code.WiredWorm wrote:There's nothing stopping you from coding the framework of the game in VB and then using C# for the stuff which needs to be quick (graphics routines and the like).
Writing the arse end in C++, OTOH, and accessing it via COM (with interop overheads) or directly (via the DLL interface - unmanaged code ahoy!) may yield swifter code.
It's easier to write the arse end in C++/CLI and define the API to the arse end as managed classes. That way the compiler does the interop for you and you only have to link the C# (or VB) code of your main application against a managed assembly.moobaa wrote:You wouldn't necessarily see any speed improvement, since I think the two compilers are around about equivelant in terms of the speed of output code.WiredWorm wrote:There's nothing stopping you from coding the framework of the game in VB and then using C# for the stuff which needs to be quick (graphics routines and the like).
Writing the arse end in C++, OTOH, and accessing it via COM (with interop overheads) or directly (via the DLL interface - unmanaged code ahoy!) may yield swifter code.



