Next VS 2010 Rant
-
After 3 reboots and 3 1/2 hours of install - the installer popped up a message "Another setup is already in progress. Click retry to retry the setup or Cancel. Then restart the installer". WTF????? Retry did just that - retried the same message. So I cancelled and restarted. After ANOTHER hour it's fianlly installed and started. I'll give them this - it sure is pretty.
Everything makes sense in someone's mind
So, strictly speaking, this is a rant about MSIs.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
So, strictly speaking, this is a rant about MSIs.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
Not at all. I'v installed plenty of apps in the last 25 years that don't require 3 reboots and 5 1/2 hours to complete. I was also thinking that I have written countless apps and installed them and never once needed a reboot.
Everything makes sense in someone's mind
-
Not at all. I'v installed plenty of apps in the last 25 years that don't require 3 reboots and 5 1/2 hours to complete. I was also thinking that I have written countless apps and installed them and never once needed a reboot.
Everything makes sense in someone's mind
But, as you hadn't actually got to VS at this stage, it's still the MSI that sucks.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
But, as you hadn't actually got to VS at this stage, it's still the MSI that sucks.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
Your logic doesn't hold up. Many, many apps use MSI to install and don't require a reboot. Therefore it's the app being installed.
Everything makes sense in someone's mind
-
After 3 reboots and 3 1/2 hours of install - the installer popped up a message "Another setup is already in progress. Click retry to retry the setup or Cancel. Then restart the installer". WTF????? Retry did just that - retried the same message. So I cancelled and restarted. After ANOTHER hour it's fianlly installed and started. I'll give them this - it sure is pretty.
Everything makes sense in someone's mind
As I wrote this morning. No installation issues on my PC. Well, I'm a lucky man. :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles] -
Your logic doesn't hold up. Many, many apps use MSI to install and don't require a reboot. Therefore it's the app being installed.
Everything makes sense in someone's mind
-
Your logic doesn't hold up. Many, many apps use MSI to install and don't require a reboot. Therefore it's the app being installed.
Everything makes sense in someone's mind
Kevin Marois wrote:
many apps use MSI to install and don't require a reboot
True, but there are few apps as big as VS 2010. There isn't some guy on the VS team thinking, "Oh man, how can we fit more reboots into this setup process?" :) Rather, like most things in life, the answer is more complex:
- Visual Studio is a big app that installs services, .NET frameworks, environment variables, new language runtimes, for example, some of which must be installed and registered (restart) before other parts run (restart again).
- MSIs can't touch certain system files while Windows is running.
- Windows itself doesn't let you touch certain files while it's running, and thus provides options for touching said files during a reboot.
Thus, the problem of reboots is at least 3-fold:
- VS is a big app that touches Windows' private parts. ;)
- MSIs have to deal with this, and sometimes are overly zealous on the restart thing. (e.g. "We touched some system files. We're not sure, but to be safe, you should probably reboot.")
- Windows itself doesn't have any general hot-swapping mechanism, and thus must allow for reboots.
Now, that problem about "another installer is running" is different. I lay the blame on MSIs. (By the way, did you know an old CPian is a head honcho on the MSI team? It's true! :-O) Bottom line: to solve the reboot problem, Windows would have to provide some sort of atomic hot-swap of system files. If that were allowed, MSI could use it, and then the Visual Studio install wouldn't demand any reboots.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
Kevin Marois wrote:
many apps use MSI to install and don't require a reboot
True, but there are few apps as big as VS 2010. There isn't some guy on the VS team thinking, "Oh man, how can we fit more reboots into this setup process?" :) Rather, like most things in life, the answer is more complex:
- Visual Studio is a big app that installs services, .NET frameworks, environment variables, new language runtimes, for example, some of which must be installed and registered (restart) before other parts run (restart again).
- MSIs can't touch certain system files while Windows is running.
- Windows itself doesn't let you touch certain files while it's running, and thus provides options for touching said files during a reboot.
Thus, the problem of reboots is at least 3-fold:
- VS is a big app that touches Windows' private parts. ;)
- MSIs have to deal with this, and sometimes are overly zealous on the restart thing. (e.g. "We touched some system files. We're not sure, but to be safe, you should probably reboot.")
- Windows itself doesn't have any general hot-swapping mechanism, and thus must allow for reboots.
Now, that problem about "another installer is running" is different. I lay the blame on MSIs. (By the way, did you know an old CPian is a head honcho on the MSI team? It's true! :-O) Bottom line: to solve the reboot problem, Windows would have to provide some sort of atomic hot-swap of system files. If that were allowed, MSI could use it, and then the Visual Studio install wouldn't demand any reboots.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
"VS is a big app that touches Windows' private parts.".... well - I hope it bought it flowers and wined and dined it first .....
Judging by the disk activity, I think it gave Windows a good thrashing. :)
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
Kevin Marois wrote:
many apps use MSI to install and don't require a reboot
True, but there are few apps as big as VS 2010. There isn't some guy on the VS team thinking, "Oh man, how can we fit more reboots into this setup process?" :) Rather, like most things in life, the answer is more complex:
- Visual Studio is a big app that installs services, .NET frameworks, environment variables, new language runtimes, for example, some of which must be installed and registered (restart) before other parts run (restart again).
- MSIs can't touch certain system files while Windows is running.
- Windows itself doesn't let you touch certain files while it's running, and thus provides options for touching said files during a reboot.
Thus, the problem of reboots is at least 3-fold:
- VS is a big app that touches Windows' private parts. ;)
- MSIs have to deal with this, and sometimes are overly zealous on the restart thing. (e.g. "We touched some system files. We're not sure, but to be safe, you should probably reboot.")
- Windows itself doesn't have any general hot-swapping mechanism, and thus must allow for reboots.
Now, that problem about "another installer is running" is different. I lay the blame on MSIs. (By the way, did you know an old CPian is a head honcho on the MSI team? It's true! :-O) Bottom line: to solve the reboot problem, Windows would have to provide some sort of atomic hot-swap of system files. If that were allowed, MSI could use it, and then the Visual Studio install wouldn't demand any reboots.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoJudah Himango wrote:
atomic hot-swap
But the radiation would be way too high... :-D :-\
WE ARE DYSLEXIC OF BORG. Refutance is systile. Your a$$ will be laminated. There are 10 kinds of people in the world: People who know binary and people who don't.
-
After 3 reboots and 3 1/2 hours of install - the installer popped up a message "Another setup is already in progress. Click retry to retry the setup or Cancel. Then restart the installer". WTF????? Retry did just that - retried the same message. So I cancelled and restarted. After ANOTHER hour it's fianlly installed and started. I'll give them this - it sure is pretty.
Everything makes sense in someone's mind
Unlucky you. VS 2010 Professional (at home) 23 min. to install with no reboots. VS 2010 Premium (at work) 25 min. to install with 1 reboot.