haha, ok thats shedding a good light on it
!
I can forgive for having to reset the default page everytime (i should have
just named it default.aspx and avoid the whole problem...)
BUT, what about the other complaint?
Look what happened to me today.
We have test & production both on the same machine -- what can i say, we're
low on servers.
Anyhow, I ran the msi to put something into test. I use the same msi for
test & production, and during the install I just point it to test/ or
prod/.
Windows gives me the error "you must go to add - remove programs..." and
uninstall the existing msi. (This is retarted to begin with. I just want
to run a setup routine, why is it in add-remove programs to begin with?!)
So I uninstalled the .msi. Then I get a phone call by angry users that
production is down!
Turns out when you uninstall the msi setup routine, it pulls down whatever
the last thing it installed as well!
I wish the web setup project just have me a way to run a setup.exe, without
putting the install routine in add-remove programs etc, and just let me
install where I want without these headaches
Jason Shohet