Dude, Where's My Framework?
![Image](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhBuoT0QbK49xKkur6IeDULysLeN301nRUQKDL1Y4EE41B2ONf7Ygv57SqsVz6b2fDC2Y8Oht6o2_QjmU1jJHQul3XaVkvmJ_idshq0QhCBSYAp5uz9eErunv3oKeE1gn-s3n32P8CxzosZNCbIz_dDEjCTjtVKhCuoZfkJttvR8jAj97ljaxLLX0bA/s320/NuGetErrorScreenshot.png)
You start out your day with a nice cup of coffee, and think, "Ah, greenfield project day...smooth sailing". You fire up Visual Studio and create a new C# project. "First things first, I need library X." you say. "Wait, what the?" The full error: Package 'MyPackage 1.0.0.0' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework 'net6.0'. This package may not be fully compatible with your project. "Ok" you think, "That library is a bit older. I'll go update the library project to .NET 6 to match my project. But, where is .NET 6? "Ok, what about my new project? Just as a test, does the warning go away if I set it to an older .NET Framework? Wait, where are the .NET Framework versions?"