Skip to content

Bootstrapper also can’t install your application after rebooting…


Another problem with MSBuild bootstrappers that can screw all your installation…

If scheduling reboot after installing .NET or other prerequisites, bootstrapper copies itself to run from TEMP on boot. Why not staying where it is - who knows. And definitely, all the other MSIs are not copied, so it won’t find them. Reproduced for me.

Now give up and go write own bootstrapper. I’m setiously considering going for InnoSetup deployment.

For now, I’m trying a crazy ting, to copy MSI to TEMP for Setup.exe to find it after reincarnation… It’s the way to use given tools.

Please bookmark this post: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • del.icio.us
  • StumbleUpon
  • Live
  • Google
  • description
  • YahooMyWeb
  • Technorati

Post a comment — Trackback URI RSS 2.0 feed for these comments This entry (permalink) was posted on Friday, April 4, 2008, at 21:17 by Victor Sergienko. Filed in Main and tagged , , .

Post a Comment

Your email is never published nor shared.