OSDev.org

Of course OS cann't be writen in MS C#.NET but can it be writen in Borland C# ?

Of course OS cann't be writen in MS C#.NET

As long as you can write the nessecery runtimes in C or ASM and link them in instead of the default MS ones you can use any language. However if there are lots of runtimes you may have to completely write the OS in something else before you could use the language (e.g. Java, VB, Basic etc.)

Pete

well c#.net != c#.. one is a language definition, one is a platform...

if oyu had a standalone compiler for c# you could use it like c or C++ for osdev. c++ requires some underneath work to get working properly, c# would be no different.

But C# needs the .NET Platform to run on unless the programs is made in setup pachage to on other Win Sys that don't have the .NET Platform.
so, how to use it ?

You'll probally have to use the compiler from the command line to produce object files that a linker like 'ld' can understand and then link it to a binary, COFF, elf or whatever and then use GRUB to boot it.

As I don't have C#.NET so I can't tell you how everything will work exactly. Try MS Knowledge Base
Pete

There's nothing stopping you from porting the CLI to your OS. We already have a CLI for BSD, so it's not just Windows.

And I sincerely hoped that C# would be a passing craze, dismissed by the development community at large... :-[

Solar wrote: And I sincerely hoped that C# would be a passing craze, dismissed by the development community at large... :-[

I think that C# never really targetted the developers ... but rather the poor Toni Administrati , which usually has no choice but accept it ...

and sarah programatzki?

@solar: you could at least reinstantiate this special page of your former pro-pos site for reader's education. Isn't this a proposal? ];->

Hehe... didn't know so many people actually did read that stuff.

Well, the plan is to bring up some of the stuff again as static HTML. I'm on extended R&R starting next Tuesday, and tending pro-pos.org is definitely on the schedule.

Tim Robinson wrote: There's nothing stopping you from porting the CLI to your OS. We already have a CLI for BSD, so it's not just Windows.

if you had a native compiler you wouldnt need the CLI tho... (native meaning c# -> x86 opcodes) blah.

Depends how you wanted to write your C# kernel code. Am I using the right TLA when I say the CLI is equivalent to the C runtime? I'm not sure. Anyway, if you were programming C#, you'd want to write System.Console.Write instead of printf.

excuse my pinguin-only ignorance ... but ... what is "CLI" in C# ? Command Line Interface ?

Tim Robinson wrote: Depends how you wanted to write your C# kernel code. Am I using the right TLA when I say the CLI is equivalent to the C runtime? I'm not sure. Anyway, if you were programming C#, you'd want to write System.Console.Write instead of printf.

sure, thats what i mean when i said youd need the support code for it. naturally you wouldnt need the entire cli, winforms, etc. just enough to strap the system.

Pype.Clicker wrote: excuse my pinguin-only ignorance ... but ... what is "CLI" in C# ? Command Line Interface ?

Nope. Common Language something. (All .NET languages map to the same intermediate.)