M
Me 1971
I have an Excel Plugin that uses a number of things defined in the App.Config
File.
Through trial and error Ive discovered that the exceptions I was getting are
down to the fact that my actual config file was not trusted.
If I use .Net2.0 admin I can manually add in this file, based on its url.
But this isnt too helpful on my own PC as I have the Development and Release
locations. I can see further issues when this is deployed as I do not want to
have to manually add the location of the config file to everyones Machine.
So, am I better off modifying the SetSecuirity project to add in another
section to register the config file via caspol, or can I somehow trigger the
granting of full trust to my config file through the MSI setup?
Cheers
File.
Through trial and error Ive discovered that the exceptions I was getting are
down to the fact that my actual config file was not trusted.
If I use .Net2.0 admin I can manually add in this file, based on its url.
But this isnt too helpful on my own PC as I have the Development and Release
locations. I can see further issues when this is deployed as I do not want to
have to manually add the location of the config file to everyones Machine.
So, am I better off modifying the SetSecuirity project to add in another
section to register the config file via caspol, or can I somehow trigger the
granting of full trust to my config file through the MSI setup?
Cheers