I am trying to run the sample Microsoft Media Platform plugins on the xbox (MMPPF.Addons).
I am able to compile the project in visual studion 2010 and deploy it to the xbox (I have a xbox debug box that supports lakeview platform.). I am able to run the application by double clicking "default.xex" in "Xbox neighborhood" or clicking "start without debugging" in visual studio.
However, I am unable to debug it by clicking "start with debugging". I got an error message saying "Unable to start program 'devkit:\MMPPF.Addons.Xbox\Debug\default.xex'".
I have installed the following software.
visual studio sp1
xdk 20871.1
adk
flash 14448.0
silverLight 4
I also have the xbox connected to both the internet and my computer.
Could anyone tell me what is missing?
Finally figured out why. There seems to be something wrong with the debugger. I switched to the xbox native debugger and it worked. What I did was in the project property, debugger, pick the "xbox360 debugger" instead of the "xbox360 managed debugger".
Related
I am running Mac OS Catalina, and have Visual Studio version 8.3.8 installed. Before installing Catalina I had no problems building and running my code in Visual Studio.
I don't get any errors when building the code, but each time I try to run my code I get the following dialog popup
Could not connect to the debugger
And I get the following in my terminal:
bash: /Library/Frameworks/Mono.framework/Versions/6.4.0/bin/mono32:
Bad CPU type in executable
I suspect that Catalina doesn't run 32 bit programs, is there a way around this? I thought that Mono from version 5.2 defaulted to 64 bit.
I ran into this issue while using the following settings:
Windows 10
Visual Studio 2019
Macbook Pro
macOS Big Sure 11.4
Visual Studio for Mac (latest)
XCode 12.5
When trying to debug my Xamarin app for IOS and connect my mac in visual studio I had to follow the following steps.
Install mono - https://www.mono-project.com/docs/about-mono/supported-platforms/macos/
Open Visual Studio for Mac (on mac)
Open XCode (mac)
Connect To mac through Visual Studio
After that I stopped getting the connection error.
I know this isn't your exact question, but maybe it can help someone in the future.
I experienced the same problem when trying to debug practically any app in VS Mac. I am now using 2022 and the same issue persisted since using 2019. If trying to debug your code locally, what you can do is to run your app first without debugging. Then, attach the debugger to the executed process. So, if your web app is executing in let's say, "Chrome", then search for that process, usually, it will be the name of your app (it's a dotnet process), then simply attach the debugger to it. Then, you should be able to set breakpoints and hit them.
Hope this will help anyone working with VS for Mac.
I've followed the instructions on how to set up the hello world "AwesomeProject" targetting the "Universal Windows Platform" from https://github.com/ReactWindows/react-native-windows
The app is running and I want to debug. How do I access the developer tools and debugger?
The Getting Started instructions regards debugging on the react-native-windows project just points to the http://facebook.github.io/react-native/docs/debugging.html which mention nothing about this platform.
I've tried all the obvious combinations of Command + D & CTRL-D to no avail.
How do I access the developer tools and debugger?
You can Press Shift + F10 to open dev menu:
Based on the information in here
BTW, On Universal Windows Platform, the react native has helped us to generate all UIElements instead of web elements.
They can be seen in Visual Studio Live Visual Tree windows:
See Inspect XAML properties while debugging
Since some time i got some issue with my Visual Studio 2015 Community edition. When i am trying to debug my windows form application it's stack and when i click on visual studio window i see message
"Delay notification"
and i have to option either
"Switch To"
or
"Continue waiting"
. And it's never come back to work again i have to restart my computer to work again for some time again and then again. I am using windows 10. Do you have any clue why it happens?
Run Visual Studio's setup and click Repair. It's a long process, but works. Also, check if you have updated the Microsoft ASP.NET and Web Tools extension to the latest version.
I'm not able to see any of emulator in VS 2012 express for windows phone. My system has all requirements to run an emulator. previously I was able to debug on emulator. After uninstalling and reinstalling VS 2012 I'm unable to get emulator list and i'm getting error "There were deployment error" and error list shows " Error 1 Exception from HRESULT: 0x89721500". Please help me to solve this problem as I'm unable to test my window phone apps on my system.
Maybe you could fix this issue by deleting this folder:
When you use Visual Studio 2012
C:\Users\<username>\AppData\Local\Microsoft\Phone Tools\CoreCon\11.0
When you use Visual Studio 2015
C:\Users\<username>\AppData\Local\Microsoft\Phone Tools\CoreCon\12.0
Then open VS2012 or VS 2015 again.
If not repairing is always recommended
In addition to Daniel's answer, you may need to then manually repair the emulator install from programs and features in control panel.
I have to maintain an old Compact Framework application written for Windows CE 4.1 in Visual Studio 2003 (sigh!). It's the German localized version of Visual Studio 2003.
Every time i start a debug session in the WinCE emulator, I get this message on the virtual device:
"Microsoft .NET CF 1.0 DE-String ist
bereits installiert. Möchten Sie
erneut installieren?"
which translated into English means:
"Microsoft .NET CF 1.0 DE-String is
already installed. Do you want to
re-install it?"
After clicking "OK" the app runs normally, but it is very annoying havong to click this every time I test the application. Is there a solution for this?
Thanks!
You want to turn off deploying the compact framework to the mobile device when deploying. This is an option that you can turn off in your project properties menu on the devices tab that will stop this from happening each time.