C
Chris
Hi,
on what OS is .NET currently supported ? mac, unix, ... ??
thnx
Chris
on what OS is .NET currently supported ? mac, unix, ... ??
thnx
Chris
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
S
Scott M.
From MS - only Windows. There is a version of the .NET Framework for Unix.
I don't have the name of the company that provides it, but search this
thread, it is mentioned.
I don't have the name of the company that provides it, but search this
thread, it is mentioned.
M
Michael Giagnocavo [MVP]
Microsoft has Rotor (search MSDN), which runs on BSD, Mac OS X, and maybe
some others.
www.go-mono.com has support for others.
-mike
MVP
some others.
www.go-mono.com has support for others.
-mike
MVP
C
Chris Taylor
J
John Montgomery [MSFT]
There's more detail on the specific versions of Windows supported at
http://msdn.microsoft.com/netframework/technologyinfo/sysreqs/default.aspx.
John
http://msdn.microsoft.com/netframework/technologyinfo/sysreqs/default.aspx.
John
M
Michael Giagnocavo [MVP]
CLR means Common LANGUAGE Runtime. How does WinFS defeat a common language?
-mike
MVP
-mike
MVP
T
Tian Min Huang
Hi Alvin,
I agree with Mike that WinFS does not defeats the purpost of the CLR. As
you know, WinFS will be implemented in Longhorn (next version of Windows).
You are writing system specific program targeting Longhor and later if you
use WinFS,
Have a nice day!
Regards,
HuangTM
Microsoft Online Partner Support
MCSE/MCSD
Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
I agree with Mike that WinFS does not defeats the purpost of the CLR. As
you know, WinFS will be implemented in Longhorn (next version of Windows).
You are writing system specific program targeting Longhor and later if you
use WinFS,
Have a nice day!
Regards,
HuangTM
Microsoft Online Partner Support
MCSE/MCSD
Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
R
rs_tiin
Hi
You can use the following
a) for Mac OS
Rotor : The SCCLI framework provided by M
b) For *nix : you can use dotgnu or mono
As to the stuf about Avalon WinFX etc. I think there is a
gap here. When we talk about .Net, we talk of the CLI.
The CLI is the Common Language Infrastructure, a standard
that has been submitted by MS to ECMA.
Now this CLI has been implemented by Microsoft and this
implementation is what is CLR or the Common Language
Runtime. Similarly DotGnu and Mono have come out with
their own implementations(CLRs) based on the same CLI
standards
The CLR here is the binding glue which looks at the tasks
of memory Management, Type Safety, Type verification,
Garbage Collection and other thuings. These features are
available in the MS CLR, DotGnu CLR, and the Mono CLR
That said, one level above the CLR is the FCL or the
Framework class library which provides the infrastructure
in the shape of pre-written libraries. Now these
libraries can be different in different vendors. So MS
might give a class library which caters to Avalon related
priogramming, whereas others might not. So i think
binding the FCL to the CLR is not the right thing to do
So i think the answer to the question "on what OS is .NET
currently supported ? " should be not based on the FCLs
but as to the implemntation of the CLR on the OS and i
think the answer to the question is as above
hth
regards,
sr
You can use the following
a) for Mac OS
Rotor : The SCCLI framework provided by M
b) For *nix : you can use dotgnu or mono
As to the stuf about Avalon WinFX etc. I think there is a
gap here. When we talk about .Net, we talk of the CLI.
The CLI is the Common Language Infrastructure, a standard
that has been submitted by MS to ECMA.
Now this CLI has been implemented by Microsoft and this
implementation is what is CLR or the Common Language
Runtime. Similarly DotGnu and Mono have come out with
their own implementations(CLRs) based on the same CLI
standards
The CLR here is the binding glue which looks at the tasks
of memory Management, Type Safety, Type verification,
Garbage Collection and other thuings. These features are
available in the MS CLR, DotGnu CLR, and the Mono CLR
That said, one level above the CLR is the FCL or the
Framework class library which provides the infrastructure
in the shape of pre-written libraries. Now these
libraries can be different in different vendors. So MS
might give a class library which caters to Avalon related
priogramming, whereas others might not. So i think
binding the FCL to the CLR is not the right thing to do
So i think the answer to the question "on what OS is .NET
currently supported ? " should be not based on the FCLs
but as to the implemntation of the CLR on the OS and i
think the answer to the question is as above
hth
regards,
sr
C
Clif H
the MS patent that was part of the ECMA submission was
very broad, does it's submission to the ECMA standard
_guarantee_ it's free usage cover any and all parts of a
..NET reimplimatation or just the cli/clr, c#? can the
patent be used to collect royalties on other aspects of a
..NET reimplementation?
very broad, does it's submission to the ECMA standard
_guarantee_ it's free usage cover any and all parts of a
..NET reimplimatation or just the cli/clr, c#? can the
patent be used to collect royalties on other aspects of a
..NET reimplementation?