Building XPCOM components with MSVS 2005

[Buffaloaf]

Hello,

I'm having some trouble getting a personal XPCOM component to work
under XulRunner when compiled with MSVS 2005.

This component worked fine when I compiled it using vc7.1. I used the
GeckoSDK 1.8b1. It compiled and runs great. However, I'm working on
migrating all my code to compile with vc8 and I'm having some problems.

When I compile with vc8 I get this JS Error:

Error: uncaught exception: [Exception... "Component returned failure
code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)
[nsIJSCID.getService]" nsresult: "0x80570016
(NS_ERROR_XPC_GS_RETURNED_FAILURE)" location: "JS frame ::
chrome://modzilla/content/js/pkg_zillacom.js :: <TOP_LEVEL> :: line
1202" data: no]
(I believe that I had at one point received an error stating something
about not finding msvcr80.dll)

I, then copied the msvcr80.dll into the xulrunner directory and I
received the error : R6034 - attempt to load C runtime library without
using manifest

So I found the way to compile with the manifest using microsoft's
manifest tool mt.exe

Once I did that I did not get the JS error NOR the R6034 error, but
xulrunner just crashes. With microsoft wanting me to send an error
report. The crash occurs in my component dll. But I don't know where to
go from here.

I attempted to use the /MT linker option to statically link the CRT
into my component, however, that just presented all the previously
mentioned problems of "error LNK2001: unresolved external symbol XXXX"

Currently my XulRunner is v1.8.0.4.

I haven't tried to compile xulrunner, does anyone think that compiling
it with a static CRT is better/worse than compiling with the
MSCVR80.DLL dependency?

Any help would be greatly appreciated.

Many thanks,
Luke