Tag: Visual Studio

Azurite emulator cannot be started

Callon Campbell [MVP] on January 24, 2022

After installing Visual Studio 2022 and working with Azure Functions I noticed that a new storage emulator is being used called Azurite.

Azurite is an open source Azure Storage API compatible server (emulator). Based on Node.js, Azurite provides cross platform experiences for customers wanting to try Azure Storage easily in a local environment. Azurite simulates most of the commands supported by Azure Storage with minimal dependencies.
https://github.com/Azure/Azurite

This seemed to replace the old Azure Storage Emulator you would run previously when doing local development. I quickly came across an issue where the Azurite emulator cannot be started because port 10000 is already in use. This is also applied to ports 10001 and 10002 which it uses. Here are the contents of the Service Dependencies from the Visual Studio 2022 Output pane:

Ensuring Azure Functions Core Tools are up to date. This may take a few minutes...
Azure Functions Core Tools are up to date.
DotNetCore31-FunctionApp: Azurite emulator cannot be started because port 10000 is already in use. Another instance of the Azurite emulator or Azure Storage emulator might be already running on your machine.
DotNetCore31-FunctionApp: We detected that Azure Storage emulator is running on your machine. The Azure Storage emulator is now deprecated. Microsoft recommends that you use the Azurite emulator for local development with Azure Storage. Follow the directions in the link 'https://go.microsoft.com/fwlink/?LinkID=2167087' to install and run Azurite emulator.
Unable to start dependency 'functions.storage1'.
Ensuring Azure Functions Core Tools are up to date. This may take a few minutes...
Azure Functions Core Tools are up to date.
Ensuring Azure Functions Core Tools are up to date. This may take a few minutes...
Azure Functions Core Tools are up to date.
DotNetCore31-FunctionApp: Azurite emulator cannot be started because port 10000 is already in use. Another instance of the Azurite emulator or Azure Storage emulator might be already running on your machine.
DotNetCore31-FunctionApp: We detected that Azure Storage emulator is running on your machine. The Azure Storage emulator is now deprecated. Microsoft recommends that you use the Azurite emulator for local development with Azure Storage. Follow the directions in the link 'https://go.microsoft.com/fwlink/?LinkID=2167087' to install and run Azurite emulator.
Unable to start dependency 'storage1'.
DotNetCore31-FunctionApp: Azurite emulator cannot be started because port 10000 is already in use. Another instance of the Azurite emulator or Azure Storage emulator might be already running on your machine.
DotNetCore31-FunctionApp: We detected that Azure Storage emulator is running on your machine. The Azure Storage emulator is now deprecated. Microsoft recommends that you use the Azurite emulator for local development with Azure Storage. Follow the directions in the link 'https://go.microsoft.com/fwlink/?LinkID=2167087' to install and run Azurite emulator.
Unable to start dependency 'storage1'.

Let’s drop into Windows Terminal and take a look at what process is using that port:

Get-Process -Id (Get-NetTCPConnection -LocalPort 10002).OwningProcess

After stopping the Node process and re-running Azurite (I restarted Visual Studio) we can see everything starts up as expected:

Ensuring Azure Functions Core Tools are up to date. This may take a few minutes...
Azure Functions Core Tools are up to date.
DotNetCore31-FunctionApp: azurite.cmd --location "C:\Users\ccampbell\AppData\Local\Temp\Azurite" --debug "C:\Users\ccampbell\AppData\Local\Temp\Azurite\debug.log"
DotNetCore31-FunctionApp: Azurite Blob service is starting at http://127.0.0.1:10000
DotNetCore31-FunctionApp: Azurite Blob service is successfully listening at http://127.0.0.1:10000
DotNetCore31-FunctionApp: Azurite Queue service is starting at http://127.0.0.1:10001
DotNetCore31-FunctionApp: Azurite Queue service is successfully listening at http://127.0.0.1:10001
DotNetCore31-FunctionApp: Azurite Table service is starting at http://127.0.0.1:10002
DotNetCore31-FunctionApp: Azurite Table service is successfully listening at http://127.0.0.1:10002

This was not a great experience on the first day I started to use Visual Studio 2022 with Azure Functions as I had to go off and figure out why the Azure emulator could not be started instead of just working on my application. You can go and change the default ports ft you like which is mentioned in the documentation. For more information on Azurite check out the docs on their GitHub repository.

I hope this helps with anyone new to the Azurite emulator in Visual Studio 2022.

Enjoy!

References

https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azurite?tabs=visual-studio

https://github.com/Azure/Azurite

AI Azure DevOps

Writing code and having fun with Rock, Paper, Scissors, Lizard, Spock | Azure Friday

Callon Campbell [MVP] on April 17, 2020

In this episode of Azure Friday, Isaac Levin joins Scott Hanselman to talk about building highly scalable applications and having fun with the Rock, Paper, Scissors, Lizard, Spock sample application. Rock, Paper, Scissors, Lizard, Spock is a multi-language application built with Visual Studio and Visual Studio Code, deployed with GitHub Actions and running on Azure Kubernetes Service (AKS). It also uses Machine Learning and Azure Cognitive Services (Custom Vision API). Languages used in this application include .NET, Node.js, Python, Java, and PHP.

[0:01:55]

Source: Channel 9

Resources

Azure Friday – https://channel9.msdn.com/Shows/Azure-Friday
Free Azure Account – https://aka.ms/cldntvshw/freeazure

Development Events

Discover the world of .NET – .NET Conf 2018

Callon Campbell [MVP] on July 27, 2018

Discover the world of .NET for free this September 12-14, 2018 by attending the .NET Conf virtual developer event, which is co-organized by Microsoft and the .NET community. Over the course of the three days, you will have a wide selection of live sessions from .NET community and the .NET product teams. This is a great chance for you to learn, ask questions and get inspired for your next great project.

You will learn to build for web, mobile, desktop, games, services, libraries and more for a variety of platforms and devices all with .NET. We have sessions for everyone, no matter if you are just beginning or are a seasoned engineer. We’ll have presentations on .NET Core and ASP.NET Core, C#, F#, Azure, Visual Studio, Xamarin, and much more.

Join your fellow developers in a city near you, and learn more about the world of .NET, Azure, and Xamarin. To watch the sessions from last year, take a look at the 2017 sessions on demand from Channel 9.

Agenda

Day 1 – September 12

8:00 – 9:30
Keynote broadcasted from Microsoft Channel 9 Studios

9:30 – 17:00
Sessions broadcasted from Microsoft Channel 9 Studios

17:00 – 18:30
Virtual Attendee Party! Engage with our partners on Twitter and win prizes!

Day 2 – September 13

9:00 – 17:00
Sessions broadcasted from Microsoft Channel 9 Studios

17:00 – 23:59
Community Sessions in local languages & time zones around the world

Day 3 – September 14

0:00 – 17:00
Community Sessions in local languages & time zones around the world

All times listed are in Pacific Daylight Time (UTC -7).

Attend a Local .NET Conf

In addition to the three day virtual event being held from September 12-14, there will also be some local events you can attend. Take a look at this page for locations and to register. In Canada we will have 2 local events in Vancouver BC and Mississauga ON.

September 26, 2018
Vancouver, BC, Canada
Register Here

October 25, 2018
Mississauga, Ontario, Canada
Register Here

Run your own local event

If you’re interested in running your own .NET Conf take a look at this link for details.

Enjoy!

References

https://www.dotnetconf.net

https://www.dotnetconf.net/local-events/

https://github.com/dotnet-presentations/dotnetconf2018

Development Mobile

Troubleshooting the installation of Xamarin Android Device Manager

Callon Campbell [MVP] on February 26, 2018

UPDATED: Feb 26 2018 (later that day)

This post is a follow up to how I got Xamarin Android Device Manager up and running on Windows. Please read the Xamarin Developer guide first which explains how to install and use the Xamarin Android Device Manager for Visual Studio on Windows (or for Mac). Please keep in mind that at the time of this post the Xamarin Android Device Manager is still in preview.

For me I’m running the latest version of Visual Studio 2017 (15.5.7) and I already had the Xamarin components installed and working. Up until now I wasn’t really using the Android emulators for any Xamarin development as I was more focused on iOS and Windows. However now I have a need to and so I decided to try out the new Xamarin Android Device manager. Why you might ask? Well as of Android SDK Tools version 26.0.1, Google has removed support for their UI-based AVD and SDK managers in favor of their new CLI (Command Line Interface) tools.

After having installed the latest version of the Xamarin Device Manager installer for Windows, I ran it from the Start menu with Administrator privileges like so:

And this is the error I get:

I ran through the troubleshooting section section and the issue is that I was missing the Android SDK (requires 26 or higher). Perhaps a one of the latest Visual Studio updates caused this issue because now none of the Android tooling like device or emulator are working. Perhaps installing the Xamarin Device Manager broke it, I’m not sure but it’s broken. The only way I was able to resolve this was to run the Visual Studio Installer and uninstalled the the Xamarin SDK Manager and re-install it. Here is what I did.

My Solution to Fixing Missing Android SDK

1. Run Visual Studio Installer and then click on the Modify button:

2. Now go to the Individual components tab and Remove Xamarin SDK Manager and then click on the Modify button to apply the changes. Take notice of the amount of disk space that will be freed up. For me it was 113 MB.

3. Now do steps 1 and 2 again but this time add back the Xamarin SDK Manager and then notice the amount of disk space required for these changes…for me it was 1.4 GB, obviously something screwed up and I was missing a great deal. Now apply the changes by clicking on the Modify button.

Now when you run the Xamarin Android Device Manager from the start menu (with administrator rights) it should load up as expected. Now if you are like me and don’t have the latest Android SDK Tools, then you are then presented with the following dialog prompting you to download them from the Xamarin Android SDKs and Tools manager:

When the Xamarin Android SDK and Tools manager opens, review the SDK platforms you want installed and then click over to the Tools tab:

In the Tools tab, expand the Android SDK Tools selection and change the selected tooling to the current version which is 26.1.1 and then click on the Apply Changes button. If you’re just changing the Android SDK Tools, this should only take a couple min at most to apply. Once it’s done close down the Android SDKs and Tools manager.

Now go back to Visual Studio (re-run if you have it running already) and run the Android Emulator Manager from the Tools – > Android menu.

You will now be presented with the new Android Devices manager. When you first launch the Android Device Manager, it presents a screen that displays all currently configured virtual devices. For each device, the Name, Operating System (Android API Level), CPU, Memory size, and screen resolution are displayed:

I then went on and added a new option for Android Oreo and when I tried to run it I got another error:

Now it looks like I need to install another tool, Intel’s HAXM which requires Hyper-V be disabled.

Summary

What seemed like a quick and easy update has turned into quite the adventure. It’s 2018…why can’t this be more simple!

Enjoy!

References

Channel 9 | The Xamarin Show: Snack Pack | The New Xamarin Android Device Manager

How to setup and create Android virtual devices using Xamarin Android Device Manager

Installing Xamarin.Android on Windows

Installation Instructions for Intel® Hardware Accelerated Execution Manager (Intel® HAXM) – Microsoft Windows*

Development

GitHub for Visual Studio now allows Pull Request Comments from IDE

Callon Campbell [MVP] on September 26, 2017

GitHub for Visual Studio 2.3 was recently released and it brought new functionality that now allows you to add pull request comments directly from the IDE.

To get started you will need the latest version of GitHub Extension for Visual Studio. Next open up a pull request from the GitHub pane and while viewing a file you can click on the left gutter (see blue plus button) to add your feedback, all without leaving Visual Studio.

This functionality is still pretty limited but its a step in the right direction. I look forward to more GitHub online functionality making it’s way to this great extension.

Enjoy!

References

Inline comments in GitHub for Visual Studio

Development Infographics

Visual Studio 2017 Infographic – What’s New

Callon Campbell [MVP] on April 1, 2017

Curious about what’s new in Visual Studio 2017? The Visual Studio team has released an infographic with all the new features. Take a look.

Enjoy!

VisualStudio2017_ProductLaunchPoster

Development

Visual Studio 2017 has Landed

Callon Campbell [MVP] on March 7, 2017

Visual Studio 2017 is finally here and you can download now. Visual Studio 2017 enables you to be more productive for any application and on any platform.

If you download Visual Studio 2017 by March 14, you’ll get a 60-day access to Xamarin University which is a sweet deal.

What’s New

Visual Studio 2017 has a brand new installation experience which includes a minimal footprint for Visual Studio. Installation is quick (minutes not hours) and finally uninstalls cleanly. It’s also much easier to just install the features you want and need.

Quick Reference of New Features

For a full list of all new features, please take a look at the release notes.

Enjoy!

References

Visual Studio
Visual Studio 2017 Download
Visual Studio 2017 System Requirements
Visual Studio 2017 Release Notes

Development

Extended Strongly Typed Resource Generator for VS2013 and VS2015

Callon Campbell [MVP] on August 20, 2015

Following up to a post I did in 2012 on ResXFileCodeGeneratorEx Update for VS2010, here are links to download this tool for Visual Studio 2015 and Visual Studio 2013:

Extension for Visual Studio 2015 can be found here:
https://visualstudiogallery.msdn.microsoft.com/f43d27fa-6bf7-4f3d-bf5e-3e716e63716b

Extension for Visual Studio 2013 can be found here:
https://visualstudiogallery.msdn.microsoft.com/16d24be3-6400-4a43-b946-766e41aca4bd

Enjoy!