The name "WebHost" does not exist

[alessandroros]

Describe the bug

I get the following error:
The name 'WebHost' does not exist in the current context. As I can see the WebHost

To Reproduce

I would like to create a WebApi project using .Net Core 2.2.0.
I'm using the scaffolded solution proposed from Visual Studio.

Program.cs (which I see is the same as the doc):

{
    public class Program
    {
        public static void Main(string[] args)
        {
            CreateWebHostBuilder(args).Build().Run();
        }

        public static IWebHostBuilder CreateWebHostBuilder(string[] args) =>
            WebHost.CreateDefaultBuilder(args)
                .UseStartup<Startup>();
    }
}

Throws the following error

VS Community 15.9.4
NetCore 2.2.101

[davidfowl]

Looks like it might be a resharper issue. Try updating reaharper

[alessandroros]

thanks for your tip, you're right.
After disabling it the error disappears.

[quentingarlan]

I had the same issue without resharper, could not find any solution but going back to .Net core 2.1.0. It seems that I am not the only one : https://stackoverflow.com/questions/53623730/webhost-doesnt-exist-in-the-current-context-in-asp-net-core-2-2-default-api-tem

[alessandroros]

I had the same issue without resharper, could not find any solution but going back to .Net core 2.1.0. It seems that I am not the only one : https://stackoverflow.com/questions/53623730/webhost-doesnt-exist-in-the-current-context-in-asp-net-core-2-2-default-api-tem

After checking better you're correct. Disabling ReSharper was a workaround for Net Core 2.1.
With NetCore 2.2 the WebHost issue is still present even with ReSharper disabled.

WebHost now is no more "red", but just underlined: anyway the error is the same:

The name "WebHost"does not exist in the current context

[PTurczynowski]

I had the same problem but I found the solution: In properties of the project select as Target framework one of the .NET Core framework, ex. .NET Core 2.1, save. Then select correct framwork - .NET Core 2.2

Rebuild project. That's all.

[alessandroros]

I tried but it doesn't work for me.

Just to repeat your steps:

1. Change Target Framework to 2.1
2. Save
3. Rechange Target Framework to 2.2
4. Save and Rebuild Projects

Correct?

[quentingarlan]

I add some luck building in administrator mode, I noticed a permission error was sent when compiling. But no guarantee it would work for you, I still don't know the route cause of the issue.

[alessandroros]

No luck even with administrator mode enabled, for the moment I'm switching back to 2.1.

[PTurczynowski]

I tried but it doesn't work for me.

Just to repeat your steps:

1. Change Target Framework to 2.1
2. Save
3. Rechange Target Framework to 2.2
4. Save and Rebuild Projects

Correct?

Yes, steps are correct. But check if in csproj file something has been change after 1 and 3 steps. And make sure that Microsoft.AspNetCore.App (2.2.0) dll is added to the project.

[alessandroros]

Ok I didn't have that package.
I don't know how to add it on SDK, I tried to added it via Nuget package, using the command:

PM> Install-Package Microsoft.AspNetCore.App

But nothing has changed. Other advices?
Are you using the community edition or the professional one?

[alessandroros]

I tried but it doesn't work for me.
Just to repeat your steps:

1. Change Target Framework to 2.1
2. Save
3. Rechange Target Framework to 2.2
4. Save and Rebuild Projects

Correct?

Yes, steps are correct. But check if in csproj file something has been change after 1 and 3 steps. And make sure that Microsoft.AspNetCore.App (2.2.0) dll is added to the project.

Ok I added manually the line:

<PackageReference Include="Microsoft.AspNetCore.App" />

to the .csproj file of the project.
Then I also noticed that for new application scaffolded by vs studio 2017 15.9.4 , the .csproj also adds in PropertyGroup:

<AspNetCoreHostingModel>InProcess</AspNetCoreHostingModel>

Rebuilded, and then now no more issues

[Eilon]

Glad you got it working!