Re: gacutil and co. DLL built under 2beta, deploying to IIS5+DotNet Framework 1.1?
From: Tim Hanson (t.hanson_at_faz.de)
Date: 10/15/04
- Next message: i.r.f.: "Re: Problems installing .Net Framework 1.1 SP1"
- Previous message: Meats: "Re: New install of Upgrade VS2003 CDs"
- In reply to: Tim Hanson: "gacutil and co. DLL built under 2beta, deploying to IIS5+DotNet Framework 1.1?"
- Messages sorted by: [ date ] [ thread ]
Date: 15 Oct 2004 05:14:13 -0700
(open letter to self :)
sometimes we get enough help through other channels to answer our own
questions. makes sense to share the result, eh?
I learned from an MSFT guru that 1.1 and 2.0 assemblies are *not*
interchangeable and that I should recompile with the 1.1 framework. so
i did the following:
1) copied my source tree to a machine where 1.1 was installed and ran:
csc /t:library /out:my.dll webref/x/Reference.cs my.cs
[copied the tree so that my web reference, strong name key, ... would
be where I hoped they'd be expected. presumably one can copy
significantly less, but that's harder anyway...]
2) copied my.dll to the target machine that has the 1.1 framework
3) ran gacutil /i my.dll and regasm my.dll
NB: drag and drop to c:\winnt\assembly now ran without error, but I'm
not sure if it would really work. (i had a couple other errors along
the way and haven't gone back yet to check.) peeking at the DLL with
CompMgr gave me the impression it wouldn't work (I did not see the
class and kith))
4) tested and got
mscorlib error '80070002'
File or assembly name 7zblux2w.dll, or one of its dependencies, was
not found
at a line in my ASP script *after* the service object was
instantiated, but the first time a method was called. searched, found
a question from a year ago (2003-10-22 -- in the parallel aspnet group
re "mscorlib error '80070002'") and this rang a bell: a couple days
ago i had a different-sounding error solveable by giving the local
user ASPNET write permission in c:\winnt\temp (and children).
5) gave ASPNET that permission. (i'll want a different user at some
point, but...)
bingo. this is one chapter of what ended up being quite a saga for my
first small app (a SOAP interface), but i learned a lot (and beginners
typically need time before they can crawl).
on balance i think it was worth the trouble: when the WSDL is clean,
adding it as a web reference in Visual Studio is pretty painless. more
work with environments than actual coding, but for a small application
that makes sense.
cheers,
Tim Hanson
- Next message: i.r.f.: "Re: Problems installing .Net Framework 1.1 SP1"
- Previous message: Meats: "Re: New install of Upgrade VS2003 CDs"
- In reply to: Tim Hanson: "gacutil and co. DLL built under 2beta, deploying to IIS5+DotNet Framework 1.1?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|