Strong Names



  • 1. how can i make button make dial action?
    hi everyone i have sql database containing the name of person and his telephone number, i select the name from combo box and I want to click on the button make dial action so i can open the port of the modem to dial specific number thanks
  • 2. XP Style and Visual Studio .NET 2003?
    Anyone tried putting XP Style on Visual Studio .NET 2003 to get to see the actual XP design at designtime?
  • 3. What do I need to run and
    What do I need in order to run and Is it possible at all to create pages on a XP home machine? Or do I need to upgrade to a different machine? Can I do this if I upgrade to XP Prof.?
  • 4. C# .NET versus VB .NET
    I'm just getting into the .Net experience from a VC++ (6.0) background, and am looking at the .Net languages. Just wondering what the differences are, in your opinion, between C# and VB, dispite the obvious syntax changes between the two where '}' is 'End Sub', and the fact you can still have "modules" in VB, where as C# is toltally OO. The .Net libraries that are exposed to both seem to be identical, so what advangtages/disadvantages, would one have over the other? Or are they just both for different people, coming from differing programming background, doing essentially the same thing? Thanks. =o) Dan.
  • 5. How can I set the cursor position in VB.NET
    Hi Gang, I would to know how to set the cursor position in VB.NET can somebody tell me how. If not I will resort to API calls (the black art :). Cheers, Christian

Strong Names

Postby Scott Meddows » Sat, 06 Mar 2004 03:05:15 GMT

I have a major problem.

I have a deadline of Monday and I don't know if I can do what I need to do.
(darn Crystal Reports for not migrating to a different server!)

I'm adding a reference to a COM control in VS.  However, my assembly is
signed with a strong name.  When I attempt to compile the exe I get the
error of  "Unable to emit assembly: Referenced assembly 'Interop.SHDocVw'
does not have a strong name"

Is there a way I can tell the compiler to not check this dll for a strong
name?  Is there a way I can have VS generate this proxy WITH a strong name?

Help is needed and appreciated.


Re: Strong Names

Postby Mattias Sjren » Sat, 06 Mar 2004 07:24:06 GMT



Not when using VB.NET no.

But you can use the TlbImp or AxImp tools to generate the interop
assembly instead. They both have /keyfile options so you can give the
assembly a strong name. Then reference this assembly from VS.NET.


Mattias Sjren [MVP]  mattias @
 http://www.**--****.com/ |  http://www.**--****.com/ 
Please reply only to the newsgroup.

Re: Strong Names

Postby Scott Meddows » Sat, 06 Mar 2004 08:39:29 GMT

I've tried to use that tool and it gives me the error that a CSP cannot be
found for one of the classes in the DLL

What I was trying to wrap is the COM Internet Explorer control.

Re: Strong Names

Postby Mattias Sjren » Sun, 07 Mar 2004 08:49:20 GMT


Never seen that before. Can you post the exact command line you used
and the error message you got?


Mattias Sjren [MVP]  mattias @
 http://www.**--****.com/ |  http://www.**--****.com/ 
Please reply only to the newsgroup.

Similar Threads:

1.To strong name or not to strong name a DLL

I'm going to develop an API for an application that then gets published and 
documented to a wider audience.

I'm trying to decide whether I should place the API DLL in Global Assemby 
Cache (as seems to be the official recomendation) or not.

My main question revolves around this issue:
Since it is going to be an API that means that some other parties not known 
to my organisation are going to use it to write "connectors" to their 
software. My idea is to keep the API as a filter between the "native" 
methods, eg when there is new functionality to the application the API would 
not be immediately revised to accomodate for the new features except in a way 
that does not expose a new interface. Example of this would be entering an 
empty string to a new field rather than providing a new function call to 
accomodate for this new field. The API would be revised at a much slower pace 
than the application itself.

The reasoning behind this is, that this would not force the connector 
designers to revise their connector everytime there is new functionality. The 
revised API would include backward compatibility in a namespace etc way so 
that whatever was written some time ago would still work even though the DLL 
is recompiled.

Now the issue I encounter is this, that if I strong name the DLL, it would 
have a new strong name everytime it is updated hence resulting in a situation 
where the "connector" would be still talking to the the old DLL when it in 
fact should be talking to the new one that has the exact same interface but 
internally accomodates for the changes.

Avoiding the DLL hell isn't easy ....

2.Strong Named Assemblies and Non Strong Named assemblies

Hi All

I have a third party .net assembly that I do not have the code for and it 
also does not have a strong name.

I want to strongly name my assemblies but I keep getting an error saying 
that the 3rd party assembly is not signed.

I have had a look at the tlbimp.exe but this looks like it only works for 
ActiveX/COM componants, NOT .Net assemblies.(Unless I am typing in the wrong 
commands....keep getting error not a valid type library)

Is there some compile switch or something that will not check on this 3rd 
party dll for a strong name?



3.Strong Naming a Non-Strong Named assembly


Yes, you can sign it later using sn.exe provided you have the private key of
the public-private key pair.

Delay Signing is something related with module based development where
individual, small teams doesn't have access to the private key for that
organisation. So they sign the AssemblyKeyFile with the public key & set the
AssemblyDelaySign = true to enable to have room for the private key to be
hashed later. Later, the resulting assembly is re-signed using the private
key using the -R switch of sn.exe.


"Gururaj" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...
> Hi,
> Is it possible to strong name an assembly (already existing third party
> assembly) which is not strong named and has been built with /delaysign-
> option.
> Basically my question is can one introduce a /delaysign+ attribute and use
> the sn.exe with "-R" option?
> Thanks,
> Gururaj

4.strong naming an assembly that has non-strong named references?

How can I strong name my assembly if it references 3rd part non-strong named

I just want my part strong named--I don't care about their part.



5.Unmanaged Type Name and Strong Names

Why is the IDE not letting me compile with an instance of an unmanaged type 
library COM object?  It tells me that the type library needs a strong name?  
I did not think this was necessary for unmanaged type libraries...  How do I 
fix this, since I cannot modify the type library itself.

Andrew S. Giles

6. Strong naming assembly in an vb aspx project

7. VB6 to VB.NET & Strong Naming

8. Using a strong named vb6 DLL in ASP.NET

Return to VB.NET


Who is online

Users browsing this forum: No registered users and 52 guest