SUCCESS!! So, I tried a few different things with some suggestions I received above. Per Bob's suggestion I added [assembly: AllowPartiallyTrustedCallers] to my AssemblyInfo file. I had done this earlier and tested my app and it didn't work but I must have not re-compiled or the old dll was cached or something, because I was doing some other tests and tried it again and sure enough my control loaded just fine.
I did some more research and have some conclusions here that still confuse me a bit but my control works, so... If you use a strong name key(.snk)then you need the APTC attribute in your assembly info or the control will not load. If you remove the strong name key then you do not need the APTC attribute. I did numerous tests adding and removing the APTC and key name attribues to test in which case each was required. In this case my control will be doing File I/O with the client so I will need the strong name so that I can mess around with Code Groups and Permissoin Sets. Thanks again for all your help. =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: Essential .NET: building applications and components with CSharp August 30 - September 3, in Los Angeles http://www.develop.com/courses/edotnet View archives and manage your subscription(s) at http://discuss.develop.com
