Disclaimer: All postings are provided "AS IS" with no warranties, and confer no rights. This weblog does not represent the thoughts, intentions, plans or strategies of Microsoft. Because a weblog is intended to provide a semi-permanent point-in-time snapshot, you should not consider out of date posts to reflect current thoughts and opinions.
Reading this article http://www.nytimes.com/2010/12/05/us/05bully.html?_r=1&hp
It’s clear that ensuring you “grab” your online “address” (Facebook page) and establish it as authoritative, before some other clown does is important.
Once you have your kids (yourself) online, then you monitor. Best you take the slot before somebody else does…
I was taking the Windows Azure CmdLets project and getting it into an MSI just to make it easier to deploy in a nice package. I ran into problems with the Setup project not being able to properly establish the right registry settings for an x64 environment.
Even though you set the target platform on the Setup project to x64 the InstallUtil.lib that get’s run is still x86. In order to have it work property, you need to follow the steps identified here:
The section “64-bit managed custom actions throw a System.BadImageFormatException exception” covers the steps you need to follow, using the Orca MSI editor to replace the InstallUtilLib.dll from the one that the Setup Project embeds (x86) to a x64 version.
Now, works like a charm…
Resultant installer here:
The CmdLets are the same ones from the Training Kit – November 2010 release.