I am doing this Robosapien Kinect project in C# ( http://www.youtube.com/watch?v=TKpO5F8LsCk ) and I zipped the code source form here https://github.com/fatihboy/Robosapien and I don't know why that when I open the KinectRopsapien project with Visual Studio 2012 and I run and debug the MainWindow.xaml.cs window, the window that should show what the Kinect is filming is not opening and there is blue bar on the bottom saying "Ready". I have Kinect for Windows SDK 1.7 installed on my computer. On the first image is a message that appears twice while the code is being debugged in which I click "Continue" (which I think is to finish debugging and I think there is no problem to continue) and the second image is what appears after the code is debugged where you can see the blue bar below saying "Ready" and when the window of what the Kinect is filming should appear, in which I have the Kinect and USB Uirt connected to my computer. So I would like to know why there is no window opening after I run the code? Thank you for your attention
img850.imageshack.us/img850/7566/13285409.png - First image img547.imageshack.us/img547/1449/31396912.png - Second image
Identical problem... XamlParseException after deploying WPF project
In this case the project was clean re-built...
However, I do think it might be deeper than that. Try: http://geekswithblogs.net/lbugnion/archive/2007/03/14/108728.aspx that at least then should give you more concrete information.
This program worked great for me in VS 2010 running .Net Framework 4.0 and debug as x86.
I can see your Debug is set as Any CPU in your screenshot. Make sure it is set as x86.
Related
I am a beginner when it comes to coding, and I have been struggling with a very annoying problem this entire day. I hope you can help me relieve this awful headache.
My idea is to create a very simple app for my Mac, so I downloaded Visual Studio and Xcode.
I followed this tutorial from Youtube to get started, but halfway in the film I see that I am not able to get the same "outputs" as this Youtuber gets ( https://youtu.be/rj_n4W_mDN0?t=340 ). In my case it doesn't automatically provide "NSTextField*LabelInfo", but I can attach the button and label to the script and make them show when I run Visual Studio.
I am not provided this autofill either ( https://youtu.be/rj_n4W_mDN0?t=420 ) or the option of calling the "HelloPressed" function in Visual Studio.
Then I discovered that I have an error message in Xcode when I try to build it: "undefined symbol _main" (which the Youtube person doesn't have).
It also reads:
"Undefined symbols for architecture x86_64:
"_main", referenced from: implicit entry/start for main executable
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)"
I deleted my code and restarted the program, but the same message popped up. I deleted both Xcode and Visual Studio, and reinstalled it, but it still came up. This time I didn't add or do anything other than opening a new projects (in Cocoa app), and still I was greeted with this annoyance.
I see that my "Main.cs" in Visual Studio is not appearing in Xcode project (all the other ones are), but I don't know if this is relevant. I have tried to add different Frameworks to Xcode (AppKit), but I still receive this message. Maybe there is something I have to do in the Build section of Visual Studio, but I don't know what.
I have absolutely no clue what to do and how to proceed. I find it so strange and annoying that the Xcode gives me an Error without me doing anything else then starting up the program. My Macbook pro is very new so that cannot be the cause, the softwares are newly updated: Xcode 11.5 and Visual Studio 8.6.5 (build 23). I am programming in C sharp
I hope you are able to advice me in what to do. I am a beginner so I would appreciate easy-to-follow assistance or instructions.
Thank you very much,
August
Sorry I can't offer a definitive answer but hopefully the following will help you find your issue. I don't usually use VS for Mac and installed it just to see if I could figure out your issues. It is not as intuitive as one may like...
Visual Studio for Mac on both Mojave & Catalina does not work appear to work as the video you found seems to show.
Double-clicking on a .storyboard file generally seems to open the file in VS's XML editor rather than in Xcode. There might be a setting to control this somewhere. To open in Xcode right-click (or control-click) the file name and select Open With… -> Xcode Interface Builder in the menu that appears.
– Once over in Xcode you may find you have two open windows, one is just the .storyboard file and the other is a dummy Xcode project containing it. Close the first of these and just edit within the Xcode project window. If you don't do this you cannot create bindings between the controls and the source. If you look at the Xcode windows in the video you found you will see that when the bindings are being made it is in the project window, but there is nothing to show how/why that window opened up at the front.
Do not try to compile the "project" in Xcode. It is not meant to be compiled and appears to just be the bare minimum scaffolding required to enable VS to use Xcode for UI editing. All the errors you got are related to this.
Searching the internet for Visual Studio for Mac and storyboard files turns up plenty of hits and these files failing to open correctly seems a common problem from a scan of the titles. Do some research and you'll probably get it to work smoothly, but it does work as is albeit a little fiddly. HTH
I'm using Windows 10 ver. 1909. Installer hangs or does nothing. No feedback.
I had exactly this problem. Same version of Windows 10. I tried both vs_community.exe and vs_professional.exe. On a Microsoft Surface Pro 4. The installer launches, a brief unpacking screen appears, that vanishes, and you're left with the task manager showing the installer but no user interface. I tried numerous different suggestions from Googling as well as the Collect.exe tool. None of that helped. Someone had a similar problem that hinted that a display could cause the problem. My Surface had Duet installed, which allows you to use an iPad as a second monitor. Uninstalling that allowed Visual Studio to install normally. Apparently the Visual Studio installer is finicky about displays so if you have any unusual display drivers, or screen sharing utilities, they should be removed to allow installing. I suspect that the driver or utility could be put back after installation.
In my case, the issue was that I have downloaded and launched the installer to a user folder that contains non-English characters. Moving the installer to another folder fixed the issue. I´ve diagnosed the issue by looking into an installer log file in C:\Users<username>\AppData\Local\Temp\dd_vs_professional__143315035.1628536728_decompression_log.txt.
At first you need to download this tool Event Collect for visual studio, open your CMD as administrator,then run Collect.exe , after that you need to run your visual studio installer in the event of an error you will find and file named C:\Users{username}\AppData\Local\Temp\VSSetupEvents.txt that you can check to see the error messages.
For more details you can check documentation .
My case is very embarrassing for Microsoft. I downloaded Visual Studio Setup and started it right away from browser. It was opened and then immediately closed. Nothing I could read on the Internet about this problem was not helping. Then I did one very simple thing. Moved setup from original location: C:\Users(user name)\Downloads, to c:\Temp -> worked like a charm. The thing is that my user name contains international characters (plus containing a space). All in all 21. century, full unicode support everywhere, but not in windows. Really embarrassing.
Visual Studio 2019 Installer doesn't start
I lost time about something I shouldn't have, I couldn't install vscode studio 2019 (I've installed it on multiple machines before).
I don't know exactly why, observed there might be something in my folder blocking it, I just moved it to a new folder and I could install. Good luck and don't make the same mistake as me
I've been working on xamarin to build a crossplatform project on VS2017. I'm in the late phases of development and everything used to work fine. Couple of days ago while coding, I took a brake and updated windows. Since than my visual studio has gone "crazy" . Every time I deploy an application on a device and trying to debug it, it will only show a message in the stack trace and then it will crash my app.
This is what it shows :
Android application is debugging.
In this moment the app will reopen and than crush. It's a very strange behaviour. I of course tried different apps which used to perfectly work, and they have the same issue. I even tried it with a brand new application. Same thing. And of course the app works when I build it from my windows PC to an Iphone or iphone simulator. I can't wrap my head around this.
Has this happened to anybody lately? Is there a problem with the PC or a problem with the VS2017 ???
A little help would be very appreciated. :)
== edit ==
My VS2017 version is : 15.4.2 . Is there any known problem with this kind of version??
try to enable Exceptions
Debug > Windows > Exception Settings
Probably this can be a problem of the emulator. In short, get a fresh installed copy of the .android folder by installing vs on other pc, delete the current one, RESTART your PC and paste the copy to its folder.
To makr things more clear, I believe its good to share my attempts. What I noticed from my experience is, the emulators start behaving odd on your normal debug process. The reasons can be different, some of which were, according to my experience, sudden pc shut down, using large file size images as drawable backgrounds, closing emulator before debug was complete and so on.
Once such odd behavior happened to the emulator, I tried everything I could access online to reset the emulator or create a new one but none solved my problem, even reinstalling vs2017. Finally I was left with one choice which I still think is a foolish idea. Backed up and reinstalled windows, reinstalled VS2017 and other software I needed at that moment. When I was done with clean installation, before I started my work, I copied and backed up the .android folder (almost 10GB for the four default installed emulators) that is located in the user folder and continued my work as usual. And if the emulator fails again at anytime (like even in cases of black screen, being super SLOW, Launcher not responding...), I DELETE the current .android folder in the current user folder, make sure all of the emulators ARE NOT available for the debug option (replaced by start) in visual studio, RESTART the pc (important), copy your backed up .android folder and paste it back to your user folder where it was originally located.
Then you are good to go. I hope this will help someone.
This might have a very simple answer.
I'm trying to learn C# on my Mac, so I downloaded Visual Studio for editing and Xamarin Studio to run. However, after putting in my "Hello World" code into Xamarin, I literally am unable to click the play button on the top left hand corner.
Any ideas? I thought about reinstalling, how do I uninstall Xamarin Studio? What my code looks like.
Press on solution to expand it
Then select startup project by right click
If you still can't build, then you need to download Xamarin.Mac (since you're building on Mac, rather than on a mobile device) You can do that by launching installation, it will ask to re-download missing frameworks.
I am repeating a question posed on Xamarin forums by another user as there has been no solution (http://forums.xamarin.com/discussion/37139/debug-chaos). Since the update to Xamarin at the start of April.
I'm facing very strange debugging errors using Xamarin Studio.
1) Set a breakpoint in the IDE and it stops at the breakpoint with a nullreferenceexception, even when the breakpoint is set on a curly bracket of a function.
2) Move the breakpoint by 1 line and the nullreferenceexception will occur there instead.
I have tried to enable/disable fast deploy and mono shared runtime without changes, and fully reinstalled Xamarin Android and Xamarin Studio.
Any ideas? It's very frustrating to not be able to debug.
Update: Xamarin Studio v5.8.2, Xamarin.Android v4.20.0.37, Nexus 7 (2013) running Android 5.0.2
it is a related to drawable images problem, please do try it that remove image from layout file and then run application as same configure it will be run successfully.
this type of problem i face at staring but now i have the solution to how to handle it.
setting android images and icon is perfect hierarchy which is mention below images and also update your SDK.