>Yeah, at first I found that to be a pain in the neck too. There are several reasons that MS did this, one of which is that with the Transaction Installer Technology it would make doing a rollback rather impossible with a post executable.
>Initially it ticked me off so bad that I DID find a way to manualy edit the .msi file and get it to run a post .exe program by writing a script.
>However, after some thought, I decided against it in the long run. I simply changed my application to detect a 'first run' and blah...blah...you get the deal.
>The dumbest thing about it is that there is no way to modify the 'start in' directory for shortcuts that are created. It is simple to work around that as well, there is a program called 'Orca' that comes on the Platform SDK CD that lets you modify the .msi table - it's like a 2 second change, but still quite anoying that you actually have to do it. Sooner or later I'm sure one of my apps will go out with me forgeting to do that.
>
>

Windows/Visual Studio installer is new. My guess is this is one of those "OOPS, we forgot something" scenarios that will be fixed in an upcoming release.