Here is the situation.

I have a dll (.Net 1.1 C# to be exact)

It has a path harcoded into it inside an include that is used as a
resource.

I hav lost the source to the app, it hasnt needed changed in some time
EXCEPT a server path (refrenced inside that resource a js file to be
exact) is now broken and cannot be changed server side.

I have changed the path in a Hex Editor (I am proficient with a hex
editor and have no doubt it will run and do what I need)

HOWEVER because of the way .Net Strong Name etc is when I try to run
the app I get  The check of the signature failed for assembly
'Foo.dll'

No suprise there since its not quite kosher anymore as far as the CLR
is concerned.

I do NOT care about security on this Dll, or that whole server for
that matter as it is only used internally (not exposed to the web) and
I am in control of everything else that gets installed there.

I absolutley need to be able to have it run.

I tried adding it to the GAC (knew it would fail) here is the error

gacutil -if Foo.dll

Failure adding assembly to the cache: Strong name signature could not
be verified.  Was the assembly built delay-signed?

Ok no suprise there right ? WELL I have read about all the reasons in
the world NOT to use DEVPATH , I dont see it being an issue here, I
NEED to try this option.

Where exactly do I set the DEVPATH and How ? Ok, its an enviromtnal
variable ? I set it EXACTLY where and when ?

OR Is there another way to let a bonked (but functional) previously
stron assembely to run ?

I am in desperate need of a solution, and I dont care what breaks with
devpath as LONG as this app run until I can recreate the source (with
a few new bells and whistles of course :)

I just really really need to know how to make this run again

Please help me oh god of the .Net CLR

Chris