Some time ago I asked about a problem we were having running a .NET Windows application from a shared network resource. I was instructed at that time to run the Framework Wizard to Trust the Assembly. It wasn't the ideal solution, but as it only seemed to occur on our developers' workstations, it was a small hassle. This problem is now occuring on every user's workstation every time we push a new version of the program and I now have to run Trust an Assembly on every users' workstation! Clearly, this is no longer practical and I need a scalable solution.

Is there some way, in version VS 1.0 and Framework 1.0, to tell workstations to trust new versions of the same program so this does not continue to be a problem with each new release? Is there a setting for the project that will make it always trustable? Is there a registry setting that needs to be changed on the workstations to accept the new executable?

Are our choices to either Trust the Assembly on every workstation with each new release or install this directly on the users' machines, or is there some work around to this that's practical?

Hi
I have a similar problem, could someone suggest the preferred method.

I would like to update the .net exe file on the network, though if I do this, no one will be able to run the app, until i go through each client machine and trust the same exe again.

Any help or pointers appreciated.