I would like to ask can I just put "msvsmon.exe" to target device and remote debugging like Win XP on Win CE?
msvsmon.exe is a desktop Windows executable. It will not run under Windows CE.
To remote debug to a Windows CE device - which is a very common task - use CoreCon to connect from Visual Studio. The process is outlined in this article.
Related
My system:
Server: Windows 10 Pro 1511 10586.36 Microsoft Visual Studio 2015 Community 14.0.24720.00 Update 1
Client: Windows 10 IoT Core (build 10586) Raspberry Pi 2.
My question:
I would like to profile C++ native application on Raspberry Pi 2.
But i was unable to find how exactly to do it.
Default profiling launch wizard works ok when using the application which is deployed locally but doesn't work for the case when application deployed remotely.
Here is the link Visual studio 2012 profiling remotely debugged process which is about VS 2012 actually, but it seems that even for 2015 problem is the same.
So is there a direct way to use VS remote profiling tool similar to the local one?
I have a maybe a small problem.
My task is to test a windows 8.1 tablet app. I have no tablet here, so I installed the Visual Studio 2013 Express and the Windows Phone SDK.
If I start the "windows phone application deployment" and try to start the *.appxbundle file, I get an error
a packaging error prevented this application from installing
I sent this back to the developer, he means the app is made for tablets and have to be tested on tablets.
So my question:
Is it somehow possible to simulate windows 8.1 tablet on a windows 8.1 system?
How to install the .appxbundle file?
Thanks.
If you want to test the app in a tablet then there is no need of a Windows Phone SDK or any simulator. You can install the app in your Windows 8.1 pc/desktop, and it will be the same as it will be on a tablet, because a windows store app is common for tablet and pc.
And to install the .appxbundle you can refer to this link (from step 6).
Found a solution, install the app with windows power shell
add-appxpackage C:\myapp.appx
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..
Our team currently has two business licences to Xamarin and one Mac book Pro, which is connected to the companies network.
If one of us opens the Hello World app within Visual Studio 2012 on Windows 7, we can connect, build, deploy to the Mac and see the iPhone simulator running the application.
However, if the second user attempts to do the same, they're unable to connect to the Build Host, as it's currently being used.
Is there a way to either manually disconnect the connection between PC 1 and Mac, so that PC 2 can connect, or can multiple PC's connect simultaneously with a additional build arguments?
Many Thanks
Dom
Xamarin 3.3 (stable) for Visual Studio now has a button for quick disconnect from a build host.
EDIT:
Xamarin 4.0
You can run one Mac virtual machine per Visual Studio instance using VMware Fusion on your Mac. I'm not sure of the legal implications, however.
To disconnect you can just go to the MAC and unpair in the "Xamarin.iOS Build Host" (same place you got the password required for pairing.
Then to connect from the second PC you can go (in VS) to:
Tools->Options->Xamarin-> iOS Settings-> Find Mac Build Host... follow the same steps as you did to connect the first PC.
I've already built windows ce 6.0 and run it in windows ce emulator.
but I want to run this without visual studio 2005.
I found emulator for windows ce 5.0, but I couldn't find emulator for windows ce 6.0.
somebody help me, thanks.
So you're saying you have created a CE image that does boot up in the Device Emulator? If that's the case, then you probably just need to install the stand-alone Device Emulator v3 bits (and your image) on the target PC.