According to the documentation,:
Start VS Code and then connect the DevKit to your computer. VS Code automatically finds the DevKit and opens an introduction page.
But this is not happening. No error is thrown, but nothing happens. I can hear a tone from the computer when the AZ-3166 is plugged-in. It shows up as a storage device on the PC. And the Arduino IDE is able to recognize it.
But VS Code ignores it and does not take me to the introductory page, so I am unable to complete the documented process of connecting to Azure.
I come across this issue as well.
You can resolve this manually by pressing F1 and typing in the command Arduino: Board Manager. From there look up MXChip - Microsoft Azure IoT Developer Kit and install the latest version. From there you should be able to proceed as normal.
Is there a workspace open? If so, try closing it (File > Close Workspace) then close VSCode, reopen and connect your device.
It works for me. Good luck.
Related
I'm more of a newbie into the world of programming but my journey has been a good one with the knowledge I have gathered thus far. However, I'm experiencing quite a problem that no one seems to have a solution to (considering I have been browsing the internet for 2 hours without luck). Android studio shows "No debuggable process" in the logcat and then shows some code running endlessly and the emulator doesn't run. I have updated the drivers of my Samsung phone (A20 - API 28) from the internet but this seems not to work. I am using Android version 3.4.1. I doubt I am that specific but if anyone can help I can provide more details.
Have You enabled adb integration? (to do that just go to Tools-->Android-->Check Enable ADB Integration). Maybe this process can resolve the issue.
Enable ADB Integration is removed from 3.+ versions. It gets active automatically. Still if you want to reset-set it.
You can check Preferences->Build,Execution,Deployment -> Debugger -> Use libusb backend(check/uncheck) it.
Just have the same problem after download Android Studio version 4.1 and checked to Preferences -> Build, Execution, Deployment -> Debugger -> Use libusb backend I found out that Use libusb backend is unchecked by default. Try to check it solve the issue for me
Build and deploy settings are missing from ibm mobile first development server hybrid project.
After clicking on Run as(as in attachment) even from a newly created project..not finding any options. Unable to start application.
Please let me know why it is happening, if any have faced this error before. The image below shows that there's nothing in "Run As...".
Something is wrong with your installation.
Try again in a new Eclipse workspace.
If it fails as well, re-install the Studio plug-in in a fresh Eclipse instance.
I'm just getting started with some of the samples at the Getting Started site, working with the Developers Edition. Whenever I Open Worklight Console, the eclipse environment abends. I'm sure I missed a set up item, but all seemed to install well. I appreciate any help / direction. Thanks.
I tried to post an image of the error, but stackoverflow indicates I need 10 reputations to post an image. Go figure.
The first line is Java was started but returned exit code=8096
There are some hits on this indicating that the license may not be compatible with the Rational license installed. Not sure what to do with that.
There's another post indicating Environment Variable corruption, but I don't have the corrupt Temp environment variables indicated.
StackOverflow has a FAQ explaining what one can and cannot do and when. It makes sense. Read it.
Did you at least create a new Worklight project and application?
If you do that and run the application by right-clicking on the application in the project tree and choose Run As > Run on Worklight Development Server this will: start the server + build the app + deploy the app.
Then you can right-click on the project icon and choose Open Worklight Console and you will see the console...
So unless you have some errors preventing the server from loading, the above should work.
Host the image elsewhere, like imgur.com
Explain what you have installed in your Eclipse. Which Eclipse is it? Did you install only Worklight Studio, or another plug-in in addition? Which?
What are those "hits" you mention? Elaborate.
Searching for the exit code in Google, I see the following IBM tech notes:
http://www-01.ibm.com/support/docview.wss?uid=swg21303648
http://www-01.ibm.com/support/docview.wss?uid=swg21567836
http://www-01.ibm.com/support/docview.wss?uid=swg21627887
Perhaps one of them is relevant for you as well.
If you have followed Idan's advice to Run on Worklight Development Server and it is still not started, try this:
Switch to the Servers view (on the bottom pane of Eclipse by default).
Check your Worklight Development Server status
Right-click and select Clean...
Select OK when prompted to discard all publish start.
Redeploy your app using Run As > Run on Worklight Development Server
I am not sure if this would clean up your environment variable error message as I have not seen that one, but it has helped with several other errors that have caused my server to not start or run properly. (The most common one I get is an Out of Memory in the server.)
If I F5 a Windows 8 JavaScript app and look at the processes pane in VS11, I see that it's WWAHOST.exe that I'm attached to. Is it possible to attach to this after the fact using Debug | Attach to Process? I don't see it in the process list even when I show processes from all users. I see the same thing whether I run locally or in the Simulator. Thanks.
There are effectively two ways to do this. Delay starting the app and attaching the app. You will need to install the remote debugger from Microsoft. As of this writing, it is located on http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=28973
Detailed steps plus explanations are here.
Summary:
Install VS remote tools
On start menu, launch "Debuggable Package Manager" (powershell will start)
using powershell: get-appxpackage (to locate your package)
using powershell: enable-appxdebug PackageFullName
Launch application
Attach to the correct wwahost.exe for your application.
Debugging Topics Located here.
I have recently put together a new development machine and loaded Windows 7 64 bit and VS2010.
I copied over all my projects (VB) from the old machine which was Windows 7 x86 and VS2008.
After following the conversion wizard in VS2010 and installing a third-party component I had forgotten about, my solutions opened and executed fine on the new machine.
Then I tried to work on one of my projects via RDP from a Windows XP machine (something I have done many, many times with the old machine) and the project crashes when run. I get the "no source availiable" tab and an AccessViolationException as soon as the splash screen has loaded. Going back to local operation, the project runs fine.
I've Googled this one to death and I can't find anything that relates to this problem at all. Any sugggestions would be gratefully received.
Thanks.
I do have multiple monitors but have never had a problem before with RDP. Anyways, I found other problems when opening other, older, projects in VS2010 so I uninstalled and reverted to VS2008. All OK now. Thanks for your help.
I was having an issue running Visual Studio 2010 via RDP where the IDE contents except the Solution Explorer wouldn't render. I went to Options->Environment->General->Visual experience and turned off the the "rich client visual experience" options. I suspect turning off "Use hardware graphics acceleration if available" did the trick.
I had also problem with RDP working in "windows 10"
My connection other computers always run successful, but closing after 5-15 second. I very long try fix this error. And I open this exception in VS2015 and read full excaption:
Unhandled exception at 0x00007FFBE35A8283 (ntdll.dll) in mstsc.exe: 0xC0000374: Куча была повреждена (parameters: 0x00007FFBE35FF6B0).
At first I thinked my PC have truble with RAM memory, but I decide change RDP settings and it began work without problem.
I changed the picture quality and uncheck using printer in other window.
My rdp workin very nice now.
I tried many fixes
From the microsoftware, with updates and system files, but nothing helped. I am writing now if someone with the same collision can solve temporarily the problem by lowering the quality of the picture. On a remote computer, it may be very important to simply connect, especially if it is a server.