I've got a xamarin-forms pcl/android/ios) solution referencing a dll compiled from M2Mqtt (mono).
The app worked fine and still does. I'm still able to compile an run the app on my device, except I can't debug anymore. As soon as the app starts, the breakpoints change from red dots to red circles.
It all started a while ago after I installed some updates (beginning of May). At first I thought this was due to a problem with the latest Xamarin.Forms update, but even reverting to an older one didn't help. I've installed VS2017 community for mac, but no luck. Yesterday I tried to run the debugger on VS2017 on PC, also no luck. I then started to remove references, deleting packets and now I know it's this dll I compiled which is the cause of the debugger not attaching anymore.
How ever, since the app is still working fine and since I can't do without this dll ... does anybody have an idea how I could get the debugger working again?
Best Gerrit
Related
It seems that there are issues with running and debugging Tizen .NET (Xamarin Forms) apps on Tizen emulators.
My environment is a Windows 10 machine, with the latest 2004 version. For development I tried both Visual Studio Professional 2019 (v16.6.2) and VS Professional 2017 (v15.9.24) with the VS Tools for Tizen extension.
I am able to deploy the application on the emulator however cannot debug, VS fails with the message Unable to start debugging. The system cannot find the specified file and in the console output I can see an the message [StdErr] error: cannot remove forward listener.
Does anyone have any idea? Is there some magical software combination that I can use to make this work or am I missing something?
I've experienced no end of troubles with Visual Studio Tools for Tizen. I nearly gave up today completely, I've spent weeks just getting it to partially work, and only a day or two of actual development, but finally figured out a few things that might be unique to my system or most likely are just missing in the documentation (which is not rare for Samsung at all).
First up, the emulator issue. I'm assuming you've been through the certificate manager and generated a Samsung certificate (make sure to have installed the extensions in the package manager, Samsung wearable extensions and Samsung certificate extensions then run through and create your Samsung certificate in certificate manager).
So now in the emulator manager try "right" clicking the specific emulator and select allow to install applications. It might now indicate it has installed a certificate. This is a good sign. Also i assume you know not to use HyperV (you can look up how to create a bootloader that can enable you to dual boot windows where HyperV can be disabled in one and enabled in your default).
Assuming that worked and you still can't debug i found that you may need to build the application (clean the build for good measure first - remember this - it can save you often if things don't work when you change something), then click Start without Debugging from visual studio. This should install the application to the device and launch it, fingers crossed. Now if that worked, and your application is now running in emulator or on device, you may find that future attempts now to debug it will work.
The final thing which has nearly made me give up is the update to my watch. It recently updated and i noted the new tizen version reported by the watch is 5.5. So naturally i went ahead and changed the api level to 5.5 and hey presto it all just seemed to work and i could continue as before, debugging and changing things happily. Then i uninstalled the application for a dry run and since then I spent a week trying to figure out why it will not reinstall the application on the emulator or the watch ( (it was a week ago i upgraded to api 5.5 and there were no issues, so that was way down the list of anything that could go wrong). I reinstalled etc, did the whole gamut of things all to no avail. At some point i got it working on the emulator but not the watch, finally today i have it working on both and don't wish to develop anything, i'm spent.
So that final issue was resoled by moving the projects back to api 4.0 and they would now reinstall on my watch and my emulator (use the Start without Debugging trick as well to install it first). Also (my fault - why it worked on emulator but not watch at some point) beware if you have one that is api 4 and one is api 5.5 - which i did while i was testing the above (one is a service the other the ui - they were at different api levels - that will not work on a device - but was happy on the emulator).
If none of that works for you, i'd advise give up, life is too short.
Cheers
I had issues with VS2015 before and eventually had to reinstall my OS. So after that, I installed VS2015 + Xamarin on my Windows 10 PC. Before I had reinstalled my OS, and before it went all haywire, everything was working fine. The AVMs launched and everything worked well. Now, apparently, even after reinstallation on my OS, the ghosts of the errors don't seem to go away.
This is what's going on:
When I create a simple project, and I debugged the sample code in it, I got this error:
So, naturally, I used the x86 version VM. Then I got this error:
I dug around in Stack Overflow and the other parts of internet and tried multiple things, but nothing seems to have worked. I really would liked to have this sorted out so I can go ahead with my project. Any help is appreciated.
I've tried to remove/reinstall HAXM and
Tried to Install Visual Studio Android emulator
Nothing seems to have worked. With the latter, the debugging is SLOW. It just doesn't do anything. The emulator launches fine, but nothing happens after that. No, I don't get the Stop Debugging button, so..
Thanks
Everything was going fine but the next day, when I opened the visual studio It showed error as
this error occur at every project files and at the starting.
I uninstalled and reinstalled the VS again but also nothing is improved. when I started my pc in safemode , in that case visual studio runs fine however when I opened in normal mode , It shows the error.
Also using command like devenv or devenv/safemode or devenv/resetsettings pops the same error message.
In my experience and from what I've heard from others, VS2005 has problems on newer OS's and needs to be run in a XP VM for reliable results. Some editions of Win7 have a nice transparent way of doing that for software that doesn't like newer OS's, but the VM component needs to be installed first.
I also recall VS getting fouled and needing to be ripped out and re-installed to work again. In your case, re-installing from original media did not include all the service packs and patches, and it probably only worked at all due to updates and a bit of luck. You might try restoring from a backup rather than re-installing, but it's really a lost cause.
Recently, I needed to refresh my Windows 8.1 PC, and now that I have finally finished getting all of my programs reinstalled and everything is back to normal, I am ready to finish work on my Windows 8.1 app, but I am having an issue with compiling my apps. Every time I try to compile, I get the following error.
Now normally when I need to refresh my developer licesnse, Visual Studio tells me, but this time I didn't get any prompt at all, and that is the error that I got when trying to compile. How can I fix this? I am installing updates for Visual STudio at the moment, and I am hoping that doing so will somehow magically fix the problem, but I am also aware that it probably won't.
EDIT: Now that I have updated, the message has been shortened to "Can't resolve Windows.metadata."
For some reason, even though the Windows 8.1 SDK is supposed to be installed with Visual Studio Ultimate 2013, it wasn't for me. I was able to find the Windows 8.1 SDK by Googling it, and it came up as the top result. I installed it, and suddenly all of my errors went away and Visual Studio started recognizing them as legitimate Windows 8.1 app code.
I have an ASP.NET web application that I've been working on for the past few months. Recently I've encountered a problem where when I start debugging and internet explorer launches it locks up. I've tried waiting, but it hangs indefinitely. This happens about 75% of the time. I know it will lock up if the progress bar doesn't show up in the footer. If the progress bar appears then everything works fine. It's turned into a ritual of starting/stopping debugging until it works. If I use Firefox everything works fine. However I can't avoid IE forever as this application is being used in a closed environment where all users are using IE8 exclusively.
I know it's not code related as everything was fine on a Friday, and then with no changes made, it started behaving this way on Monday. I've also opened other web applications and they suffer from the same problem.
I've made sure everything is up to date in Windows Update. I've looked for any updates/fixes to Visual Studio 2010. I haven't been able to find any posts anywhere describing this problem. There's nothing in my logs showing up either.
I'm running Windows 7 SP1 64-bit with VS2010 SP1.
Edit: I've also tried running the solution with IIS instead of the built in dev server, but it had no effect.