Skip to main content

Visual Studio Dev Tunnels

Today I want to talk about a great feature in Visual Studio 2022; dev tunnels (originally called port tunneling/forwarding). It allows you to create an ad-hoc connection from your local machine to the internet. This means that an ASP.NET Core project (or Azure Function) running locally on localhost can be made accessible to any device with an internet connection.

Some use cases:

  • Developing an API that is consumed by Power Platform.
  • Developing a web hook for an external service.
  • Testing a web app on an external device.

Let me show you how to start using this feature in Visual Studio.

Create a Dev Tunnel

  • Open Visual Studio 2022
  • Go to Views –> Other Windows –> Dev Tunnels. This will load the Dev Tunnels window.
  • Click on the + sign to create a new Dev Tunnel.
  • On the Create window, you need to specify the following
    • Account: Choose the account that will be used to create the tunnel
    • Name: This is the name that is used to show it in the list of available tunnels
    • Tunnel Type: Choose the lifetime of the tunnel. A persistent tunnel will reuse the same URL whereas a temporary tunnel will use a new URL each time Visual Studio is restarted.
    • Access: Decide who can access this tunnel. Private makes it only accessible to the account you are using, Organizational will limit access to people inside your organization and Public makes it available to everyone(not recommended).

  • Click on OK to create the tunnel. If creation is successful, you should get a message and the tunnel becomes available


Using the Dev Tunnel

  • Create a new ASP.NET Core project or open an existing one
  • Click on the arrow icon next to the Run button and select the created dev tunnel(if not selected yet)


  • Now click on the Run button
  • After authenticating, you get a warning that you are about to connect through a dev tunnel the first time you try to use it. Click on Continue


  • Now the website is available on a public URL


Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more