Hi
I have a VB.Net exe on the network, for my client PC to use the program, i had to go round all the PCs and use the framework wizard to trust an assembly.

I am now at the point where I want to update the exe file, in doing so I will have to go round ALL the PCs to repeat the task above. Surely there must be a better way??

I have tried looking at caspol

caspol -addgroup 1 -appdir file:S:\customApps\Temp\ FullTrust

though I am a little confused and not sure of the syntax above, could someone point me in the correct direction or preferred method on handling this.

Thanks

Hi Daniel,

I was having the same issue and I solved it as follows.

First of all u have to generate a public key for the application. There is a utility provided in the Visual Studio 2003 command prompt (i dont remember the name right now, but u can search on web, it provides all info on how to generate public key file). This key file will be something like xxx.snk (snk being the extension).

Then in your assembly info file, add the path to this key. The when you build your exe, the public key will get added to your application.

Now when u use the trust wizard for the first time, it gives u two options (give access to this assembly, which u are probably using and the other option is give access to all assemblies with the same public key). select the second option. Once u do that, u wont have to do the trust wizard everytime u do a new exe (as long as u dont change ur public key file )

Thanks

Balu
:)