5
Hey guys, I've tried and tried to find a walk thru that works. Since I am using VS C# 2008 express, i am using clickonce deployment. I am targeting the 2.0 framework as I am not using any 3.5 features.
Here is my issue and questions:
1) I have a c# program that I would like to publish to my website (it does NOT have front page extensions, nor do I plan to use them). Should I publish to a file path and then copy the files over to my website?
2) I am a bit confused about Signing the ClickOnce manifests and Signing the assembly. I can create a tempory .pfx file to use with both and hope that's good enough. Nonetheless, I am not signing the assembly (I don't see the point). However, it seems to force signing the ClickOnce manifest even if I uncheck it, after a publish it is checked and the manifest has the public key in it so I guess it does this by force? Not really sure what is going on here.
3) Obfuscate! I am using SharpObfuscator.exe from codeplex.com. Using Lutz Roeder's .NET reflector it appears that if I use SharpObfuscator.exe on a .exe in one of the Debug or Release directories of my c# application that it does indeed work. I can click on the obfuscated program and it works. However, I cannot figure out what I need to do to obfuscate the deployment package (you know when you publish the c# program). It seems to rebuild the exe files and thus I loose the obfuscation. What am I doing wrong. This is not a SharpObfuscator issue, it is my lack of understanding the process of using the VS IDE to build the program and publish it and understand where in that process I need to obfuscate the EXE.
I am not using any DLL files, all my code is going into one exe. I was up til 1:30am last night trying to figure these things out and it is frustrating. I have a nice program I would like to release to the public but I can't because of these road blocks. Thanks for you help guys!
