1. 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? Thanks David
2. Problem with signing assemblies using AL.exe (Strong name signing an unsigned assembly) - CSharp/C#
3. Strong Naming a Non-Strong Named assembly
Hi, 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. Regards Joyjit "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-named assembly calling unsigned assembly: FileNotFound exception - CSharp/C#
5. Restricting access to Assembly.LoadFrom call within an assembly based on strong names
Surya,
You aren't going to be able to do this. You are going to have to
implement a load mechanism yourself and then have all of your code go
through that mechanism.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- XXXX@XXXXX.COM
"surya" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...
> Hi,
>
> I use the Assembly.LoadFrom call in my code to load assemblies
dynamically.
> This call currently loads both signed and unsigned assemblies.
> It now needs to be changed to load only signed assemblies. Again only
those
> signed assemblies with known public keys need to be loaded.
> Is there an easy way to implement this?
>
> Regards
> Surya
>
>
>
7. hexedit assembly - snk, strong name, sing assembly question
Hello
How can I ensure that a assembly (dll) is not manipulated (e.g.
hexeditor).
I thought that sign the assembly (snk-File), this ensures.
I have tried the following.
1.
Create assembly Test.Dll with AssemblyVersionAttribute("1.1.*") and
sign with Test.snk (Property-Page and/or
AssemblyKeyFileAttribute(@"Test.snk")
2.
Create UseTest.Exe with reference to Test.Dll.
--> Now UseTest.Exe requires the desired Test.Dll, ok
However, I can manipulate Test.dll (Hexeditor) an use it !! e.g.
Class Test1 in Test.Dll
public class Test1
{
public static void SayHallo()
{
System.Windows.Forms.MessageBox.Show("Hallo Peter");
}
}
Change text Hallo Peter with hexeditor to Hallo Qeter
Do I something wrong ?
or is signing not at all thought my problem ?
Is there built in mechanism to "checksum" a assembly
thank you
Peter
8. hexedit assembly - snk, strong name, sing assembly question - CSharp/C#