.NET is evil.

[cyclonebri]

C#.net also includes the 'this' keyword, instead of the 'me' keyword which is used in vb.net.

[hog]

I love .NET. I love Microsoft. I love all the help files that keep me from polluting this board with all but the more difficult questions (wish others had that mentality).

 

Sometimes it is far quicker to ask the forum than to drudge through the help. I do look through the help a lot but then again a lot of the times you get passed from pillar to post so many times you end up forgetting what it was you were originally looking for:)

 

I think .NET is fandabbydosey, yes it does make life so much easier and hey why not.....why reinvent the wheel if someone else has already done it....use it :)

 

Apart from ripping of games that is....comon Liu ya could have at least changed the splash screen or somthing:)

[Banjo]

Part of the trick to using the help system is to read the articles. They give you a lot of information about how things slot together, including practical examples.

[Darc]

I have a question... I've used VB .NET for a while, and I have C++ .NET (I only really ever make Win32 apps with it though). Is it worthwile to go get C# .NET or to learn C++ .NET? VB .NET was my first language when I started a month ago, but it now seems a little slow for gaming uses. Input?

[AlexCode]

For gaming uses you shouldn't find any diference between VB.net and C#... It's basiclly a language option. Althogh if you want to play "out" of the framework C# gives you a small oportunity, giving you the ability to call "unsafe" code and C++, that putting it in a simple way, do whatever you want!

 

In my idea, choosing between them it's just a matter of productivity.

 

 

Alex :D

[goodmorningsky]

Hi, all.

This thread is the most popular debate at the year when the .NET comes out.

There are lots of software engineers with .NET and against .NET.

I feel like that

those who work with Microsoft technologies like .NET but, others are against it.

Since, as you all heard, the architecture of .NET is tween of Java technology.

Because .NET was planned after MS was sued by SUN regarding that MS used Java as a core part for Biz component development, and MS paid several millions to SUN. Then MS started .NET to bit SUN.

 

If you guys interest about .NET features, it's good to learn Java or read articles comparing .NET and Java..

 

You will see nothing in .NET is new to Java developers, but brand new to MS developers.

[Robby]

I've done more than enough JAVA.

 

Perhaps reading this will shed some light, by the way it's written by a JAVA guy and he's not a 'Microsoft patriot' ....

http://www.exia.net/html/app/sitecontent/CGI%20Dot%20Net%20vs%20J2EE.pdf

[divil]

It's interesting, that when Sun won their case against Microsoft, they effectively sealed Java's fate - at least on the client side. Being distributed with Windows is the best thing that can happen for a product, and that's not allowed any more.

[Derek Stone]

Sun has made a lot of poor decisions over the last few years. The fact that they still talk out of both sides of their mouth regarding Solaris and Linux is just one example.

[Tryster]

I think one ot the key things to bear in mind is that Longhorn is being build from the ground up around the .NET philosophy.

 

Indeed, if you believe the hype the .NET FW will eventually replace the Win32 layer. Just because currently MS has chosen to implement a lot of it's classes on top of Win32 (probably for speed of development) does not mean they will continue to do so in the future. Essentially Win32 is a wrapper around calls into the kernel, so as new kernel calls are added in Longhorn and beyond, it makes sense that the associated .NET classes will make these calls direct to the kernel. As such I think we'll see (on the Windows platform at least) .NET performance getting better and better.

 

Additionally, with longhorn and beyond the framework will become part of the operating system, (much as Win32 is now) and we should see performance gains from this...