bri189a Posted October 19, 2005 Posted October 19, 2005 In Version 2.0 you don't seem to have these any more? What's up with that? In another post I complained about having to strongly name something to use it (because XCOPY isn't good enough for WebPartManager); now I can't strongly name it because I can't find a dll or assembly for it? ***???? Quote
bri189a Posted October 19, 2005 Author Posted October 19, 2005 Okay, I figured out how to 'publish' or change the build - but signing the assembly...well now how do I create a key to do that? The instuctions in 'help' saying there's a 'Signing' pane...yeah...where'd they hide that cause I opened every window (I think) and couldn't see that one. Quote
Administrators PlausiblyDamp Posted October 20, 2005 Administrators Posted October 20, 2005 You only get the full signing pane on certain project types - not on ASP.Net ones. You should still be able to create a keyfile with the sn.exe command line utility though. Once you have generated a key you can set a path to it on the MSBuild Options property page of your project. Quote Posting Guidelines FAQ Post Formatting Intellectuals solve problems; geniuses prevent them. -- Albert Einstein
bri189a Posted October 20, 2005 Author Posted October 20, 2005 Yeah...the sn.exe. command line utility...um...that syntax is so long and the 'help' is so obscure that it's not much good to me...I'm searching code project for a good example or anywhere else I can find and haven't found a good tutorial/example yet...do you have any PD or know of some? Trying to avoid that utility is what got me to posting a look for the 'Signing' pane. Quote
Administrators PlausiblyDamp Posted October 20, 2005 Administrators Posted October 20, 2005 Most basic use is simply sn -k to generate a keyfile. Other possibilities are -p and -R when it comes to delay signing a dll. Quote Posting Guidelines FAQ Post Formatting Intellectuals solve problems; geniuses prevent them. -- Albert Einstein
bri189a Posted October 20, 2005 Author Posted October 20, 2005 That is simple; guess I was reading too much into the other parameters. Thanks! Quote
bri189a Posted October 25, 2005 Author Posted October 25, 2005 Okay, PD, signed my first assembly - that was fun. Got it in the 'Configured Assemblies' - fun also. How to I get it to appear under .NET resources though when adding references? What kind of install package do I create for co-workers so that they can do the same? Would they still be able to use the dll now that it's signed if they just XCOPY'd the dll into a new project of theirs? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.