.NET is evil.

[wyrd]

.NET is evil. It has lured me into its claws by providing such simple and elegant ways to accomplish tasks, which would of taken hours upon hours to do in another language. In the end, it has seduced me in such a way that I cannot refuse it. And now I am proud to call myself a lazy programmer, because if I can help it, I'll never program in another language again, as I would obviously not have the patience to deal with such ugly syntax.

 

This could only be the work of evil.

 

Today I was toying around with my DX utility class library, and was adding resize logic (which later I found out that I didn't need to). Just for fun, I fiddled around with the WindowState of the form that I was using, and resized it to FormWindowState.Maximize. I know it was mentioned a few times on these forums, but I totally forgot that it was a cheap way to simulate fullscreen for a game.

 

My GameSurface (holds primary and buffer) has been greatly improved in the flexibility it can handle, all because of what .NET does for me. You can resize the window at will, move it around, set it to a control on a form, or even set the form to fullscreen to get the "fullscreen" effect. All of this is basically done for me, and has saved me the pains of adding my own code to handle such features. Heck, it even has some helper methods such as Control.PointToClient. LOL. Yet more code I didn't have to write.

 

I know this is not ideal for "real" games, but I'll take a small performance hit any day to have a flexible class that I can use in any situation, which didn't take me long to code at all.

[Robby]

The title of this thread is evil, it seduced me into reading your post. :)

[Liu Junfeng]

Yeah, it is easy to program in .net.

But it only benifits programmers not user!

This is the evil.

[Hamburger1984]

Hey wyrd!

 

you need something to make your app "real" fullscreen? try this:

 

a form with a Button "button1" - "button1_Click" Handles its Click-Event...

 

private bool m_FullScreen = false;
private Size m_RestoreSize = new Size(300,300);
private Point m_RestoreLoc = new Point(10,10);

private void button1_Click(object sender, System.EventArgs e)
{
if(m_FullScreen)
{
	this.FormBorderStyle = FormBorderStyle.Sizable;
	this.Location = m_RestoreLoc;
	this.Size = m_RestoreSize;
	this.TopMost = false;
	m_FullScreen = false;
}
else
{
	m_RestoreSize = this.Size;
	m_RestoreLoc = this.Location;
	this.TopMost = true;
	this.FormBorderStyle = FormBorderStyle.None;
	this.Size = Screen.FromPoint(this.Location).Bounds.Size;
	this.Location = new Point(0,0);
	m_FullScreen = true;
}
}

 

Hope this helps!

[wyrd]

While I appreciate your help, there wasn't a single question in my post. My post was about how easy .NET is to use and how it's spoiled me as a programmer.

 

To switch between "cheated" fullscreen and windowed, all you need to do is this (with the border set to none, obviously);

 

this.WindowState = FormWindowState.Maximized;

this.WindowState = FormWindowState.Normal;

 

That's what I mean by .NET being evil, it's just too darn easy.

[Robby]

Liu, how does it not benefit users? Are they not getting their products developed faster and with better features and so and so on and...........?

[Liu Junfeng]

I coded a software and a game in C#. But little people use them

because they use windows 98,2000,XP and they are not willing to install .net framework of 20M in order to use a software below 2M.

 

I also feel that .net program runs much slower than C++.

 

You can download my software at:

http://www.funnyok.net/rufi/Software.htm

http://www.funnyok.net/rufi/Game.htm

 

The information is given in Chinese. But I think you can find the link to download.

[Robby]

Hmm, funny how people will download huge DirectX updates in order to play games and such, or even Windows updates that can be much larger than 20 megs.

 

And by the way the Framework is already part of XP service packs, and will be shipped with all future releases of Windows.

 

I simply don't understand all complaining. :(

[Derek Stone]

Of course little of it has to do with the popularity of the software... *cough*.

[Robby]

:)

[wyrd]

You coded a game in C#? Maybe it's just coincidence that the game looks almost identical to mine, but with minor changes.

[PlausiblyDamp]

Very minor changes indeed - does have a certain 'similarity'.

[Liu Junfeng]

You coded a game in C#? Maybe it's just coincidence that the game looks almost identical to mine, but with minor changes.

 

Yes, the the game is based on your source code, only minor changes and render engine with directdraw. I once informed you via email, have you forgot that?

[wyrd]

I remember, but I didn't remember who it was. Still, what you said is misleading.

 

Now back to the subject at hand. :P

 

20 megs isn't that much in this day and age. Plus, future versions of windows will ship will .NET installed, and it's already on the windows update site.

 

For a real application that is shipping on a cd, it could just check to see if .NET is installed, and if not go ahead and install it. It doesn't take the user any longer then hitting the "next" button and waiting 1 minute.

[Liu Junfeng]

Although, .net is slow for game programming and 3D animation

[wyrd]

LOL.. what?

[bri189a]

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). I used to do VB6 before .NET; I thought it was cool at the time. Then my friend told me about C#. Something C based but not so intemidating as C++. I did take a C++ course once, got a 102% as a final grade (extra credit)... but I didn't pursue it. I don't miss messing with pointers, function declaration, worthless help files that basically give you the syntax and if your lucky that syntax is correct. I don't know how many time the help file would tell me that it was looking for an address and I'd get an invalid parameter run-time error, but once I changed it to a pointer or a static object it worked just fine, or some crap like that. Yes C# is the ultimate language for me. Low-level enough to do cool things and keep the idiots out, but high level enough that you don't spend a day just get the objects on your window to show up, much less work correctly. Now C++ (and Assembly for that matter - yes I fiddled in that a little bit for fun) are something I play with as a hobby. C# is what I moonlight with.

 

Thank-you Microsoft!

 

-Microsft Tool

:)

[Heiko]

.NET is slow.

 

I can not recall to ever have worked with an IDE that needs to contemplate 10 seconds over simple cut & paste questions. :(

 

Apart from that ... it*s ok ;)

[divil]

Sounds like it's time for an upgrade ;)

[Heiko]

2003 didn't look much better in our tests.

But that was way back in March.

 

Do I understand you correctly? There have been significant improvements?

Or is this a hint to upgrady my hardware :) :)

[Robby]

.NET is slow.

 

I can not recall to ever have worked with an IDE that needs to contemplate 10 seconds over simple cut & paste questions. :(

 

Apart from that ... it*s ok ;)

 

There must be something wrong with your system.

 

I find that 2002 has better intellisense (VB) then 2003. The Find/Repplace also.

[cyclonebri]

bri189a said

Yes C# is the ultimate language for me. Low-level enough to do cool things and keep the idiots out, but high level enough that you don't spend a day just get the objects on your window to show up, much less work correctly. Now C++ (and Assembly for that matter - yes I fiddled in that a little bit for fun) are something I play with as a hobby. C# is what I moonlight with.

 

I couldn't agree more with the comments on C#. I have also switched from VB to C#, for almost exactly the same reasons. I am glad to get the power of C and the RAD of the .Net IDE. It has been nice. Now if Microsoft would just quit coming out with new Studios every year...

[Nerseus]

Now if Microsoft would just quit coming out with new Studios every year...

 

As long as they keep fixing them and making them better (there are still a number of troublesome bugs), let them come out every year (or sooner)!

 

Anyone remember VB4? By the time my company ran through the first phase of conversion from a VB3 project, they were already up to VB5. That was a whole new, major release (using version number as a "major" release). I believe it was a little under a year for that one, too.

 

.NET evil? Maybe. I think it's fun, as do most of you - or else we wouldn't be here talking about it :)

 

-Nerseus

[cyclonebri]

As long as they keep fixing them and making them better (there are still a number of troublesome bugs), let them come out every year (or sooner)!

 

Don't forget offering them at substantial upgrade discounts, like the 30 dollar deal that was going on earlier...or better yet, something that is free like webmatrix, only as powerful and complete as VS.net's IDE.

[wyrd]

Both Java and C++ have the keyword this.