.
.
Last edited by Troll_King; 11-30-2001 at 11:23 AM.
Who has Microsoft hired to correct the bugs in Windows? It is a given that they cannot themselves because they lack even the weakest tentative grasping understanding of how an O/S is to be written.
Fundamentals such as Memory Management, Device I/O, and Multitasking are well and far beyond them.
C# was not needed to correct the systemic problems of the existing windows model-- simply experience programmers who've been around long enough to know _how_ and _why_ things should be written in such a way as to _work with the machine, not against it_.
'nuf said.
enjoy.
XP home is also very good (most home users dont need the pro version) - but the best operating system for servers when it is released will be Windows .NET Server (what is currently known as whistler and was going to be xp server at some stage) - it is very very cool
Do not meddle in the ways of dragons, for thou art crunchy and taste good with ketchup
Indeed, Whistler sounds much better...
So what are some examples of this "ability to use technology" and "weaknesses and faults of the current Windows model"? I seem to be able to do anything I please programming Windows now.... A poor programmer will take C# to its knees in about 10 min, I guarantee.
-Justin
Allegro precompiled Installer for Dev-C++, MSVC, and Borland: http://galileo.spaceports.com/~springs/
Actually, I find C# quite easy to learn if you know the MFC or VB or maybe even Java. It has native access to the .NET framework classes. You can easily build windows applications. However, a good programmer will build a nice app, and a bad programmer will write a crawling, buggy app. As with every language, it's up to the programmer to use his/her tools wisely. It's just another language, it won't bring world peace or end hunger.
hth
-nv
She was so Blonde, she spent 20 minutes looking at the orange juice can because it said "Concentrate."
When in doubt, read the FAQ.
Then ask a smart question.
I was fooling around with C#, and stumbled across how to make Windows apps, here's some sample code:
I don't have VS.NET on this computer, just the framework so I couldn't use the form designerCode:using System; using System.Windows.Forms; class MainForm : Form { public MainForm() { Text = "First WinApp"; } public static void Main(string[] args) { Form form1 = new MainForm(); Application.Run(form1); } }
Last edited by -KEN-; 11-12-2001 at 04:29 PM.
Ok, well I just went upstairs to compile this with VS.NET, and it's giving me errors...but it compiles & runs fine with just csc.exe to compile it on both computers...anyone know what I'm doing wrong in VS.NET? some sort of option to set? (I can't even FIND the compiler options for VC#...)
You can get the options by right clicking on the application name in class view and then selecting properties, but I think your code is fine (it ran ok for me using Visual C#.NET as a windows app).
zen
well I just do empty C# project and a a new .cs file. Whenever I try to make a windows app it loads up a new form and stuff, which I don't want.
Create New Windows Application
Delete preset Form1 class
Add class...
Delete preset code from new class
Copy code into new class
...
runs fine on my machine
hth
-nv
She was so Blonde, she spent 20 minutes looking at the orange juice can because it said "Concentrate."
When in doubt, read the FAQ.
Then ask a smart question.
so basically - create new windows app, delete all code, add my code?
sounds like a plan.