GAC dll registration trouble

[Guest]

I'm new to the Global Assembly Cache, so pardon my ignorance on this part.

I'm having an issue trying to add a proprietary dll that came with a software package that was purchased. The DLL apparently doesn't have a strong name assigned to it. What I was wondering is, is this a problem with the DLL itself, or do I need to build a strongly named wrapper assembly dll around the existing DLL in Visual Studio .NET? If the latter, are there anything I should be aware of when building the wrapper

Any help is appreciated.

 

[some guy with a computer]

my guess would be they don't want you to put it in the GAC

the assembly would need to be signed when compiled, unless delayed signing
was specified

I doubt they would do that and let you sign it.

Ask them if this is ok with them. Maybe they'll sign it for you and
re-release it, then again maybe they don't want you using it like that ;-)

I'm new to the Global Assembly Cache, so pardon my ignorance on this part.

I'm having an issue trying to add a proprietary dll that came with a

software package that was purchased. The DLL apparently doesn't have a
strong name assigned to it. What I was wondering is, is this a problem with
the DLL itself, or do I need to build a strongly named wrapper assembly dll
around the existing DLL in Visual Studio .NET? If the latter, are there
anything I should be aware of when building the wrapper?

 

[Guest]

Hmm. They say in the manual to feel free to put it in the GAC, so it could be an issue with their code. Guess I'll contact them to find out. Thanks for the response!