I have checked through my project and as far as I can tell there is no reason why the following DLL's should be included yet they are.
of most concern are System and System.XML
Just the other day my project was compiling nicely without them but today it is now including them - bloating out my app size by ~1Meg. Now i thought I must have added something to the scene that somehow needs those things. So I though ok if I compile a blank scene (in the same project - ie. create a blank scene and add it to the compile list and tick so only that scene compiles) then it shouldn't include those other dll's. But it still includes them giving me a blank scene that costs 990KB.
So it seems that there must be some things that kick unity into a failsafe mode of including all these things 'just in case'.
This is the second project where I have seen this happening. If anyone has some insights that would be fantastic.
I am aware of the following things: Things in the Resources folder are automatically included (I have no resources folder in my project). Dlls in the plugins folder are automatically included (I have one C# script in the plugins folder but no DLL's). Are there others to add?
All scripts are included, so apparently you have a script that's requiring System.Xml etc.
answered Aug 11 '10 at 02:26 AM