Visual Studio complains:
Warning 1 Unable to get MD5 checksum for the key file "RemoteCalendars2.pfx". Could not find file 'C:\temp\calendars\remotecalendars\NewTrunk\RemoteCalendars.Core\RemoteCalendars2.pfx'. RemoteCalendars.Core\RemoteCalendars2.pfx
Warning 2 Unable to get MD5 checksum for the key file "RemoteCalendars2.pfx". Could not find file 'C:\temp\calendars\remotecalendars\NewTrunk\RemoteCalendars.ICalGenerator\RemoteCalendars2.pfx'. RemoteCalendars.ICalGenerator\RemoteCalendars2.pfx
Warning 3 Unable to get MD5 checksum for the key file "RemoteCalendars2.pfx". Could not find file 'C:\temp\calendars\remotecalendars\NewTrunk\RC4IE\RemoteCalendars2.pfx'. RC4IE\RemoteCalendars2.pfx
Warning 4 Unable to get MD5 checksum for the key file "RemoteCalendars2.pfx". Could not find file 'C:\temp\calendars\remotecalendars\NewTrunk\TZ4Net\RemoteCalendars2.pfx'. TZ4Net\RemoteCalendars2.pfx
Logged In: YES
user_id=1114442
Originator: NO
Hi,
"it's not a bug": since in order to correctly load an add-in in Outlook you have to sign it with a key, I preferred not to add it in subversion (just imagine someone making malware using the same key :S...)
You need to create your own key.
Logged In: YES
user_id=87962
Originator: YES
Can you please document these gotchas (this one here and the VSTOOLS Second Edition) in a README perhaps?
For this one here, do you mind documenting the steps for such key generation? Thanks.
Logged In: YES
user_id=1114442
Originator: NO
Hi,
you're right, I'll add these instructions in the next release...here are all of the passages:
1)Right click any of the projects inside the solutionù
2)Choose Properties
3)Choose the tab Signing
4)Check Sign this assembly
5)In the combo box, choose New
6)For all the other projects, you have to do the same, except you have to choose of course Browse, and to select the key you created at passage 5.
Logged In: YES
user_id=1114442
Originator: NO
I've written you the instructions in the other bug tracker.
As I told you, I have written to the VSTO forum...but the answer that I received was just a "I don't know, I believe it won't harm" which I really disliked (a MVP in the VSTO forum telling me this means he has no clues at all, so he doesn't know if it'd be an harm or not!)