First drawback i see is that it increase the filesize of your
application.....

--
LEBRUN Thomas
http://morpheus.developpez.com

Thanks for your interest in our products.

No, it does not loose any functionality, rather it retains all features of
the original application, including dynamic loading of external assemblies
(don't link such assemblies, and make sure all dependencies are
mini-deployed). The big difference is that .NET Framework is now a part of
your own applications, so the user doesn't really see the Framework in the
picture, and therefore, it may not be convenient if you want to do something
to the framrwork as a whole, such as running the Framework configuration
utility. Framework utilities are not deployed with the application. All
configurations are done at development time, so when the app ships, it
contains an isolated and much smaller version of the framework, which is
internal to the mini-deployed applications. Even when a full framework
exists on the same machine, the mini-deployed app wouldn't know it at all,
which is quite useful considering the many difference versions and service
packs of the framework yet to come.

The mini-deployed applications has all security features of the original
.NET app. In the case of a managed user control under IE, there is a little
difference in the HTML that deployes the control. When full .NET framework
exists, you can use the extended <object> tag to embed the control, however
when mini-deployed, it rolls back to the regular scenario of a traditional
ActiveX control.

I guess a mjor difference also lays in terms of upgrades. When a
mini-deployed app needs to a new version of the framework, you need to
re-generate the mini-package to contain the latest subset of the framework.