Hi Kurtis,

I'm no interop expert, but here's a thread that may or may not help you:

http://forums.microsoft.com/MSDN/Sho...53976&SiteID=1

I'd try another group if this doesn't help (maybe
microsoft.public.dotnet.framework.interop).
--
Regards,

Jake Marx
www.longhead.com


[please keep replies in the newsgroup - email address unmonitored]


Temporalis wrote:
[This question may belong in another group (some sort of .NET or C#
group). If it does, please point me in the right direction!]

I've created a DLL in C# (VS2005, using .NET framework 2.0) for use
with Excel XP (to provide some business logic, as well as connectivity
to various components of our business applications). The same DLL is
also to be used with Project 2003. I've created the DLL as COM
Visible, and registered it properly - it works properly in Project
2003, which is what I've been using to test it (thinking that it would
work fine in Excel as well).

My problem is that now when I try to use the DLL from Excel XP, I get
an error on creating a "new" class from the DLL - and because of this,
I can't use any of the classes in the DLL.

For example:
--------------------------------------------------------
public sub tester()
{
dim x as myDLL.myTestClass 'Statement 1
set x = new myDLL.myTestClass 'Statement 2
}
--------------------------------------------------------
Statement 1 executes just fine - intellisense even figures out all the
class members (so if I were to start typing "x.testM", it would figure
out it was "x.testMethod").
Statement 2, however, I get an automation error on - without any
description:
--------------------------------------------------------
"Run-time error '-2146232576 (80131700)':
Automation Error
--------------------------------------------------------

The exact same sub, however, works without any problems at all in
Project 2003. Note that I don't use any Office Interop libraries
(This is a very simple class I created to test this problem, so it
basically has 1 method that sets the only variable in the class, and
has a default myTestClass() constructor), so I don't know why it
doesn't work in XP.

Would anyone be able to help me here? Have I somehow used a COM
format that doesn't work with XP? Does anyhow have an insight that
can help?

Thank you in advance!
- Kurtis W. Story