I am wondering why deployed packages are so much smaller than built packages. What is removed and why isn't it removed when the packages are built?
I have a package that goes from 3Mb to 1.5Mb
Any answers|||We don't remove anything from package during deployment. The things that may affect package size:1) XML encoding. UTF-16 (usually called just "Unicode") may take twice as much as UTF-8. I think we use UTF-8 in most places, but not sure.
2) Encryption. If you encrypt the whole package (instead of just sensitive information) it may noticeably increase package size.
How you do deploy, and to what location?|||
You're spot on with the unicode, which concerns me.
The package file in the bin folder is unicode with no directive in the xml clause i.e. <?xml version="1.0"?>, the deployed file is utf-8 but with the same xml directive.
The file is deployed by double clicking on the deployment manifest and selecting "file system".
Surely this is a problem if the package contains unicode, whats more it means the file being deployed isn't the file that is built. Thats not common practice
|||Interesting. Did you do anything special with the package?I always get utf-8 encoded DTSX files (you are right, without encoding specified in XML clause): both the project folder and bin folder contain utf-8 encoded files. I don't know a way to make designer save utf-16 files.
No comments:
Post a Comment