VSTO - assemblies & what I don't understand 1

[cramd2]

I am working some tutorials to understand VSTO 2003 with VB.Net 2003. I've worked several of the tutorials on my local machine, next step of the tutorial shows me how to run my application on a network drive. I've tested the application on the network drive and all works fine, next I try testing the application on another's pc and it fails with an error about security policies. I've done some research and realized I need to add a machine level policy for the .xls workbook and the assembly on each user's pc that will be running this application. MY QUESTION IS - I don't like running around to "every pc" and adding the assembly paths. Is there another way around this, possibly upgrading to VSTO 2005, or do I create my application on the network share in the very beginning to avoid this issue - OR is there no way around this and for anyone using a VSTO application on the network share, I have to modify each pc for machine policies??
cramd2

 

[jebenson]

I'm not sure about VSTO, but .NET apps running across a network will not run locally on a PC until you change the >NET Framework security settings on that PC to allow the app to run. You cannot change these remotely, or with the installation program...its a security measure.

To make the change, go into Control Panel->Administrative Tools->Microsoft .NET Framework 1.x Configuration, then click on the link titled "Configure Code Access Security Policy". In there you can select "Increase Assembly Trust" and browse to your app, then set the trust level. You can also select "Adjudst Zone Security" to make it so any assembly on the local network (LAN) will run on the PC, and you won't have to do this for every app you deploy on your network.



I used to rock and roll every night and party every day. Then it was every other day. Now I'm lucky if I can find 30 minutes a week in which to get funky. - Homer Simpson

 

[cramd2]

jebenson,
Thank you for the information, it is very helpful. I definitely need to understand the trust levels - my choice would be to Adjust Zone Security for all assemblies to run on the network. Although, by changing the security zone, I'm not sure what security risk I am opening up.
Again, thanks for the info, I will be testing my application with the change of settings that you indicated.
cramd2

 

[chiph]

The security permissions can also be set by a domain administrator and pushed down to the PCs via the group policy editor.

Chip H.


____________________________________________________________________
Donate to Katrina relief:

http://s1.amazon.com/paypage/PELYGQVJ8Q7IB/103-6821258-5919825

If you want to get the best response to a question, please read FAQ222-2244 first

 

[cramd2]

Ah....but that's only if you have a Domain, much less a Domain Administrator.......
I'm not so lucky to have this.
cramd2

 

[jebenson]

Chip,
Good one, I didn't know that. Have a star!


I used to rock and roll every night and party every day. Then it was every other day. Now I'm lucky if I can find 30 minutes a week in which to get funky. - Homer Simpson

 

[chrissie1]

The security permissions can also be set by a domain administrator and pushed down to the PCs via the group policy editor.

Our server is in the basssement, so we can't push them down. Now what?

Christiaan Baes
Belgium

I just like this --> [Wiggle] [Wiggle]

 

[earthandfire]