dotnet | A simple but effective mini-profiler for ASP.NET ( and Core

Some time ago, a Visual Studio update added a hot reload feature. It be handy, but it also can be annoying especially when you're testing and you don't want to reset the current state of the front end. Visual Studio injects the script whether you're debugging or not.

How can hot reload be disabled? My Visual Studio version is 16.10.3

https://devblogs.microsoft.com/visualstudio/speed-up-your-dotnet-and-cplusplus-development-with-hot-reload-in-visual-studio-2022/

I used the database first approach. The model is right (or at least it looks like) But I always get this error. Please, I've already tried so many things.. The full code of my program (and even sql script by which I create my database) is here: https://github.com/AntonioParroni/test-task-for-backend-stack/blob/main/Server/Models/ApplicationContext.cs

Since I have a mac. I created my model with dotnet ef cli commands (dbcontext scaffold) I can use my context. But I can't touch any DbSet..

I have an Azure pipeline setup for my builds. I have been running into this issue recently and cannot figure out a way to fix this:

When I publish my ABP project I get the following error:

I get the error:

Since updating to Visual Studio 2019 version 16.11.0 (today), compilation of Razor MVC views is failing on multiple cshtml files in multiple projects:

error CS1576: The line number specified for #line directive is missing or invalid

I've tried to set fixed version of .NET Core SDK in global.json file, which was placed in a root folder of MVC Web project, as described here, but that did not help as well.

I have installed .NET 6.0 SDK and Visual Studio 2022. However, Visual Studio 2022 does not offer the ability to select .NET 6.0.

I know I can edit the project file with the target framework so please don't suggest that. This question is specifically around the Visual Studio 2022 UI.

Edit 1:

.NET 6.0 Runtime has been selected in the Visual Studio Installer for Visual Studio 2022

Edit 2:

I can create .NET 6.0 projects but cannot seem to target .NET 6.0 in existing projects which were previously .NET 5.0.

I am using VS 2022, .Net 6.0, and trying to build my first app using System.CommandLine.

Problem: when I build it, I get an error

The name 'CommandHandler' does not exist in the current context

The code I'm trying to build is the sample app from the GitHub site: https://github.com/dotnet/command-line-api/blob/main/docs/Your-first-app-with-System-CommandLine.md , without alteration (I think).

It looks like this:

So I have a c# class library project that I only intend to use on windows. It contains some classes that use the System.Drawing.Image class which is only available on windows. After upgrading to VS2022 and setting the target framework to .NET 6.0 I'm seeing a bunch of warnings that say CA1416 "This call site is reachable on all platforms. 'SomeClass.SomeMethod' is only supported on: 'windows'. See screenshot below for some examples:

In some sense, it's cool that VS2022 has scanned the library and found all the platform specific code that I'm using in the library. But I'd like to tell VS that I only plan to use the library on windows and it can mute all those warnings.

First I checked the Target Platform options in the properties of the project but didn't seen any windows specific targets.

Then I decided to edit the project's .csproj directly and changed the Target framework from

net6.0
to
net6.0-windows

But sadly even after a recompile, that didn't make the warnings go away either. So then I did some reading on the CA1416 warnings and sure enough it says in the Microsoft Docs that the TFM is ignored for assessing this warning however VS does add an attribute to the project based on the TFM that influences this warning, but it only does so if the project is configured to generate the AssemblyInfo.cs file on the fly. But alas, my project's AssemblyInfo.cs is maintained as a actual file rather then having it auto generated at build time.

So at this point, I'm ready to punt the ball and just disable CA1416 warnings for my project. So in the project's .proj file I added CA1416 for both the release and debug builds like so:

One would think that would be the end of those pesky warnings. (sigh) As it turns out, after rebuilding the project the warnings still show up. Got any suggestions? I'm all ears.