Could not load type 'Namespace.Global' - one man's solution

Here's what we did to resolve the Could not load type
'Namespace.Global' issue...

the setup: asp.net app, iis 6, home directory is a share located on
another computer.

our solution: ymmv
1. start > control panel > admin tools > ms .net framework 1.1
configuration
2. runtime security policy > machine > code groups > all_code
3. right click to create new code group, give a resonable name > next
4. choose a condition type of URL (yes, you can add a file share here)
5. ex. //servername/share/somefolder/* (* = all assymblies under the
location)
6. shoose use existing permission set of FullTrust > next
7. thanks to the good folks at http://gnonug.xocomp.net for the info.

I would like some feedback on the pros/cons of this approach as well
alternatives.

One drawback is that giving full trust to assemblies on a network
share exposes another opening if someone wants to get malicious code
to execute on the web server.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On 8 Dec 2004 07:17:57 -0800, "heromull" <heromull@gmail.com> wrote:

>Here's what we did to resolve the Could not load type
>'Namespace.Global' issue...
>
>the setup: asp.net app, iis 6, home directory is a share located on
>another computer.
>
>our solution: ymmv
>1. start > control panel > admin tools > ms .net framework 1.1
>configuration
>2. runtime security policy > machine > code groups > all_code
>3. right click to create new code group, give a resonable name > next
>4. choose a condition type of URL (yes, you can add a file share here)
>5. ex. //servername/share/somefolder/* (* = all assymblies under the
>location)
>6. shoose use existing permission set of FullTrust > next
>7. thanks to the good folks at http://gnonug.xocomp.net for the info.
>
>I would like some feedback on the pros/cons of this approach as well
>alternatives.