C#
C#

help

Root Question Message

Rhaenyra
Rhaenyra11/22/2022
❔ How to uninstall. NET Core SDK 7.0.100?

Hello everyone,
I used the dotnet-core-uninstall on command prompt but I get the message "cannot uninstall version 7.0.0 or above"

I use a Windows 10 pc

I need to have .NET core SDK 6 as the latest version installed on my pc

I'm following through a tutorial that works up to. Net 6

How to do it?
Ero
Ero11/22/2022
whatever tutorial you found "that works up to net6", will also work on net7
Rhaenyra
Rhaenyra11/22/2022
@542772576905199626 no it doesn't and I need the new project in. Net 6, do you know how to remove . Net 7? I found only how to remove it on mac from a post on stack overflow
Ero
Ero11/22/2022
none of what you're saying makes sense
Ero
Ero11/22/2022
net6 code is upwards compatible with net7
Ero
Ero11/22/2022
you can change the target framework by... just doing that
Rhaenyra
Rhaenyra11/22/2022
@542772576905199626 in the command prompt the project is by default created in. Net 7 but I want it in. Net 6
Ero
Ero11/22/2022
here's a .net 7 project:
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net7.0</TargetFramework>
  </PropertyGroup>
</Project>

and here's a .net 6 project:
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
  </PropertyGroup>
</Project>
Ero
Ero11/22/2022
notice something
Ero
Ero11/22/2022
and just use .net 7
Ero
Ero11/22/2022
like geez
Rhaenyra
Rhaenyra11/22/2022
@542772576905199626 i need. Net 6 for multiple reasons
Ero
Ero11/22/2022
there is not a singular good reason you can name
tebeco
tebeco11/22/2022
install both on your computer and both will run
tebeco
tebeco11/22/2022
and your project can still run net6
tebeco
tebeco11/22/2022
you don't need to uninstall net7 to install net6
tebeco
tebeco11/22/2022
else uninstall just like any windows software
tebeco
tebeco11/22/2022
in the "uninstall program" menu
Message Not Public

Sign In and Join Server To See

11/22/2022
tebeco
tebeco11/22/2022
fun fact ... it's not a very good reason
tebeco
tebeco11/22/2022
because it's generally not applicable / not a thing / not done / not used / not nothing
tebeco
tebeco11/22/2022
all it gives is confort for managment on "we'll update it later"
tebeco
tebeco11/22/2022
they got used to windows version being 10+years
tebeco
tebeco11/22/2022
or weird old netfx too
tebeco
tebeco11/22/2022
that time is long gone and its ~3year max
tebeco
tebeco11/22/2022
so you can stay on LTS to "avoid" having to spend a very little time on bump most of the time
tebeco
tebeco11/22/2022
to them ... have to the years right after anyway
tebeco
tebeco11/22/2022
so you're saving yourself ~1 year
tebeco
tebeco11/22/2022
I'm not saying it's a good or bad idea
tebeco
tebeco11/22/2022
but it's not a VERY good reason
tebeco
tebeco11/22/2022
especially regarding the near 0 cost bump stince core 3.0 => now
tebeco
tebeco11/22/2022
the 2.x => 3 was costy for aspnetcore but not that much once you understand it
Message Not Public

Sign In and Join Server To See

11/22/2022
tebeco
tebeco11/23/2022
it's only 3 years max with an overlap of only 1 year on a non LTS
tebeco
tebeco11/23/2022
so it's mostly a concept for "dev fatigue"
tebeco
tebeco11/23/2022
mostly team that don't have update mechanism in place for doing that for you and upfront
tebeco
tebeco11/23/2022
if you have that in your team generally the cost of the update is way lower
tebeco
tebeco11/23/2022
it cost way more when you're "forced" because "it's not LTS 3 weeks, quick quick"
tebeco
tebeco11/23/2022
and also is was more a thing in 2.x when msft.ext.* and msft.aspnetcore.* were ns2.0
tebeco
tebeco11/23/2022
which made the code base compliant over runtime update
tebeco
tebeco11/23/2022
now they are release as part of the cycle of both runtime and aspnetcore release
tebeco
tebeco11/23/2022
take for example STJ and Logging
tebeco
tebeco11/23/2022
literraly 2 super important pilar from aspnetcore and any decent generic host stack
tebeco
tebeco11/23/2022
the SourceGenerator they come in won't be available unless you're net6
tebeco
tebeco11/23/2022
etc ... etc ...
tebeco
tebeco11/23/2022
at the same time
tebeco
tebeco11/23/2022
"but you don't understand library maintainer .... blablabla ...."
tebeco
tebeco11/23/2022
well with that model library maintainer HAVE to cross target
tebeco
tebeco11/23/2022
<TargetFrameworks>netstandard2.0;netcoreapp3.1;net6.0;net7.0</TargetFrameworks>
tebeco
tebeco11/23/2022
or more like it's super recomended
tebeco
tebeco11/23/2022
because depending on what's in their code
ContactFrequently Asked QuestionsJoin The DiscordBugs & Feature RequestsTerms & Privacy