Closed DonovanAGBR closed 1 year ago
6.0.11 hasn't been released yet. 6.0.10 is the latest publicly released build.
If you want to use 6.0.11, you can try the dotnet6
NuGet feed:
<add key="dotnet6" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6/nuget/v3/index.json" />
<add key="dotnet6-transport" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6-transport/nuget/v3/index.json" />
But that's the problem. I don't want to use 6.0.11. The project's reference is using 6.0.10. So why does Visual Studio insist on trying to find 6.0.11?
I added the recommended NuGet feeds and 6.0.11 doesn't appear as an option. 6.0.10 is the latest version.
Here's the project file. As you can see, it's just default project.
<Project Sdk="Microsoft.NET.Sdk.BlazorWebAssembly">
<PropertyGroup>
<TargetFramework>net6.0</TargetFramework>
<Nullable>enable</Nullable>
<ImplicitUsings>enable</ImplicitUsings>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly" Version="6.0.10" />
<PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" Version="6.0.10" PrivateAssets="all" />
</ItemGroup>
</Project>
As a note: I just uninstalled Visual Studio 2022 - 17.4.0 Preview 6.0, uninstalled every .NET SDK, Runtime, and Hosting Bundle I had, and reinstalled VS but still have the same issue.
The project's reference is using 6.0.10. So why does Visual Studio insist on trying to find 6.0.11?
@balachir any ideas on what may be going on here?
@DonovanAGBR can you please try the following in CLI:
dotnet new blazorwasm -o blazorwasm_44828
cd blazorwasm_44828
dotnet build
Does that work as expected? Trying to determine if this is a VS issue or an SDK issue.
I had to add in -f net6.0, but it did the same:
dotnet new blazorwasm -o blazorwasm_44828 -f net6.0
The template "Blazor WebAssembly App" was created successfully.
This template contains technologies from parties other than Microsoft, see https://aka.ms/aspnetcore/6.0-third-party-notices for details.
Processing post-creation actions...
Restoring C:\Code\Sandbox\2022\githubissue\blazorwasm_44828\blazorwasm_44828.csproj:
Determining projects to restore...
C:\Code\Sandbox\2022\githubissue\blazorwasm_44828\blazorwasm_44828.csproj : error NU1102: Unable to find package Microsoft.NETCore.App.Runtime.Mono.browser-wasm with ver
sion (= 6.0.11)
C:\Code\Sandbox\2022\githubissue\blazorwasm_44828\blazorwasm_44828.csproj : error NU1102: - Found 28 version(s) in NuGet Official Package Source [ Nearest version: 7.0
.0-preview.1.22076.8 ]
C:\Code\Sandbox\2022\githubissue\blazorwasm_44828\blazorwasm_44828.csproj : error NU1102: - Found 0 version(s) in C:\Program Files\dotnet\library-packs
Failed to restore C:\Code\Sandbox\2022\githubissue\blazorwasm_44828\blazorwasm_44828.csproj (in 3.31 sec).
Restore failed.
Post action failed.
Manual instructions: Run 'dotnet restore'
Please try:
dotnet new globaljson --sdk-version 6.0.402
and then repeat the steps from above:
dotnet new blazorwasm -o blazorwasm_44828_2
cd blazorwasm_44828_2
dotnet build
I had to reinstall a 6.0 SDK (downloaded 6.0.402) as I had uninstalled ALL of them in my attempts to find a solution. BUT once I did it worked! It was able to build and run.
I ran the same command the project folder I was working in originally and was able to get it restore and build successfully.
Glad it was resolved, closing this out now.
Is there an existing issue for this?
Describe the bug
When I create a new Blazor WebAssembly project targeting NET 6.0, the client project won't build due to the following error:
Upgrading to 7.0 is not an option at this time, however, if I create a new Blazor WebAssembly project targeting NET 7.0 (7.0.0-rc.2.22476.2), the project builds just fine.
As far as I can tell Microsoft.NETCore.App.Runtime.Mono.browser-wasm 6.0.11 doesn't exist. I suspect something is hosed up on my machine, but I can't find where to reset / reinstall / etc. so that VS pulls the actual version currently available. So the issue is this: where do I go or what do I need to reinstall to fix this?
Expected Behavior
When I create a new Blazor WebAssembly project, the solution should build.
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
7.0.100-rc.2.22477.23
Anything else?
Visual Studio 2022 Preview 17.4.0 Preview 6.0