Azure-functions-core-tools: "Downloading the Azure Functions CLI tools" dialog appears every time I start (debug) an Azure Functions project in Visual Studio.

[michaeldaw]

Every time I start an Azure Functions project in debug mode in visual studio, I see the dialog in the image below.

I thought the problem was related to #1755 but I'm not behind any kind of proxy or anything else that should be blocking it. I've tried a number of things, including deleting the Azure Functions related folders in AppData, upgrading Visual Studio (from 16.5.0 Preview 3, to Preview 5), and repairing the Visual Studio installation, but the problem remains.

[anthonychu]

@soninaren Do you know if there's any ongoing work that's going to address this also?

[garypendlebury]

For me, this only occurs with a v2 Functions project (CLI Tools version 2.45.0), and not with a v3 Functions project (CLI Tools version 3.4.1). With Visual Studio 2019 Enterprise 16.4.5.

[fabiocav]

@soninaren I believe this is related to a download timeout. Can you please share the details on how to perform the out-of-band update here?

[garypendlebury]

A download timeout would make sense, as I experienced this problem whilst suffering an intermittent network connection problem. Today, with the connection restored, the problem has gone away.

@soninaren I believe this is related to a download timeout. Can you please share the details on how to perform the out-of-band update here?

[michaeldaw]

I find that, for me, this problem is only occurring at a particular location that has a fairly poor internet connection. When I'm developing from a different location with a much better connection to the internet, the problem doesn't seem to occur.
This may be consistent with what @fabiocav and @garypendlebury have observed.

[dastewa]

I recently started hitting this issue on a newly created functions project. The answer on this SO question worked for making it stop trying to re-download the tools. Still not sure why this is happening though.

[Harshagracy]

This is a workaround that helped me.

https://stackoverflow.com/a/60342560

[DavidStania]

I've got the same problem. With my slow internet connection, it takes 2 minutes until debug mode starting.

workaround for me:

1. download the current azure functions tools cli from gitHub

1. change the launcheSettings.json

{ "profiles": { "YOUR_PROJECT_NAME": { "commandName": "Executable", "executablePath": "C:\\Users\\USERNAME\\AppData\\Local\\AzureFunctionsTools\\Releases\\3.6.0\\cli\\func.exe", "commandLineArgs": "host start", "remoteDebugEnabled": false } } }

After that, your function is running on local azure functions tools without downloading before debugging.

[anthonychu]

@vijayrkn Do you know why this might be happening?

/cc @stefanushinardi

[vijayrkn]

We have improved this experience in the latest version of Visual Studio (currently in preview 16.8 preview3). We have increased the timeout to download the latest version and made sure that this happening in the back-ground and not impacting the current run.

[aaltotsky]

I have the same issue. Check if any of the folders in
C:\Users{User}\AppData\Local\AzureFunctionsTools\Releases*
are empty. then copy from other folders and update manifest file.

[akousmata]

Still an issue for me using VS 2019 16.8.3. Workarounds mentioned in this need to be updated as well to work with local.settings.json and/or host.json. In a newer version of an Functions project, there is no launchSettings.json. The SO post "works" but is incredibly cumbersome to have to do that every time I want to debug.

[Oxyrus]

@akousmata in my case I had to manually edit my manifest.json (located in one of the release's folder), because as you said, there's no launchSettings.json.