|
|
Granted, that's the only client doing this 
This space for rent
|
|
|
|
|
My company (our shop) is going to start testing Windows 10 in about 6 months. I actually want Windows 10 to work, because I make my living with the Microsoft stack and a "new" stable OS, would be nice.
|
|
|
|
|
They are not getting Windows 10 on as many machines as they had hoped, especially the business market. For instance, our shop has no intention of going to Windows 10, anytime soon. So, "Biblical" proportions, is not out of the question, anymore.
Not enough people want\use Windows 10, for it to be a viable OS in today's market. Many people are waiting a year or two, for the bugs to get ironed out. Question is, does Microsoft have the time to wait that long.
|
|
|
|
|
I don't see why not. Historically they have shown that they're very patient - and they have deep pockets. Even with longer replacement cycles, existing 7/8 machines won't last forever. . .
My long term goal is to live forever. So far, so good...
|
|
|
|
|
Frank Alviani wrote: I don't see why not. Historically they have shown that they're very patient
and that is why they are forcing installs now, because they are so patient. 
Trust me when I tell you, that they are very concerned about all of this.
|
|
|
|
|
Slacker007 wrote: if Windows 10 does not cut the mustard for any reason, then Microsoft will have to re-evaluate their future product line and strategy.
When would that never have been the case, in all of Microsoft's history?
|
|
|
|
|
When has anyone NOT wanted to update to the latest OS? For me and our company (and other companies) it is now, with Windows 10. Only time in MS history, that I can think of.
|
|
|
|
|
Slacker007 wrote: Only time in MS history, that I can think of.
Really? What about Vista? And 8? 
|
|
|
|
|
Point taken with Vista. But 8 is doable. I currently use 8 at work, and it is manageable. It's no 7, though. 
|
|
|
|
|
Slacker007 wrote: But 8 is doable. I currently use 8 at work, and it is manageable
Agreed. Not all that, but when you get used to it it's just a small step back from 7.
|
|
|
|
|
Slacker007 wrote: Microsoft will have to re-evaluate their future product line and strategy
Here's a strategy: write software that actually works!
|
|
|
|
|
Did you notice how often I rant about WinX?
That's because I'm not using it
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Neither do I
|
|
|
|
|
Use the Update for Microsoft Visual Studio 2015 (KB3110221)[^], Sander.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
If anything, that made it worse.
I now get a "Visual Studio is busy" error every time I start VS and the Test Explorer is still open... 
|
|
|
|
|
I must be lucky then, as I have had no issues whatsoever.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Sander Rossel wrote: If that doesn't work I'm going to look for an older installer without Update 1.
Good luck. I opened a project on my older laptop that has some unit tests, (BTW, this is VS2012) and got a "that file already exists" when I tried to create a new test file. No, it doesn't exist. Same problem with a non-test project. Tried a solution without tests, that worked fine. I figure, WTF, VS2012 is corrupted, I'll just install VS2015.
Nope, installer dies with some error that apparently other people have experienced. Figure, ok, I'll just uninstall VS2012 and re-install it. Nope, same error as when I tried VS2015.
Read a comment somewhere to try the web installer. Well, right now the laptop (and for the whole day so far) has been doing W7 updates. Figure I should try that first. My last update was in 2014, so there are some 157 updates.
I think what I'll do some time this week is dump everything onto an external SSD, then wipe the drive and start from a blank slate (W7, none of this W8 or W10 sh*t for me.) Maybe replace the drive with an SSD while I'm at it and breath a little life into this old, but very reliable, laptop. At least, the hardware is great, it's showing its age with the OS though.
Or maybe I'll turn it into a Debian box and use Mono.
BTW, the missing cat turns out to be living under our house. Now if it would just stop snowing and raining, he might come out for a bite and be caught in the have-a-heart trap we set out. (And this is a test to see if you read the whole post, mwahaha.)
Marc
|
|
|
|
|
Marc Clifton wrote: the missing cat turns out to be living under our house
That's great news! 
Marc Clifton wrote: And this is a test to see if you read the whole post, mwahaha.
I always start at the bottom, I haven't read further than your cat 
Seriously though, Windows after 7 is a PITA, VS is a PITA... Maybe switch to Linux after all
|
|
|
|
|
I too have lot of issues with VS 2015. In C#, right click a variable to rename, got 'Object reference not set to instance exception'. And a lot more issues with the editor.
modified 2-Aug-18 21:02pm.
|
|
|
|
|
Yes, I've seen that one too!
|
|
|
|
|
I have got a similar problem in my Visual Studio 2015 Community!!!
It happens in the solution where I have got many projects, about 20. Precisely, I have got there 20 ASP.NET Core 1.0 projects. It is crashing when I simply just open my solution. I can see that it loads projects in random order and crashes.
When it crashed I tried to debug it in another Visual Studio 2015 instance but with no result, I think I saw there only something related with json but don't know if it was related with json files in my solutions or projects or internal Visual Studio itself.
The way around (worked for me):
Note: Really be careful if you are using GIT. If you move the projects around you should commit only when your projects are where they are meant to be.
1) Close your Visual Studio 2015
2) Create a temp folder inside your solution, on the same level where your projects are
3) Move majority projects there - maybe all except one, especially keep the one where is the solution file.
4) Open your Solution
5) This should open Visual Studio 2015 without crashing and you will see in your Solution Explorer obviously that some projects are unavailable
6) Move the projects back from temp folder back to their previous place
7) You can reload (right click the project) the one you need or all of them. It should not crash.
I personally like Visual Studio 2015 very much and hope that eventually whatever is broken will be fixed and don't have to use this retarded work around..
..yep, it started with Update 1, I think the Update 73 should fix it.
modified 16-Feb-16 5:21am.
|
|
|
|
|
Nope, fixed it by uninstalling Update 1
|
|
|
|
|
At least you got it to install!
Mine just hanged at the install phase, and completely buggered up all my other OS settings. I ended up having to re-install the entire OS after facing system slowdown, repeated crashes etc.
'The time has come,' the Walrus said,
'To talk of many things:
Of shoes -- and ships -- and sealing wax --
Of cabbages -- and kings --
And why the sea is boiling hot --
And whether pigs have wings.'
-- The Walrus and the Carpenter (by Lewis Carroll)
|
|
|
|
|
I had basically the exact same problem. Even uninstalling and reinstalling with the Update didn't work. I had to uninstall everything then reinstall everything without the update, once I got that up an running I installed the update, then I had a build problem after the update that I did not have before. The build problem turned out to be an import to a non existent static class in VB, for some reason the compiler didn't say that, it just crashed. I discovered it through eliminating everything until I could build then going line by line through that code file. Update 1 is a MESS.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
