|
Freshly installed laptop running Windows 8.1. Freshly installed VS 2017 - took 2 hours to download and install. Rebooted after installation completed. Crashes within seconds of opening it. tried 7-8 times. Rebooted and tried too. Same thing.
Tomorrow - uninstall 2017, install 2015 update 3 and go from there. 
|
|
|
|
|
I never thought VS 2007 would happen to me either  I'm still using 2015. I'm always wary of new releases of MS products.
Yes I'm a pedant.
|
|
|
|
|
Sorry - my bad 
|
|
|
|
|
Interesting. I am always amazed that people are having problems with VS setup. I have never faced it. I have never used web installers, I always close absolutely everything I was running when I install anything. First step after install is to restart (whether they tell me to do it or not).
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
lw@zi wrote: I am always amazed that people are having problems with VS setup. I have never faced it.
Translation: "Please hate me!"
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
No iso for vs 2017. They have an undocumented or blog-documented workaround that lets you run the web installer with a custom command line arg that's supposed to create an offline installation folder - tried it twice, did not work for me. It does not work for lots of people based on quick searching. So was forced to use this web installer. This is annoying if you want to re-install or install on more than one device.
|
|
|
|
|
Add my story to the collection...
Uninstalled vs15 - never really used it (seemed flaky on old projects),
vs13 I guess got sad at being left alone and stopped working too. (start, show start page, close)
Repair-installed vs13, no joy. Complete uninstall, reinstall, still no fun.
This weekends job: clean reinstall OS (w7), install vs13. ... Forget vs15, too broken and wont ever be fixed
actually not that upset, many years of dreck have built up in my box, was long 'bout time for proper scrub behind the ears.
...[re]installing is OK, it's getting all the prefs back that's the PITA ... woe betide any ms fanlemmings within earshot.
Finally, got the flu anyway, so I have a real excuse to avoid other humans anyway.
|
|
|
|
|
The install GODS smiled on me .. I planned for the worst after VS2015 installation woes that dragged on for 2 weeks.
Installed and up and running perfectly in less that 2 hrs but I still remember the pain.
Only bug I have noticed is the column/row count stops updating every now and again and you have to click on desktop and back again.
In vino veritas
|
|
|
|
|
Does VS2017 come with an .iso install package file (MSDN subscription or not)? I don't use web installers if I can help it.
|
|
|
|
|
There's an offline-install option (the link is on the download page), but...[^]
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
The offline install generator approach did not work - apparently lots of others had trouble too.
|
|
|
|
|
Well that sucks... 
|
|
|
|
|
I cannot imagine the reasoning behind not releasing an ISO. 
|
|
|
|
|
No iso for vs 2017. They have an undocumented or blog-documented workaround that lets you run the web installer with a custom command line arg that's supposed to create an offline installation folder - tried it twice, did not work for me. It does not work for lots of people based on quick searching. So was forced to use this web installer. This is annoying if you want to re-install or install on more than one device.
|
|
|
|
|
Nish Nishant wrote: Tomorrow - uninstall 2017
Two words: Virtual machines.
A rollback operation takes seconds, and you're pretty much guaranteed there's no leftover.
|
|
|
|
|
Good point and quite true - but this was my spare dev laptop.
|
|
|
|
|
Now that I installed VS2017, when I open a WPF project in VS2015 and open a view in the design I get
XDesProc.exe - This application could not be started.
This application requires one of the following versions of the .NET Framework:
.NETFramework, Version = v4.5
Do you want to install this .NET Framework version now?
Anyone else seeing this? Google doesn't return any relevant results. Any thoughts on how to fix this?
Clicking Yes to the dialog brings up IE when the fails to navigate.
[UPDATE]
So I downloaded and attempted to re-install the .Net 4.5 Framework, which failed with
"Same or higher version of .NET Framework 4.5 has already been installed on this computer."
I also tried going into the Control Panel and repairing all .Net Framework related installations.
At this point I'm dead in the water
Thanks Microsoft
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
modified 15-Mar-17 17:22pm.
|
|
|
|
|
I have only one WPF application and do not plan on updating it...Fortunately...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I have seen it in VS2017, when porting a solution built with 2012 to 2017. I never really used 2015. I solve it by setting the target framework to .NET 4.62
Get me coffee and no one gets hurt!
|
|
|
|
|
I see your problem.
Kevin Marois wrote: Now that I installed VS2017
....
If it's not broken, fix it until it is.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Perhaps we should start referring to it as Vista Studio?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
hehe they did it again you should have 4.6.1 and 4.6.2 online already.
Go to open a new project ... in the top midddle there what .net version is can you select 4.6.1 or 4.6.2 or something higher than 4.5?
If you can see that it's installed and from memory it's a default template issue and you have to run something on the command line to restore them. It will be on there help site under restoring default templates.
In vino veritas
|
|
|
|
|
Don't tell me that they've done the same as with winio, and declared .NET 4.5 as the final version -- with 83,000 major updates a year to add layers of incompatibility.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I've just tried a project that targets 4.0, and one that targets 4.6; the XAML designer works fine in both VS2015 and VS2017.
Is your project targeting .NET 3.5?
Kevin Marois wrote: At this point I'm dead in the water
Presumably the raw XAML view still works?
Or, if you really need the designer, Blend for VS2015?
Or VS2017?
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
