In my usual workflow, when I’m developing an API with Visual Studio, and I need to access it from a mobile app, I publish the API to Azure or a local IIS server. I need to do this because, by default, IIS express publish your API with the localhost endpoint, and it can’t be easily used outside the running machine. I was looking for a quick fix when I found Conveyor, a Visual Studio extension that automatically provides our API’s external access. Additionally, I created an account on their website to enable public access to my API (outside of the local network). After installing the extension, it would start when I run my project in Debug mode. In the following screenshot, you can see which ones are the enabled endpoints.
We can also enable the use of certificates for HTTPS access. A great addition to my toolbox, easy to install and use 😉
I want to be able to run locally my back end apps that use Azure while I’m working on it.
In the past I used the Azure Storage Emulator but is no longer being supported, Azurite is the new version and in this post I will show you how to install it and start using it.
There are several ways to install Azurite in your development machine like a Visual Studio Code extension, NPM or Docker, we are going to use Docker (If you don’t have it installed, check my post Installing Docker for Windows).
Open a powershell command prompt and use the following command to pull the latest Azurite docker image
One of the advantages of using WSL is that we can now run Hyper-V (I use Hyper-V for android emulators) side by side with Linux containers, this was not possible before when Docker needed to use VirtualBox.
At this point Docker is installed and we can follow the provided tutorial.
To check that everything is working as expected, we can open a powershell window and execute the docker -v command.
Also in the context menu from the docker taskbar icon, we can switch to Windows Containers
And that is all! I hope this was useful and let me know what do you think in the comments!