application. This may make the deployment easier ;).
for linux. -
"Frank Lesser [LSW]" <Frank-Lesser@lesser-software.com> wrote in message
news:uHo#mCPyDHA.2440@TK2MSFTNGP12.phx.gbl...
>
> "Richard Grimes [MVP]" <read my sig> wrote in message
> news:ODovw7KyDHA.2464@TK2MSFTNGP12.phx.gbl...
> > Frank Lesser [LSW] wrote:
> > > We are working on a .NET Native compiler. It will be part of LSW
> > > DotNet-Lab
> > > 2.0 (
www.lesser-software.com/lswdnl.htm )
> >
> > I can understand a C# to native compiler, but a ".NET Native compiler"
> does
> > not make sense. Can you explain what benefit there is in using it?
> >
> > In my opinion, if your product does not have code access security,
> automatic
> > bounds checking, assembly verifiablitiy and validation then it is not
safe
> > to use. If it does not support a sizable subsection of the framework
> library
> > then it is not particularly useful. If you have provided all of the
> security
> > and a good chunk of the library then I would imagine that you would have
> > nearly the bulk of the Microsoft .NET framework (which is free), in
which
> > case I don't see what benefit there is in purchasing another tool.
> >
> > Am I missing something?
> >
> > Richard
> > --
> > my email evpuneqt@zicf.bet is encrypted with ROT13 (
www.rot13.org)
> >
> >
>
> Hi,
> most .NET apps use only a fraction of the framework. We know the topic
very
> well from deploying Smalltalk apps - where you have image sizes comparable
> to the framework size ( Our current Smalltalk Development Image is 60-80
MB
> big - The LSW DotNet-Lab Binary is aprox 4 MB )
> Of course if your imaginary app uses every corner of the framework you
will
> end up with an exe which is as big as the original framework. The current
> modularization of the framework doesn't allow to extract the code really
> needed in an easy way - it is main part of our work adding such a
> modularization concept.
> Frank
>
>
>
>
>
>