Whenever I try to run Visual Studio 2012 Ultimate on Windows 8 Professional x64 bit I receive the following dialog:
This program has compatibility issues:
Any idea why should there be any compatibility issues for the product which was released for Windows 8?
It is a problem already signaled by other users, seems that installing the Update2/Update3 will resolve the problem.
You could trigger the install of the Update going to the menu Tools, selecting Extensions and Updates and then checking for Updates. Beware, before to start be sure to have plenty of time. It is a long process and is not very fast
Related
I developed a project in nodejs on Visual Studio 2013 full edition with Nodejs plugin of Codeplex (http://nodejstools.codeplex.com/).
It always worked fine till, one week ago, when I decided to upgrade (as suggested) the Nodejs pluging. Now Visual Studio crash every time I open a project in nodejs and print me this alert:
No problem with other type of projects.
My PC has a quad core i7 CPU, 16GB ram and the SO is Windows 8.1.
I solved this.
Node.js tools plugin on VIsual Studio suggested me to update it to the lastest beta version.
I innocently accepted and then started my problem.
I has been necessary to remove the plugin and install the suggested one from http://nodejstools.codeplex.com/ to solve the problem.
You cannot uninstall it from the extension view of VS (tools->Extensions and updates) 'cause it a SO application, therefore it must be removed from Control Panel->uninstall programs.
It seems only the VS 2013 Remote tools for ARM works on Windows 8.1.
Does this mean that Visual Studio 2012 is obsolete now for WinRT development?
Update on 25 Nov 2013:
Just saw Moche's answer and was about to post the update. Yes VSE2012 on Win8.0 can now remote debug on Surface2 / Win8.1 using VS2012 Update 4 which was released over the weekend.
Also it is required to download the Remote Tools for Arm that are part of the Update 4:
http://www.microsoft.com/en-au/download/details.aspx?id=39305
Click the 'details drill down' to get the 'Remote Tools' Download
To get remote debugging running, you need to right-click on the project file in Solution Explorer and select debugging under the Configuration tab - then you will notice a field with 'machine name'... complete the machine name of the Surface 2 and select Authentication 'Yes' - Ensure both the Visual Studio Computer and Surface 2 are on the Same Workgroup in Control Panel, System, Advanced System Settings, Computer Name Tab. These brief instruction assume you will be using Windows Private lan authentication. If you want to use your live account for authentication simply google how to Remote Debug Visual Studio 2012 with Windows Live Authentication..
When you run the remote tools installation for the first time on the Surface 2 tablet, you will be prompted by a wizard which sets up the necessary exceptions for the Windows firewall on the tablet.
Actually I succeeded to do the debugging on 8.1 using VS2012. I've installed the latest update 4 of the Debugging Tools. Then I went in Windows Explorer to Program Files->MS Visual Studio 11->Common 7->IDE->Remote Debugger>arm and ran msvsmon from there. That's it - I was able to connect to it from my Windows 8 machine running VS 2012.
Yes, it's indeed obsolete.
For windows 8.1 RT development, set up a separate 8.1 machine with VS 2013.
Update
As of Visual Studio 2012 Update 4, remote debugging to 8.1 seems to be available.
The Answer above that 'Its obsolete' pertaining to VS 2012 and debugging on Win 8.1 is (entirely) not correct - the correct phrase would be that Debugging on Win 8.1 client from a Visual Studio 2012 machine is not supported at time of Win 8.1 preview - Hopefully VS 2012 update will soon allow it to connect to Visual Studio 2013 remote debugger tools to allow Windows 8 development to continue between Windows 8 and Windows 8.1..
As Per:
http://weblogs.asp.net/lduveau/archive/2013/07/10/visual-studio-2012-2013-and-windows-8-1-apps-clarifications.aspx
Quoting:
Visual Studio 2012 (running on either Windows 8 or Windows 8.1) continues to support creating and working with Windows Store apps for Windows 8. It does not support creating or working with Windows Store apps for Windows 8.1. Apps targeting Windows 8 continue to work on Windows 8.1, they just can’t take advantage of all of the new Windows 8.1 functionality and performance improvements.
When I read the Answer above I got my knickers in a real twist and then I thankfully found this (and now have hope my shiny Surface 2 isn't a desk weight for developing) -->
quoting off:
http://social.msdn.microsoft.com/Forums/en-US/3e5bd281-4dde-418b-a9fe-078815523fe1/win-81-surface-remote-debugger
For debugging applications on Windows 8.1 Preview RT devices you need to use VS2013 Professional, Premium, or Ultimate Preview with the Remote Tools for VS2013 Preview.
We are aware that VS2012 is not compatible with Windows 8.1 Preview, and we are working to address this with the next update to VS2012.
Thanks,
Dave Lubash
Visual Studio Team
#Carl L - After further digging.. It seems both our answers are sort of right.. To support Win 8.1 currently, you need Win 8.1 and Visual Studio 2013 installed - I tried Installing Visual Studio 2013 Express on my Windows 8 PC and NO DICE..
I guess the only clarification I am adding is that developers can continue using Windows 8 with Visual Studio 2012 to create apps that run on Windows 8 (only) and will also be available in the Apps Store and run compatibly on Windows 8.1 (but not use all the latest 8.1 optimized features). I am only taking this based on MS forum posts.. The information from Microsoft doesn't properly address this point in its documentation at:
http://www.microsoft.com/visualstudio/eng/products/compatibility-2013
Its also worth pointing out that Visual Studio 2013 Express (free version) is not able to produce Windows 8 Apps - ONLY Windows 8.1 apps (so that part of your answer is correct currently). So in a sense it is unsafe to say Visual Studio 2012 is obsolete as it is currently required to support creation of Windows 8.0 apps.. Unless you don't mind ditching App updates for your existing user-base who may not have yet made the jump to 8.1 (not a sound development model and I am very surprised MS is making fragmentation on its own new platforms for developers currently).
At the moment I am a bit miffed that I am forced to upgrade to Windows 8.1 and VS 2013 in order to debug on my Surface 2 (RT) tablet and in that case would not be able to debug Windows 8.0 apps on my Surface 2 (RT) using VS 2012 until MS hopefully updates VS 2012 and/or the VS 2012 remote debugger tools.
Hope that clarifies a bit - seems you were mostly right which is a real shame if Microsoft is serious about attracting developers to its newest OS and having its free development tools rival that of Android OS and iOS..
It appears that it's no longer possible to debug using VS2012 tools on a Surface RT running 8.1 (see Debugging Surface RT 8.1 from Visual Studio 2012).
So, how can I uninstall it, because it still has icons on the start menu, and items under program files. The digital signature is no longer recognized, so it's not possible to uninstall via the control panel.
Just remove the program files folder of Visual Studio 11.
Then go to your registry keys in HKLM => Software => Microsoft and remove the Remote Debugger entry.
Now you can do a fresh install of the VS2013 remote debugger tools and next time you'll restart the old icon seems to be removed from the all apps screen.
Good luck :)
Yeah good luck with that, we will all need it... As is mentioned in a few places on the web, Win 8.1 and Visual Studio 2013 can develop apps ONLY for Windows 8.1, while Windows 8.0 and Visual Studio 2012 can develop apps ONLY for Windows 8.0... You can install both side-by-side on the same machine (VS 2012 and VS 2013) though.
But what really gets me is that my new surface 2 is now a paperweight because I can no longer debug on it as I don't wish to abandon Windows 8.0 development ATM. I hope Microsoft addresses this as it could become a serious fragmentation issue and keep developers away in droves.
How can I find What Update version I have in Visual Studio 2012? (update 1 or 2 or 3). HOw can I go back to update 1 so that I can build .dll which can be supported in windows XP? I am sorry It's not a programming question but highly appreciated for your answer. I'm stuck!
I have a following Error: Unable to load DLL 'xxx.dll': The specified procedure could not be found. (Exception from HRESULT: 0x8007007F)
My Target OS is windows XP: 32 bit .NET 4.0.
Also Same dll works for windows 7 and other so I think there shouldn't be dependency problem.
Help -> About will tell you what update you are running.
As far as I can tell, targeting windows XP is supported from VS 2012 with any update. You just need to make sure the project targets a version of the .NET framework that is supported on Windows XP. (.NET 4 or earlier)
How can I find What Update version I have in Visual Studio 2012?
Open Visual Studio, Click Help, Click About. See Second line.
Mine says "Version 11.0.60315.01 Update 2"
How can I go back to update 1?
(assuming Windows 7)
Control panel > Programs and Features > view installed updates > uninstall the update you want under the Visual Studio 2012 category.
That being said, I have no idea if this solution is actually something you need to do or will fix your problem. It is simply about how to remove the updates. It sounds like you may just need to download the latest .NET framework for XP.
I'm running Visual Studio Express 2012 on Windows 7. I've been running it with no problems for several months now.
Last Friday, when I shut down my PC, a lot of Windows updates were installed. This morning, when I started up and opened a VS2012 solution, I got this error message:
This program has known compatibility issues
...
Visual Studio 2012 Express for Windows Desktop is incompatible with this version of Windows.
There's a button for Run Program, and when I click it, the solution opens normally. I haven't changed anything about my Windows configuration. This happens every time I open a solution. Did MS release a flawed patch in the batch of updates that got applied last Friday?
EDIT: I'm not sure why people are voting to close this question. The answer that's been linked to isn't related to my issue; that answer seems to pertain to trying to open a VS2012 project in VS2010. I'm trying to open a VS2012 project in VS2012. If you really think that the question needs to be closed, please let me know why in the comments, so that I can change it appropriately.
The .NET updates installed on Friday were:
KB2805226
KB2805221
KB2804582
UPDATE: I gave up, more or less, and clicked the "Don't show this window again" checkbox on the error window. Visual Studio seems to be running ok.
I received the same message on Visual Studio 2012 Premium (on PC where Windows 7 re-installed in last month) - the suggested fix was "Update for Microsoft Visual Studio 2012 (KB2781514)" which seems to have fixed it
www.microsoft.com/en-us/download/details.aspx?id=36020
Install Visual Studio 2012 Update 2 solved my problem. No previous update needed for this one. Here's the descriptions of the update.
(I'm using Windows 8, installed all important updates for Windows, then tried repair Visual Studio in Programs and Features, problem still here until installed Update 2.)
I've been running VS2012 for about 2 weeks now since I clicked the "Don't show this window again" button. I haven't encountered any problems. For now I'm going to consider this an adequate solution.
I've just installed VS2012 at home and came across the same problem. The 1st solution I found is that webdeploy doesn't work after Oct 2013 and I should install Web deploy V3.0.
Done that, no joy. I let Win7 search for compatibility solution on-line and it found an update patch (KB2781514) which did work.
This is the same solution as mentioned before by #John M.
Should've looked here first, just posting this again if someone comes across this again these days..
Thanks to all other users who helped with this thread.
I had a similar problem with VS2012 awhile ago it was along the lines of:
"this solution has no errors and could potentially be damaged"
*yet still opened fine.
as far as fixing it went I performed a clean install of VS2012 and the error has not bugged me since in saying that I am probably out of date at this time and may find if I updated I would have the same issue.
Food for thought.
Even i had the same problem on Windows 7 with Visual studio 2012.
Installed Update for Microsoft Visual Studio 2012 -KB2781514 and it fixed the issue.
Note: "Just clicking on Run program was also opening up the solution file without any issues in my case."