I'm a having play with the Magic Mirror 2 using vs2017 to integrate onto my PI 3. As this is my first time with VS I can't seem to get debug to work when trying to run Magic Mirror UWP App.
These are the instructions and app I'm using GIT Hub Magic Mirror
Instructions followed:
In Visual Studio, go to Solution explorer, click on package.appxmanifest > Application and set http://webreflections.azurewebsites.net/create as the start page
On the ribbon, change the target architecture to match that of your PC (e.g. x64)
Set the debugging target to "Local machine" (changing the architecture in step 2 probably did this for you)
Click play to start the app running on your local machine
Follow the prompts on the create experience to save a profile for yourself
If anyone can explain why the program won't run (debug) I'll be extremely happy.
Thank you
Related
I had the free trial for the Visual Studio 2019 Enterprise version. Now that it has run out, I am trying to run my build from Unity using that .sln file in visual studio using the community version. I need to use the remote machine option because I am trying to deploy it to the HoloLens. I already tried rebuilding the unity project but I still had the same problem. Is it because when I created this Unity project I was using the enterprise version and now it can't translate the same way over to the community version? Does the community version not have the remote machine capability? I've attached a picture below of what I mean by "the start menu." Back in the enterprise version I would press that little down arrow to expand the Start menu and I would press "Remote Machine," but that option is no longer there when I try to run a .sln build from my Unity project.
Are you sure you have selected the correct project for the startup project? If you have a mistake in setting the startup project, there will only be a Start option under the menu. You can change the startup project from the Solution Explorer, right-click the desired project and choose Set as StartUp Project from the context-sensitive menu that is displayed.
If you still get this issue, can you see the Remote machine field under Project settings’ Debug tab: Configure the project for remote debugging
If yes, you just need to enter the network name or IP address in the Remote machine field, or select Find to search for the device in the Remote Connections dialog box.
If not, I believe you need to repair the VS installation.
I had the same problem. I put my machine in "developer mode" via the Settings and then opened my project in VS 2022. I'm now able to see the "Remote Machine" option.
Having completed my project in Visual Studio 2015 community edition, I "published" the project to a cd. I then copied the published directory to a Windows 10 Surface 3. In an elevated cmd prompt (as administrator), I then ran the setup.exe file created with the published project.
The application loads and runs without error. But, when the program is exited, it does not show up in the windows 10 start menu or application list. Furthermore, checking the installed programs shows that the just ran program is not installed.
What am I doing wrong?
I am the administrator on the Surface 3. (Should be noted, that the same visual studio 2015 program was used to create other applications that were successfully published and loaded on windows 10 machines that were not the Surface 3).
TIA for any suggestions on this.
Simple solution -- but took much exploring.
Go to the "Publish" tab on the project properties.
Under Install Mode and Settings.
Check √ The application is available offline as well (launchable from Start menu).
Publish with "Publish Now".
Now when the publish directory was copied to the Surface 3 and setup run, the application is correctly listed on the start menu. (I'm sure this is mentioned somewhere else on SO, but I couldn't find it).
I have created a Windows Store 8.1 app and I'm trying to deploy on the local machine. The project builds correctly, but it is not deployed. Visual Studio 2013 looks like it is working but on the Output window I see following lines, and the deployments gets stuck there:
1>Creating a new clean layout...
1>Copying files: Total <1 mb to layout...
1>Registering the application to run from layout...
It doesn't show any errors.
I have tried by rebuilding the project and restarting VS, but I'm still not able to deploy the project.
Any ideas?
Renew your developer's license, then restart the computer.
Steps
Open any Windows Store apps project and go to the "Project" menu.
Select Store > "Acquire Developer License..."
In the Window, click "I Agree" (after reading all of the terms, conditions, and privacy statement, right?)
Sign in with your developer account.
If everything works, your developer license should be renewed.
Restart your computer.
Windows 10, VS 2013, VS 2015:
1.) Restart your computer
2.) check that under settings/update&security/for developer/'Developer mode' is enabled
3.) open elevated powershell (as administrator)
4.) enter: Get-WindowsDeveloperLicense
5.) enter: shutdown /r /t 0 (this will reboot your computer) and wait
6.) start VS, create a new project, built and run on local machine
also you might want to take a look at this link at MSDN
I own a Surface RT and I was programming in Visual Studio 2013.
I found the tutorial online on how to set it up but I couldn't do it. Right by the part Visual Studio tries to find remote connections it doesn't find the surface. If I reboot the surface, right about when I open the remote debugger there is a small (10 seconds) period where it becomes available on my Visual Studio to select but it disappears right after never giving me the change to remote debug the app.
Does anyone had this problem before?
You can try adding the Surface's address manually.
Right-click your Windows 8 project, select Properties, go to Debug tab. Here select Target device: Remote Machine and then in Remote machin field enter the address and port your Surface shows you when you run the Remote Debugging Monitor (in the very first message you will see something like Msvsmon started a new server named 'SOMEADDRESS:PORT'. Waiting for new connections.). This usually helps when Visual Studio fails to find the device on it's own.
My VS2010 debugger has stopped functioning suddenly today on my Dell M4500. I had reinstalled VS2008 SP1 last week, but the 2010 debugger ran fine since then, so I'm not sure its the culprit.
I can launch a project once just fine, & afterwards I get a message that reads "Unable to start debugging," without any error # or explanation of why. Doing IISRESET doesn't help, I get the same message until I close VS with the entire solution and reload it. Here are some things I've tried:
Verified I have the latest project files
Repair option for VS2010
Complete uninstall/reinstall VS2010
Replaced Web.config with known good copy
Added localhost to the list of trusted sites in IE
Performed \aspnet_regiis -i in the 2.0 & 4.0 directories
Through IIS Services Mgr -> Default Website:
verified Enable HTTP Keep-alives checked
placed check in Integrated Windows authentication
Ensured Debug on "Any CPU" is selected
Tried building to Platform targets "Any CPU," "x86" & "x64"
Added DisableLoopbackCheck registry key entry in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Tested under both IIS & VS Development web server
Does anybody have any suggestions I can also try? Any help is very greatly appreciated!
Just a side note. I got a similar error in VS2013 trying to attach to chrome the error was:
Unable to attach the application 'chrome.exe' using XXX The 32 bit
version of the visual studio remote debugging monitor (msvsmon.exe)
cannot be used to debug 64 bit processes or 64-bit dumps. Please use
the 64-bit version instead
I had to untick "Silverlight" in the web project Web section:
I received this same message, preventing my web project from running and opening in a browser. Turns out another developer had made a change in the project properties to "Use Custom Web Server" which pointed to an external URL instead of to the web server on my machine.
Try this:
Right-click your project in Solution Explorer - click Properties - click Web tab - under Servers click "Use Visual Studio Development Server". For reference the usual port value here is "Auto-assign Port". Best of luck.
Here's why I got this error.
In Debug properties, verify that Start external program is not empty.
VS 2010 will warn you about it being empty, but will let you save it
I was trying to switch it from IE to Chrome, lost track of changes I was making, and spent an hour trying to figure out where this error was coming from.
I had the same issue but it worked when I switch Build => Platform target from x64 to x86.
Kindly turned off Debug Edit and Continue option
Turn on vs2010, run debug.
turn off debug, shut down all lunched webServers (i had few of them for different services)
Turn off VS2010
Turn on VS2010.
After that everything works perfect.