No .NET framework

  • Thread starter Thread starter bob
  • Start date Start date
B

bob

Is there any way to create a Csharp Console application that does not
require the user to have the .NET framework installed?
 
yes...

if you're using Mircosoft Visual Studio, when you compile the solution,
you're generating MSIL Code in dlls...

when you run this code... JIT engine compiles it to a machine language, but
you lose portability, cause it will only runs in another machine with the
same configuration that yours.

i dont remember very well, but i think that u can use an utility named
nmake.exe that cames with the .Net Framework

Greetings
 
when you run this code... JIT engine compiles it to a machine
language, but you lose portability, cause it will only runs in another
machine with the same configuration that yours.
Click to expand...

I don't see how this is relevant nor accurate.

what do you mean by "same configuration", and what do you mean by "lose
portability"? "Portability" refers to running on other platforms, .NET is
non-portable already.
 
same configuration = same OS
loose portabilty = you cant run your app in another OS...
 
Until Mono matures and can genuinlely be called ".NET for non-Windows" then
portability is not achieved.

I'm not being harsh on the Mono project, I'm just saying that .NET is not
portable yet.

Anyway it's a non-issue since "portability" refers to source code, not
binaries. We're talking about binaries here.
 
I've compiled binaries on Windows and run them using Mono.

--
Jared Parsons [MSFT]
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"
 
That's right and so have many others. This discussion other than Jared's
post makes no sense as it does not reflect the internals of the CLR. The CLR
was designed to be multi-platform, multi-language, multi-type out of the box
and is. One only need look at the Rotor source code and docs to understand
this.

--
--------------------------------------------------------------
Sam Gentile [C#/.NET MVP]
..NET Blog http://samgentile.com/blog/
MSDN Column:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/bridge.asp
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
---------------------------------------------------------------
Jared Parsons said:
I've compiled binaries on Windows and run them using Mono.

--
Jared Parsons [MSFT]
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"

gabriel said:
Until Mono matures and can genuinlely be called ".NET for non-Windows" then
portability is not achieved.

I'm not being harsh on the Mono project, I'm just saying that .NET is not
portable yet.

Anyway it's a non-issue since "portability" refers to source code, not
binaries. We're talking about binaries here.
Click to expand...
Click to expand...
 
Sam said:
That's right and so have many others. This discussion other than
Jared's post makes no sense as it does not reflect the internals of
the CLR. The CLR was designed to be multi-platform, multi-language,
multi-type out of the box and is. One only need look at the Rotor
source code and docs to understand this.
Click to expand...

Whatever. If you would like to re-define the question to fit your answer
go ahead. The OP asked the following question: "Is there any way to
create a Csharp Console application that does not require the user to
have the .NET framework installed?"

That's what I was answering by pointing the Op to a producer of software
that allows this to happen.

As to a phylosophical discussion of .NET source code portability vs IL
assembly "portability," we could have it, but it's outside the scope of
the original question.
 
Cesar Garcia said:
have heard about mono?
Click to expand...

Everytime I see this issue of .NET portability come up, someone throws mono
around. For a company to embrace .NET, it needs to be available EQUALLY on
Windows as well as Linux/Unix. Pushing mono was like MS pushing Win32s years
ago. It was a sloppy, buggy, incomplete bandaid. If you really wanted Win32
you needed to be on NT. Equally, if you want .NET you need to be on Windows.

bob
 
Hi,
i dont remember very well, but i think that u can use an utility named
nmake.exe that cames with the .Net Framework
Click to expand...

Yes, there is such a tool. But even compiled you do have to have .NET
installed. That is because before starting the compiled image the loader
check all versions, etc of referenced assemblies. What you actually do using
that tool is that you skip the JITter. But the rest of the work like
loading the assemblies, loading types, versioning, etc is done as with
normal .NET applications.
 
And why should they? Besides if you want it to be portable, load vmWare on
the Unix box and move your app over - Portable...No? <Just Kidding> If you
really want to write console apps and not use any framework or other MS
libraries, then why not just use GNU and vi/emacs, etc. AFAICT, you have
port issues in both directions. To get most unix programs to run on
windows, you need something like Cygwin (or other) right?
 
when you run this code... JIT engine compiles it to a machine language, bu
you lose portability, cause it will only runs in another machine with th
same configuration that yours
i dont remember very well, but i think that u can use an utility name
nmake.exe that cames with the .Net Framewor
Greeting
Click to expand...

The above comments are totally wrong, there is no such thing as nmake.exe, there is a utility called ngen.ex
which generates the native image of the assembly to speed up the application startup. But not somehow eliminate the need of .NET framework itself.
 
Back
Top