While it has been possible to install Visual Studio Code onto your Raspberry Pi or Jetson Nano, the steps for doing so were less than desirable. The easier of the methods involved acquiring a binary from a third party source. One could make a binary on their own using Microsoft's source code. This avoids the problems with acquiring binaries from unknown sources, but the compilation process is long and was rather involved. Microsoft now makes the compiled binaries available. The installation is an easy process. The binaries are available for installation from https://visualstudio.com. For both the Raspberry Pi and the Jetson Nano the ARM64 .deb (Debian Package) is the option to select. Once it is downloaded, open a terminal and go to the folder in which you've saved the .deb. To install it, use the following command.
sudo dpkg -i name_of_file.deb
After a few moments Visual Studio Code will be installed. You can start it by either typing the word "code" from the terminal or finding Visual Studio Code in the list of programs listed by the graphical UI. That's the entire process.
Easy, isn't it? If you'd like to see a video of the installation check out these videos on the installation on the Pi or on the Jetson.
Having completed the Skyhook Wireless wrapper I think my next article will be on some of the free tools available to enhance one's development environment for Windows Mobile. I have seen (and used) a couple from EQATEC in addition to the Windows Mobile Power Toys.
In my opinion Microsoft is the best company around when it comes to supporting developers. Information on the general Windows Mobile APIs are freely available to everyone; no registration or fees required. The source code is not open, but a majority of the APIs are publically documented. You can find these APIs reference on the Windows Mobile Development Center in MSDN. For Windows Mobile I could divide the APIs into one of 2 categories; native and managed.
If you are just starting with Windows Mobile development you will want to use the Managed APIs. All of these APIs are implemented through .Net. When using these APIs a lot of low level tasks such as some aspects of memory management are taken care of for you. The Native APIs give one direct access to more of the device at the cost of less protection from one's mistakes and more effort being demanded to perform certain tasks. Since versions of the .Net framework are supported on both the desktop and on windows mobile devices you may want to start with some simple desktop application development with .Net before developing on a Windows Mobile device. After getting a foundation in the .Net framework pick up the book "Microsoft Mobile Development Handbook" by Andy Wigley, Daniel Moth, and Peter Foor.
The bear minimum toolset that one would need to develop for Windows Mobile would be the .Net framework and one of the Windows Mobile SDKs. These are free downloads. However, I would strongly encourage you to invest in Visual Studio 2008 Professional. It will provide a much more complete development environment then using the command line tools of the SDK.
You usually have access to the file system of a Windows Mobile device (though some businesses or phone carriers may restrict certain areas of the device for their own security or policy reasons). giving you the ability to copy programs to the device as desired.
I've downloaded the Skyhook WiFi location API for Windows Mobile. Unfortunatly their API is only available for unmanaged code which closes it to people that may not be able to write a managed wrapper. I'd like to open a door for a few people and plan to to create a managed wrapper for the API. Don't know how much time it will take me since I am essentially swamped at work right now.
There were several occasions in the past in which it would have been nice to be able to use telnet on my Windows Mobile 5 phone. I was finally able to take some time this weekend to get something functional together.