I am converting a VS.NET Web app from .NET 1.1 to .NET 2.0. This web app has a Windows installer deployment package that works just fine with 2003. On 2005 however after meticulously converting it to be the same as the 2003 one, building it and running it, I get the following:

Error 1001. Unable to get installer types in the C:\inetpub\wwwroot\CAMWEB\CAM.Web.dll assembly. --> Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.

Sounds simple right? I've looked all over the place to find information about this error message and am coming up blank. I enabled logging as suggested in the FAQ - I don't see anything that indicates what the problem is. I did find one clue on the 'net somewhere that suggested this kind of error is a problem with the Custom Actions.

Also, I researched LoaderExceptions and cannot find out how to access this property. When I throw an exception for errors in the Installer class, it doesn't activate, so it seems the error is not occurring in the custom action code itself.

Additional info: The installer has a custom Install class (in Installer1.cs) that adds a few lines of XML to a configuration file. If the error is in there it is hard to see where, because this code is relatively simple.

Please help... ANY pointers or info would be appreciated, whether you know what the message refers to specifically, or tips on getting at the LoaderException property to find out what's going on. [8|]


Thanks,
David
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
If this was my project, I'd be using ProcMon (or your favoured process/file/registry monitor) to see what activity's taking place right before this message.
Answered 09/10/2008 by: VBScab
Red Belt

Please log in to comment
0
I tried using ProcMon and I cannot see any evidence of what is going wrong. Not sure if I am not looking for the right thing?? I isolated down MsiExec.exe but I see a bunch of system-level requests and nothing to indicate to me that it's failing on a particular file.

I've redone my conversion multiple times and this time did a direct, straight, no replacement of DLLs at all conversion from VS 2003 to VS 2005. The Web application runs flawlessly when I build it and point IIS to it. This installer is supposed to be installing it onto a system. Worked perfectly in 2003, doesn't in 2005.

And I'm still having the problem. [8|] Please help if you've seen this error before or know what could be the cause of it. It is definitely the custom actions, I removed them and was able to install and uninstall...
Answered 09/19/2008 by: dchapman
Yellow Belt

Please log in to comment
0
FIXED :)


This was driving me crazy for so long but I started playing around with the project, convinced it just needed some tweak to get it to work from 2003 to 2005 (because as we all know the conversion wizard is not perfect) and when I re-added the custom action again pointing at the bin instead of the Web App Project folder the installer works now. For some reason this setup worked fine in 2003 but in 2005 I had to point it directly to the Bin to get it to recognize other DLLs I had referenced.
Answered 09/19/2008 by: dchapman
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity