New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blazor template samples don't start up on my win10 desktop PC #1779

Closed
TomKuhn opened this Issue Feb 3, 2019 · 6 comments

Comments

Projects
None yet
5 participants
@TomKuhn
Copy link

TomKuhn commented Feb 3, 2019

I've installed visual studio 2017 version 15.9.6
I've installed the blazor language services extension 15.8.31590
I've installed Microsoft .NET Core SDK 2.1.503 x64
I've installed Microsoft .NET Core SDK 2.1.600 - preview x64
I've installed Microsoft .NET Core SDK 2.2.103 x64
I've installed Microsoft .NET Core SDK 3.0.100 - preview (x64)

I can create a new Blazor ASP.NET Core web app in Visual Studio 2017. It builds.

When I run it, it exits immediately without even hitting "main"

I see a lot of dll's loading in the output window:

'dotnet.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.0.0-preview-27324-5\System.Dynamic.Runtime.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.

Why it it loading 3.0.0 dll's when .Net Core 3 is not even supported in vs 2017? Do I need to update IISExpress?

Update: "dotnet run" in the project folder works and blazor is confirmed to be loading dll's in the browser, it's just F5 through VS which is using IISExpress is not working

@iAmBipinPaul

This comment has been minimized.

Copy link

iAmBipinPaul commented Feb 3, 2019

@TomKuhn not sure it will fix or not try running VS as admin.

@hosezelt

This comment has been minimized.

Copy link

hosezelt commented Feb 4, 2019

You probably targeted .Net core 3.0 when creating the project. You can retarget to .Net core 2.1 in the .csproj file and it should run in VS2017.

@danroth27

This comment has been minimized.

Copy link
Member

danroth27 commented Feb 4, 2019

@TomKuhn What output do you see in the browser dev console when running the app?

@danroth27

This comment has been minimized.

Copy link
Member

danroth27 commented Feb 4, 2019

@TomKuhn Also, make sure you use Ctrl-F5 instead of F5 when running a Blazor app in VS. If you F5 VS will try to attache the debugger, which isn't supported yet for client-side Blazor apps.

@Matthew-Bonner

This comment has been minimized.

Copy link

Matthew-Bonner commented Feb 6, 2019

Please do not log issues here. This repo is used only for Blazor infrastructure purposes.

All Blazor code, features, and issues are tracked at https://github.com/aspnet/AspNetCore.

You can use the feature-blazor label to filter issues: https://github.com/aspnet/AspNetCore/issues?q=is%3Aissue+is%3Aopen+label%3Afeature-blazor

@danroth27

This comment has been minimized.

Copy link
Member

danroth27 commented Feb 6, 2019

This issue was moved to aspnet/AspNetCore#7327

@aspnet aspnet locked and limited conversation to collaborators Feb 6, 2019

@danroth27 danroth27 closed this Feb 6, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.