Hi, thanks for the tip.
I'm following the article on how to give your .NET assembly a Strong
Name.
http://www.codeguru.com/columns/Expe...cle.php/c4643/
Specifically the procedure to use when obfuscating your assembly.
'Begin Snippet------------------------------
Practically, this means that you end up using the delay-signing
process when obfuscating an assembly with a strong name. The typical
usage pattern for a developer using obfuscation is:
a) Build the assembly with delay signing enabled.
b) Enable strong name verification skipping for the assembly (sn.exe
-Vr).
c) Debug and test the assembly.
d) Obfuscate the assembly.
e) Debug and test the obfuscated version.
f) Delay sign the assembly (sn.exe -R).
'End Snippet------------------------------
My Question is
1) How do you "embed" the PublicPrivateKeyFile.snk to the VB Solution?
What I mean is for example you will distribute your application, will
you distribute it with the PublicPrivateKeyFile.snk on the same
directory with your EXE application?
2) After creating the PublicPrivateKeyFile.snk using SN.exe, I copy &
pasted it to my Project's Solution directory & BIN directory,...
doing the follwoing would result to an error:
<Assembly: AssemblyKeyFile("PublicPrivateKeyFile.snk")>
but doing this corrected the error:
<Assembly: AssemblyKeyFile("E:\My Projects\Visual
Basic\vbVideoPatternGenerator\bin\PublicPrivateKey File.snk")>
I've been reading the Visual Studio .NET help, & it says there that
VB's IDE will automatically check for it under your project's Solution
directory. I wonder why it still renedered that error.
3)Step B on the Snippet above,..is the following correct to apply
verification skipping for my assembly?
sn.exe -Vr E:\My Projects\Visual
Basic\vbVideoPatternGenerator\bin\vbMyProject.exe
Is this the correct way? I'm in doubt a bit because the example was:
sn.exe -Vr YourAssembly.dll
But my assembly doesnt have a DLL.
4)Lastly, when accomplishing everything above. How can I check if I
have done the correct procedure? I mean is there a way to "test" & see
if the assembly is manipulated,...then the application *must not*
start.
Thanks, I appreciate if someone will help me out here in detail
because this is new to me.
Thanks,
Henry