Catch non-existent dll compile errors

I have created a dll in .NET that i use it in excel. End users who use the excel workbook need to register the dll when they first use the workbook. Sometimes, they fail to register the dll and launch the workbook. The workbook has a reference in it to the .dll. As soon as they try to do anything they get a compile error "User-defined type not defined". This is because:

Please Login or Register  to view this content.

and the "unit.dll" has not been registered to work with excel.

What i want to do is to catch and interrupt the compile error gracefully and tell the user to go back and re-register the dll before using the workbook. As it stands now they just see compile error - and well you can imagine when they are looking at the vb screen quite confused.

So i thought maybe i would create a type

Please Login or Register  to view this content.

but you can't have a type without members. And i'm not sure how this would work once someone registers the user-defined type by the same name.

So - any ideas how to solve this problem?

Thanks,

-lta

Can't you just put On Error Resume Next before the New, and test for an error afterward?

Edit: Never mind that, it's a compile error, sorry.

Switch to late binding, and then test for an error:

Please Login or Register  to view this content.

Edit2: Please take a few minutes to read the Forum Rules, and then edit your post to wrap your code with Code Tags.

Don't you still get a compile error if you use early binding in the main code?

You can also test for an add-in using GUID, I think, though I've not used it.