Installing the only minimal set of .NET framework...

[G.Ashok]

Hello,

My WindowsApp is using only few of the .NET framework .DLL files. When I
install my app on the clinet machine, I just want to install only
required/used .DLL files of the framework not the whole framework. Because
..NET framework's isze is too big (20 MB like). And after installing it
expands up to 100MB. etc. with all ASP.NET blah blah...Stuff

I wonder how it fulfills the saying that 'XCOPY deployment'

How can I separte the required .DLLs from framework and copy only those
files on the clinets machine along with my app.

Regards,
....Ashok

 

[m.posseth]

well you could check if the compact framework forfills your needs ( it is
ment for pocket pc development )

as far as i know it is not possible to split the framework in smaller
install packages ,


and after the framework is installed you have Xcopy deployment ,, as the
framework will be part of all new operating systems you do not need to
install it seperately in the near future

hth

Miche Posseth

 

[Cor Ligthert [MVP]]

Ashok,

This is so often asked in these newsgroups.

It is the same as when there was Windows 1.0 above Dos (however a disk from
20Mb was than still normal, there are at the moment almost no computers to
buy with a disk smaller than 20Gb).

When it is for a PDA than take Miche advice.

Cor

 

[Herfried K. Wagner [MVP]]

My WindowsApp is using only few of the .NET framework .DLL files. When I
install my app on the clinet machine, I just want to install only
required/used .DLL files of the framework not the whole framework. Because
.NET framework's isze is too big (20 MB like). And after installing it
expands up to 100MB. etc. with all ASP.NET blah blah...Stuff

I wonder how it fulfills the saying that 'XCOPY deployment'

How can I separte the required .DLLs from framework and copy only those
files on the clinets machine along with my app.

In general the answer is "no". The complete .NET Framework must be
installed on the machine. There are commercial solutions available which
will only package reqiured DLLs with your application, but these solutions
stand against the concept of the .NET Framework and there may be legal
issues because it's likely not allowed to distribute only parts of the .NET
Framework.

 

[Michael A. Covington]

My WindowsApp is using only few of the .NET framework .DLL files. When I

install my app on the clinet machine, I just want to install only
required/used .DLL files of the framework not the whole framework. Because
.NET framework's isze is too big (20 MB like). And after installing it
expands up to 100MB. etc. with all ASP.NET blah blah...Stuff

A surprising number of Windows systems already have .NET because it comes in
with several recent Windows updates. This may not be the problem that you
think it is.

 

[Morten Wennevik]

Hi Ashok,

Think of .Net as a form of DirectX. When shipping a game that requires some part of DirectX, the entire DirectX is needed and sometimes shipped with the game.

 

[Vipul Patel]

You will need the complete >NET Redistributable to run your .NET
application. That takes up on 23 MB,,,,,,,,,,,

You dont need to install .NET SDK (@ 100 MB) to get the application running.

Also, you cannot deploy selective components of .NET Framework. That is
illegal.

Vipul