ERROR: Call to Interop.VBA.dll

[Mauro]

Hi,

we are finding some very strange behaviour in an ASP.NET application that
references a VB6 DLL. When the reference is created to the VB6 DLL, Visual
Studio generates an interop DLL for both our DLL and also for the VBA DLL
(Interop.VBA.dll).

When we run our web application, periodically we obtain the following error
message:

Parser Error Message: Access is denied: 'Interop.VBA'.

Source Error:

Line 196: <add assembly="System.EnterpriseServices, Version=1.0.5000.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Line 197: <add assembly="System.Web.Mobile, Version=1.0.5000.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Line 198: <add assembly="*"/>
Line 199: </assemblies>
Line 200: </compilation>

Source File:
c:\windows\microsoft.net\framework\v1.1.4322\Config\machine.config Line:
198

The bizarre thing is that then the problem seems to disappear on its own.
It's as if the application has temporarily lost its' reference and then
finds it again.

Has anyone encountered this before? Does anyone know what the reason for it
is?

Thanks for your help,

Mauro

 

[Mauro]

Just as an update, it seems that the problem occurs when there are multiple
VS.NET instances running on a PC, each loaded with a solution that
references Interop.VBA.dll. Even if we are only running 1 debug session, it
seems that VS.NET gets confused about where to find the DLL. It would be
interesting to hear any additional feedback from anyone that's seen this
and/or can explain it.

Mauro