https://www.infopathdev.com:443/forums/41.aspxIf you're not sure where to ask your question, ask it here. If necessary, our moderators will make sure it gets classified in the correct board.enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/105527.aspxMon, 15 Feb 2016 20:57:32 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:105527gtrahern0https://www.infopathdev.com:443/forums/thread/105527.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=105527Nevermind on this question, we've found a much more elegant solution using the sharepoint client side object model. Thanks.https://www.infopathdev.com:443/forums/thread/105516.aspxMon, 15 Feb 2016 16:53:13 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:105516gtrahern0https://www.infopathdev.com:443/forums/thread/105516.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=105516We are in the process of testing the following scenario: -infopath filler xsn published to sharepoint 2013 doc library -using filler because of C# code we want to run in full trust on the client -C# project references a couple external APIs (open xml sdk, open xml power tools, etc) -Related to previous bullet, we're outputting our infopath data to a word template on button click When we save the xsn, it's 16 mb, obviously way larger than we would want to load on sharepoint and obvious to me that it embedded the c# project with external assemblies included. And yet the c# project is saved externally as well in it's own location. Did it for some reason wrap the c# project up into the xsn file? Is there any way around this to keep the form template separated from the c# project and keep the xsn very small, maybe a setting we're missing?. We're new to infopath dev and got our code to run and successfully output into word, but the filesize is a deal breaker if we can't get that much smaller, we expect our file to be kb and nowhere near the mb mark. Ideally i'd like to have our xsn on sharepoint, and have our c# assembly and other assemblies saved in a shared directory accessible by all the users that will use the form, but that maybe isn't how infopath is designed to work. Thanks in advance for any tips you can give on this scenario.