I don't want to discourage you, but C# is a bad idea. There isn't some real "standard" behind it ; there is very little support (especially for other platforms) and it teaches "bad" ways of programming. On top of that, the lifetime of the language is suspect to end at any time, just like MS did with MFC.
With that said, if you really want to develop for C#, please do !</rant>

Quote: Original post by vincoof
I don't want to discourage you, but C# is a bad idea. There isn't some real "standard" behind it ; there is very little support (especially for other platforms) and it teaches "bad" ways of programming. On top of that, the lifetime of the language is suspect to end at any time, just like MS did with MFC.
With that said, if you really want to develop for C#, please do !</rant>

Well I don't agree with the language being near death in anyway, but I agree it will not be in a direction opengl is going.

But good luck if you want to do this.

This is one time I have to disagree with Vincent. I strongly encurage you to use C#. I know I'm building my next engine in it. But I'll wait for .NET 2.0 becouse 1.1 is still missing some important stuff. I don't belive C# is going away anytime soon. It's only getting evolved (v2.0) into something better. Plus, it's powerd by MS, and that is a good thing. Support for other platforms is just OK for this early stage. I've seen some apps running in Mono just fine. I know it's still getting evolved and I hope to see it on other platforms soon.

tgraupmann: I urge you to use something like Tao for opengl binding or you'll spend next 2 months wrinting just gl function warpers.

About other things. I would love to see another topic started, where people could discuss problems with their work. I'm probably not entering this one, so I'll try to help as much as I can.

Quote: Original post by tgraupmann
You see there isn't an OpenGL library for C#. So you have to dllimport or pinvoke all the methods you want to use. Basically, it requires the additional work of writing a library with all the interfaces to access opengl32.dll.

Or it requires you to look for one that already exists, and the Tao framework is the defacto standard when it comes to OpenGL and C#. For a good example of this, you can check out the Axiom graphics engine project on sourceforge. I am also a very active member there. If you have any questions on getting OpenGL and C# working together nicely, I would be more than happy to help. If I enter this contest, then I will also be using C#.

Edit: I forgot to mention that the Tao framework site still says "Coming Soon". You can either use the old version of the libraries that are supplied there, or you can get the new libraries from the Axiom dependencies download, or you can ask me and I can send them to you.

Quote: Original post by vincoof
There isn't some real "standard" behind it ; there is very little support (especially for other platforms) and it teaches "bad" ways of programming.

<rant>Those are inflamatory word there. C# is an EMCA standard, and I believe that it is also an ISO standard as well. This means that once the .Net 2.0 spec is out, Microsoft won't have complete control over the C# language specification. Support for C# is just fine on other platforms, you have your choice of Mono, or DotGNU. I can't speak for DotGNU, but the Mono project is really far along, and supports the vast majority of the .Net framework. As for 'teaching "bad" ways of programming', a programming language does not inherently teach you how to program. You can just as easily find tutorials on how to write "bad" code in C++.</rant>

J.W.

[Edited by - jwace81 on October 11, 2004 4:25:50 PM]

Quote: Original post by _DarkWIng_
I know I'm building my next engine in it.

Why would you use c# instead of c++? What are the advantages?

Quote: Original post by skow

Quote: Original post by _DarkWIng_
I know I'm building my next engine in it.

Why would you use c# instead of c++? What are the advantages?

speed of development, help with memory management.
i have been playing with c# and open gl for the past few days writing my own classes to help with device and window creation.

i too hope to enter the nehe demo contest if i can ever get to grips with doing 3d graphics with c#. ( never done this sort of stuff before, always been networking apps :) and utilities)

Quote: Original post by RenZimE

speed of development, help with memory management.

Why not just use D then.

Quote: Original post by lc_overlord

Quote: Original post by RenZimE

speed of development, help with memory management.

Why not just use D then.

because i know absolutly nothing about D, tho having said that i may just go and take a look at it. (not to go off topic) (i hope this doesnt turn into a lang v lang )

Quote: Original post by _DarkWIng_
This is one time I have to disagree with Vincent. I strongly encurage you to use C#.

We finally found a topic where we disagree ! :P

Quote: Original post by jwace81
<rant>Those are inflamatory word there. C# is an EMCA standard, and I believe that it is also an ISO standard as well. This means that once the .Net 2.0 spec is out, Microsoft won't have complete control over the C# language specification.

TBH I am truly flaming here, and I know it's "bad" [wink]
The original C# support is really a shame IMHO. I don't know about the next release (because it seems that support is going to evolve, reading at your replies here). Maybe in the near future it won't be so bad. Who knows.

Quote: Original post by RenZimE
speed of development, help with memory management.

Maybe you're comparing C and C#, but definately not C++ with C#.

I really mean "C++" as a whole. Most C++ coders only use the class feature on top of C. C++ is much, much more than that.

Quote: Original post by RenZimE

Quote: Original post by skow

Quote: Original post by _DarkWIng_
I know I'm building my next engine in it.

Why would you use c# instead of c++? What are the advantages?

speed of development, help with memory management.

I can see using it now for the use of networking or other built in things for c# but I really dont see memory management that much easier you still have to call somthing to clear it up, when you could just as easily delete [], or delete.

I'm not triing to say "NO! You are wrong!" Just trying to fully understand why dark wants to use it.