Share via

Azure Functions isolated (net8.0) incorrectly requires .NET Desktop workload to load projects.

Richard Coleman 0 Reputation points
2026-04-21T08:35:37.6733333+00:00

I have an Azure functions project that works fine in VS2022. When I open the project with VS2026, it prompts me to install .NET Desktop. The following is my .csproj (with the project names renamed).

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>net8.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
    <RootNamespace>My.Project.Functions</RootNamespace>
    <AzureFunctionsVersion>v4</AzureFunctionsVersion>
    <OutputType>Exe</OutputType>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.Azure.Functions.Worker" Version="2.0.0" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Timer" Version="4.3.1" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Sdk" Version="2.0.2" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore" Version="2.0.1" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Storage.Queues" Version="5.5.0" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.OpenApi" Version="1.5.1" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.ApplicationInsights" Version="2.0.0" />
    <PackageReference Include="Microsoft.ApplicationInsights.WorkerService" Version="2.23.0" />
  </ItemGroup>

  <ItemGroup>
    <ProjectReference Include="..\My.Project.Domain\My.Project.Domain.csproj" />
    <ProjectReference Include="..\My.Project.Application\My.Project.Application.csproj" />
    <ProjectReference Include="..\My.Project.Infrastructure\My.Project.Infrastructure.csproj" />
  </ItemGroup>

  <!-- Copy example JSON files to output directory -->
  <ItemGroup>
    <None Update="Examples\*.json">
      <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
    </None>
  </ItemGroup>

</Project>

Visual studio 2022 did not require this workload, and I don't understand why VS2026 thinks it needs it.

I am running:

April 2026 Feature Update - v18.5.0

Instance - 4b6f5e37

Developer technologies | Visual Studio | Setup
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Lizzy Dinh (WICLOUD CORPORATION) 435 Reputation points Microsoft External Staff Moderator
    2026-04-21T10:28:25.06+00:00

    Hi @Richard Coleman ,

    Thank you so much for sharing your concern with us — I completely understand how this behavior could be confusing.

    In this case, Visual Studio 2026 is using an updated dependency detection approach compared to Visual Studio 2022. Because of this change, it may interpret project requirements differently. For your specific setup (Azure Functions isolated on .NET 8.0), Visual Studio 2026 can sometimes misidentify which components are actually needed and may suggest installing an unrelated workload.

    So even though the same repository opened in Visual Studio 2022 without any prompts, Visual Studio 2026 might now display a dialog when it believes something is missing — even if that recommendation isn’t entirely accurate.

    What’s happening here is that the new Setup Assistant in Visual Studio 2026 uses broader workload detection, which can occasionally be triggered by Azure Functions isolated projects. To ensure the best and most accurate IDE experience, the recommended approach would be to install or update the Azure Development workload (along with the related Azure Functions tools and templates), rather than installing the .NET Desktop Development workload just to satisfy this prompt.

    I hope this helps clarify why you're seeing this behavior and prevents any unnecessary changes to your environment. If you have any other questions or run into further issues, please don’t hesitate to reach out — I’d be happy to assist.

    If you found this support helpful, I’d really appreciate your feedback through the platform.

    Wishing you a great day ahead!

  2. Frederik Seyns 161 Reputation points
    2026-04-21T09:56:21.49+00:00

    your .csproj is a normal Azure Functions isolated worker project targeting .NET 8. Nothing in it requires “.NET Desktop Development”. The prompt you’re seeing in VS2026 is almost always caused by Visual Studio mis-identifying the project type because the Azure Functions tooling/templates inside VS are missing/outdated/corrupted, so VS falls back to a generic workload recommendation (often “.NET Desktop”). This kind of “stale tooling download” behavior has been seen before with Azure Functions support inside Visual Studio, and the fix is to update the Azure Functions toolsets and templates inside Visual Studio.

    FIX: Update Azure Functions tools inside VS2026

    1. In Visual Studio 2026, open Tools > Options.
    2. Go to Projects and Solutions > Azure Functions.
    3. Select Check for updates, then Download & Install.
    4. Restart Visual Studio and re-open the solution.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.