Hi, Our programming sept and IT dept are having a difference of views on .NET and security risk to the network. We have create an application using .NET. WE wanted to put it on a shared drive to push it out instead of having to put it on each local machine, if we put it on each local machine then everytime we have an update or change the program we have to go back through to each machine to update, but wouldnt need to fi on shared drive, IT says that by putting an application created in .net on a shared or remote drive it is creating a hole in the network and causing a security risk. IT said that by using CASPOL to change permissions that is a risk. Does any one know if this is true or how it works. Thank you

I'm not familiar with CASPOL. However...

You might be able to solve this problem but employing 1 click web deployment. You can deploy an application installer that is accessed thru a browser for installation. The app can be configured to automatically check for updates. This can happen at a configurable interval (every app startup or based on some time interval). Once installed, the app will check for updates based on the configuration. This way you can deploy to a single location and the apps will update themselves. This should make everyone happy. (Although, are IT people every really happy with us programmer? ;)

-Peter

Peter

Thank you for all your help and yes you are correct, when is IT ever happy with programming. It is a thorn in my side especially because my boss has to me I have to get them to play nice. LOL

Sounds like running .Net assemblies on a network share is a classic problem. But rather than having some sort of security policy via AD, it seems a lot of people resort to using caspol.

Threads like this are typical.

This guy does a nice job in his MS blog to explain caspol usage.

Can any of those models be used in an entry?











__________________________________________________
heroes seasons 1-4