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.
Related
I am trying to install Microsoft Azure SDK. I downloaded this version (2.9) of the SDK from here. And I am getting the following error in the picture.
I have Visual Studio 2013 and 2015 installed on my PC. Could it be some sort of compatibility issue. I read on some forum that it won't work if I have different versions of the Azure SDK installed on Visual Studio 2013 and 2015.
But I don't have the SDK installed on any of them. And I can't seem to find any Web Development Feature in the IDE either. Does anyone know how to resolve this?
Given the situation, the issue is most probably that the relevant modules for Web Development weren't installed when Visual Studio was installed. Those modules are not selected to be installed by default.
The solution is to simply re-run the setup and select "Modify".
On the list of modules, go to "Windows and Web Development".
You should get Microsoft Web Developer Tools in the list. Just select that and install. That should do the trick.
#alchemist is right but I had deleted the VS2015 installer long ago (right after installing). So I went to the Control Panel > Programs And Features > Microsoft Visual Studio 2015 Community with Updates > (right-click) > Change
This will bring up the visual studio installer. Click on Modify > Check Microsoft Web Developer Tools > Update.
*walks towards the camera in slow motion on an exploding background
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..
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
We developed an application in visual studio 2010 and reports are working fine, when we choose to open the same application through visual studio 2012 Ultimate, reports are not working and when i open .rpt file showing binary format ad also I could not find Crystalreport.rpt in Reporting template in visual studio 2012. After googling it, I have installed
CRforVS_redist_install_32bit_13_0_5 , but doesn't work.
How can i change or edit .rpt file design using visual studio 2012 and want to change the .rpt database name too. Any suggestion or idea to achieve this?
I had the same problem after installing visual studio 2012 and found no answer on the forums. I uninstalled CR yesterday and downloaded again the CRForVS 13.0.5 from here just in case there was a bug in the previous version I downloaded in may and installed it. Then I installed update 3 for Visual studio and everything works fine now.
Cheers
Michael
I figure this one out for me.
From SAP Crystal Reports's download site:
Please note: To integrate "SAP Crystal Reports, developer version for Microsoft > Visual Studio" you must run the Install Executable. Running the MSI will not ? >fully integrate Crystal Reports into VS. MSI files by definition are for runtime >distribution only.
By default Windows 10 does not install the 3.5 framework, CR for VS still needs >it. Select it by "Turn Windows feature on or off" and choose both options.
I downloaded the exe, instead of the MSI packages, and it worked for me finally. Helps to read I guess.
I have just installed Visual Studio 2012 RC that come with Blend standalone version. When I start a new project the list is empty, there are no templates to choose from.
Do you have any idea how to solve the problem?
With the upcoming update of visuals studio (update 2) support for Silverlight and WPF will return. I think this will work on Windows 7 too. You won't be able to build Windows Store apps though.
You can install the CTP of the update if you like.
If you don't want to update visual studio yet, you can install the Blend + SketchFlow Preview for Microsoft Visual Studio 2012
What version of Windows 8 are you running? The most recently released version of Blend with VS2012 must be installed on Windows 8 Release Preview, http://windows.microsoft.com/en-US/windows-8/release-preview.
This release of Blend targets Metro style app development on Windows 8.
~Lori
Visual studio 2012 update 2 introduce a new version of Blend, witch is working correctly (including new project creation) for silverlight 4, silverlight 5, windows 8 app and so on.
Microsoft Answer Looks like it isn't available for win7 but have to update to win8 "Unfortunately Blend is empty on Win7, no matter which version you installed. It will work when you upgrade OS to win8. Or you can use visual studio directly."
Same issue, with the visual studio 2012 pro installed with the web-installer available on the MS website.
As i understand, blend for visual studio 2012 can be used only under windows 8 ?!
So why is it possible to install it under a windws 7 o_0
Feel really strange that we can't anymore edit silverlight 5 xaml under blend anymore except under windows 8...
I have Win7 + VS 2012 Ultimate SP3 + Blend installed and the following is a very good way to work around this issue:
Do not try to open Blend seperately or open new projects in Blend
Instead insert your new XAML based user control in a VS 2012 project or solution (...where they will end up anyway...)
Select the XAML file in the project explorer in VS 2012
Go to the VS 2012 menu => View => "Open in Blend..."
TADA: The XAML based control is opened in Blend and you can just normally work on it
By the way: I have another machine, without any VS 2012 service packs installed. On that machine opening and working with blend is no problem. It seems to be a VS 2012 service pack related problem.
Happy Coding!