K
kanaille11
Hi,
at the moment we're experiencing path issues. From what I know, a .NET-
assembly is looked up
1) in the GAC
2) in the EXE's directory
3) if specified in the app.config-file, in a subdirectory or in an
arbitrary location
What I need to know is this:
we have a COM-component (written in .NET) which references a .NET-
assembly with some business logic. Let's say these DLLs are in d:
\TheProject\bin\debug. The COM-dll is registered with
regasm SomeCOM.dll /codebase
A test application is under c:\program files\TestApp and opens that
COM-component. Although the .NET-assembly doesn't meet any of the 3
criteria, it can be loaded. Why is that? Where is that specified? Is
this always the case when using COM-components?
mfg Steven
at the moment we're experiencing path issues. From what I know, a .NET-
assembly is looked up
1) in the GAC
2) in the EXE's directory
3) if specified in the app.config-file, in a subdirectory or in an
arbitrary location
What I need to know is this:
we have a COM-component (written in .NET) which references a .NET-
assembly with some business logic. Let's say these DLLs are in d:
\TheProject\bin\debug. The COM-dll is registered with
regasm SomeCOM.dll /codebase
A test application is under c:\program files\TestApp and opens that
COM-component. Although the .NET-assembly doesn't meet any of the 3
criteria, it can be loaded. Why is that? Where is that specified? Is
this always the case when using COM-components?
mfg Steven