I have a VB.NET app which uses the msxml2.dll through Interop. The
application works fine on my development PC, but when installed on a user
machine, the program fails. When a new xml document is created, the
resulting error message says that the com object is "not valid" or is "not
registered."
In the installer world, I was under the impression that any Interop assembly
does not need to be explicilty registered.
Any feedback appreciated.
SC
Pickles The Cat - 26 Jan 2005 02:55 GMT
Go on to that machine ( target ) and confirm taht the msxml2.dll exists.
If not, you might want to
(a) install it there if you have access.
(b) create a Setup program that delivers all the additional COM
components need for your application.
> I have a VB.NET app which uses the msxml2.dll through Interop. The
> application works fine on my development PC, but when installed on a user
[quoted text clipped - 7 lines]
> Any feedback appreciated.
> SC

Signature
incognito...updated almost daily
http://kentpsychedelic.blogspot.com
Texeme Textcasting Technology
http://texeme.com