Greetings
In what is/was my last attempt at coding an application in C# ( ) ...For reasons of "Expediance" (HA!). I have an application that runs perfectly on local machine, but won't execute or even load from a network share.

Now, seeing that I've no intension of romping through the entire company manually installing this thing on every &*% machine in the building...I'd like to have it run from a share so that any updates necessary only need to be done ONCE!

So...Is there a way of setting the .NET v2.0 configurator options via Domain Group Policy so it'll Oke'Doke this thing into running? Or do I have to start from scratch and recode this thing in C++ so it acts like a proper application?!?

I've got it running on a test box now but that required installing the ENTIRE .NET SDK...Just so I could give Full Control permission to anything running in the Intranet Zone...Which is neither a wise or acceptable option.

Any Suggestions Appreciated

Stoic Joker

I understand your pain Phonics, but as I no longer manage our company domain, I haven't worked through the proper solution.

However, it would be appear that the best practice is to use the Runtime Security Policy | Create Deployment Package option in the .NET Framework 2.0 Configuration software to make an MSI in which that's a trusted assembly and then distibute it to each machine using Group Policy -or- Microsoft Systems Management Server.

Let me know how it goes though and good luck.

Well...That just gave me an empty .msi package *Sigh*

One thing I have noticed is that the Trust an Assembly wizard keeps giving me a "Hash for assembly cannot be generated" error.

So I'm guessing that there is something specific in the Compiler settings that isn't being included in the application.

...Ah! the shear joy of nice and simple pure Win32 API C++ code ... that would just $&%^^#$* run.

If this is progress, I want my stone ax back

Yeah, I've seen that same hash error Phonics, but unfortunately, I'm not sure how to resolve that either.

Well got the Hash thing figured out (for all the good it did me) Still No Joy.

Now the policy wizards think it just "Dandy" ... but ... It STILL won't run from the share. ...Unless I drop a hammer on the .NET config to globally allow ANYTHING to run (This is on a per-Machine basis of course AAAAAAAARRRGGGG).

I just pissed 300+ hours down the drain coding an application that "Works Fine" but is COMPLETELY USELESS.


Now I gota rewrite the damn thing from scratch in a proper code form that actually runs reguardless of where you put it with out whinning about having a note from mommy and pissing its pants.

I recently moved one of my apps over from VB6 to VB.NET 2005, and I ran in to the same problem of it not running on a network share. After doing some research on the net, I found a command that allows me to give access to certain network shares:



Once I run that command, then I am able to run my program from that network share. But I agree that it's completely stupid that I have to do this. The majority of the programs I write at work run from network shares so I can easily update them, but having to run that command on every computer just stinks. In the past I have done most of my coding in VB6, but VB.NET 2005 just has so many more nice features. But I can't stand all of that security crap.

Hmm, well still good to know Chug, so thanks for the tip.

God Damnit Chug ... You are officially my favorite person on the planet!!!!!!!