Compatibility issues
-
I just got this warning
What? Which? Where's tea?
Not a huge WTF, but the description strikes me as particularly ambiguous and uninformative.
-
-
-
But which one? 2011? 2012? 2013?..
No idea. It's not like it's right there in the name, that would be silly...
Seriously though, I don't get it.
-
Seriously though, I don't get it.
Compatibility issues with what? The OS? Another program? The wooden table?
-
There's nothing really wrong with that though. The compatibility issues could require a wall-o-text to explain, but you don't want that in a dialog, so it just says there's an issue, and if you want more help, there's an option to go get it.
-
Exactly correct. Also by keeping information about the compatibility issue online it can be easily updated (for example when a hotfix or update is created)
-
If that "get help online link" leads anywhere other than an "Oops! We can't seem to find the page you are looking for!" or a generic help homepage, I'd be impressed.
-
ALOT of work has been done to prevent that (bad links)...If the OP finds that it does, I would really appreciate knowing what the exact link behind the button is......
-
ALOT
-
This is a lame WTF.
-
-
This WTF has issues.
You can get help online and see more information about this WTF's issues.
-> Get help online
-> Post this WTF without getting help
-
Isn't it TRWTF that a Microsoft product should have compatibility issues ran on a Microsoft operating system?
-
a Microsoft product should have compatibility issues ran on a Microsoft operating system?
So IE 10 should run on Windows 95 just fine, right?
-
Microsoft gets bitched at if they special-case their own products. Remember the big bitch-fest over the "secret APIs"?
So the compatibility tool works the exact same on Visual Studio 2012 as it would on any 3rd party software.
-
So IE 10 should run on Windows 95 just fine, right?
Nope. But 1995 was 20 years ago and 2012 was 3 years ago. Based on the screenshot it's Windows 8. So VS2012 should run on Win8 just fine.
-
Nope. But 1995 was 20 years ago and 2012 was 3 years ago. Based on the screenshot it's Windows 8. So VS2012 should run on Win8 just fine.
And it does. Especially after you install Update32, which stops that message appearingOr Update 4, which is the latest one.
-
To sum up the thread thus far:
@Bulb is Doing It Wrong™.
-
Hm, I suppose I am. I ended up with that the installation refused to open some projects claiming they are not compatible though it's happily building them from command-line via msbuild many times a day (it's a build machine).
Still, I still think the message box could have said something more sensible like important update is available or something.
-
I ended up with that the installation refused to open some projects claiming they are not compatible though it's happily building them from command-line via msbuild many times a day
What project types? I can work with file extensions if you don't know for certain ;)
-
-
Still, I still think the message box could have said something more sensible like important update is available or something.
That's what the button to get more info online is for.
-
C++ projects. Three of tens failed to load.
They are however generated by CMake, so there could have been something that was confusing the properties parser while still being valid msbuild.
-
So IE 10 should run on Windows 95 just fine, right?
Given that Windows 10 is out soon, I want to run IE 95 on it.