calling a .NET dll from a .NET dll generates error when compiling

[Richard B]

I added a .NET dll as a reference to my new .NET dll. When I went to build,
I received error "Unable to emit assembly: Referenced assembly
'CrystalReport' does not have a strong name". "CrystalReport" is a .NET dll
I built which calls the third-party Crystal dll. I have no problem when I
call the "CrystalReport" dll from my .NET executables.

I never had to call a .NET dll from a .NET dll before. I figured it would a
no-brainer as we're calling managed code from managed code.

Any ideas? Thanks.
--
Richard B

[Frans Bouma [C# MVP]]

Richard B wrote:

I added a .NET dll as a reference to my new .NET dll. When I went to
build, I received error "Unable to emit assembly: Referenced assembly
'CrystalReport' does not have a strong name". "CrystalReport" is a
.NET dll I built which calls the third-party Crystal dll. I have no
problem when I call the "CrystalReport" dll from my .NET executables.

I never had to call a .NET dll from a .NET dll before. I figured it
would a no-brainer as we're calling managed code from managed code.

Sign the crystalreport dll you wrote. You can't call a method in an
unsigned assembly from a signed assembly, as that would make the
signing of the calling assembly void. (calling insecure code can return
data to the signed code, etc. )

FB

--
------------------------------------------------------------------------
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------

[Richard B]

Thanks, I had forgotten about that. By signing the dll, I was able to
compile the code.

Thanks again.
--
Richard B
"Frans Bouma [C# MVP]" wrote:

Richard B wrote:

I added a .NET dll as a reference to my new .NET dll. When I went to
build, I received error "Unable to emit assembly: Referenced assembly
'CrystalReport' does not have a strong name". "CrystalReport" is a
.NET dll I built which calls the third-party Crystal dll. I have no
problem when I call the "CrystalReport" dll from my .NET executables.

I never had to call a .NET dll from a .NET dll before. I figured it
would a no-brainer as we're calling managed code from managed code.

Sign the crystalreport dll you wrote. You can't call a method in an
unsigned assembly from a signed assembly, as that would make the
signing of the calling assembly void. (calling insecure code can return
data to the signed code, etc. )

FB

--
------------------------------------------------------------------------
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------