.NET Native Code

[Jacky Luk]

Can .NET Version 2002 produce win32 native code?
I'm engaged to a Direct3D project that requires win32
Thanks
Jack

[Jon Skeet]

Jacky Luk <no****@nospam.com> wrote:

Can .NET Version 2002 produce win32 native code?
Well, ngen will do the JITting before runtime, but it still requires
the framework to run.
I'm engaged to a Direct3D project that requires win32

What exactly do you mean by "requires win32"?

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet/
If replying to the group, please do not mail me too

[Jacky Luk]

It's a matter of fact that our clients wouldn't allow us to install the
framework on their machines.
Thanks
"Jon Skeet" <sk***@pobox.com> ¼¶¼g©ó¶l¥ó·s»D
:MP************************@news.microsoft.com...

Jacky Luk <no****@nospam.com> wrote:

Can .NET Version 2002 produce win32 native code?

Well, ngen will do the JITting before runtime, but it still requires
the framework to run.

I'm engaged to a Direct3D project that requires win32

What exactly do you mean by "requires win32"?

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet/
If replying to the group, please do not mail me too

[Willy Denoyette [MVP]]

Jacky Luk wrote:
|| Can .NET Version 2002 produce win32 native code?
|| I'm engaged to a Direct3D project that requires win32
|| Thanks
|| Jack

Not sure what you mean with "requires win32", but only C++ can produce native code not requireing the .NET runtime.

Willy.

[Jon Skeet]

Jacky Luk <no****@nospam.com> wrote:

It's a matter of fact that our clients wouldn't allow us to install the
framework on their machines.

In that case you basically can't use .NET. You can't run .NET
applications without the framework. I gather there's a program under
development to let you do that, but I'm not sure I see why a client
would allow you to install that but not the framework itself..

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet/
If replying to the group, please do not mail me too

[Tim Kurtzman]

If you mean Visual Studio 2002, then yes, it can produce native Win32 code.

Tim
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
--------------------

From: "Willy Denoyette [MVP]" <wi*************@pandora.be>
References: <#d**************@TK2MSFTNGP09.phx.gbl>
Subject: Re: .NET Native Code
Date: Tue, 19 Aug 2003 12:31:37 +0200
Lines: 11
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <eJ**************@TK2MSFTNGP09.phx.gbl>
Newsgroups: microsoft.public.dotnet.general
NNTP-Posting-Host: d5e01079.kabel.telenet.be 213.224.16.121
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP09.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.general:104984
X-Tomcat-NG: microsoft.public.dotnet.general

Jacky Luk wrote:
|| Can .NET Version 2002 produce win32 native code?
|| I'm engaged to a Direct3D project that requires win32
|| Thanks
|| Jack

Not sure what you mean with "requires win32", but only C++ can produce native code not requireing the .NET runtime.
Willy.

[Willy Denoyette [MVP]]

No, I mean VC++ the compiler (part of VS NET) is the only compiler able to produce native code not requiring the .NET runtime,
Visual studio is a development environment.

Willy.

[Huihong Luo]

We will offer two options to deploy .NET applications without installing
..NET framework:

(1) a linker and mini-deployment tool that you can choose to link everything
together (except for mscorlib.dll) into a single EXE, and the tool also
automatically figures out all other dependent DLLs. (You can also choose not
to link assemblies together). A minimum set of CLR runtime is then included
and deployed (~6MB in size) with your application rather than the whole
thing. In this way, a typical windows application will be about 5 MB after
zip, one can simply unzip it onto another bare machine to run the
application. No entries will be added into the client machine's registry.
This scenario still uses CLR underneath, but only the required portion is
shipped, and there is no noticeable installation time.

(2) take one more step from (1), we will offer a native compiler to compile
the linked .NET assembly into x86 machine code. You can then ship the native
code with a runtime (~2MB) to any machines. This scenario does not use CLR
at all. The linking and compiling usually results in a 2.5MB increase on
file size. We will do more optiomization in the future to reduce the size.
Reflections and dynamic loading, etc. are supported. If .NET framework is
also available on the same machine, the native code also supports loading
and invoking external .NET assemblies (seperate DLLs which are still with
MSIL code).

I will post more info on our website (http://www.remotesoft.com) plus sample
code within the following 2 weeks, please visit our page,

Thanks,

Huihong
Remotesoft, Inc.
"Jacky Luk" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

Can .NET Version 2002 produce win32 native code?
I'm engaged to a Direct3D project that requires win32
Thanks
Jack