I know there have been various threads on "how big is my program?" but I don't think there is a good, clear explanation here or on the Wiki yet. I'm banging my head on the ceiling for code size at the moment. I've learned that when an application is too big to deploy all you get from VS is the error "An error has occurred. Please check your hardware" and that a little more information is shown in the output from 'Micro Framework Device Deployment' e.g.: Incrementally deploying assemblies to device Deploying assemblies for a total size of 141280 bytes Assemblies not successfully deployed to device. Deployment to the device was not successful. And I understand that 141280 is much bigger than the N+ can handle (which I assume to be 65536). In helping me get to finding what assemblies are causing such application bloat, I'm looking at the start of the debug output of a successful delpoy which appears to contain details of per assembly sizes but I don't understand how these relate to the physical constraints of the target device. For example: Attaching deployed file. Assembly: xFxMF (184.108.40.206) (2644 RAM - 31216 ROM - 11306 METADATA) Attaching deployed file. Assembly: HTTP (220.127.116.11) (2152 RAM - 26640 ROM - 8930 METADATA) Resolving. Total: (16536 RAM - 159476 ROM - 73739 METADATA) What do the figures for RAM, ROM and METADATA mean? Can they help me to trim my oversize application down?
No replies to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users