Microsoft .net Framework V4.8

[Munir Junker]

Yoann same issue here. Clean install of Windows Server 2019 latest build, install .NET Framework offline installer 4.8, reboot and boom. Many native control panels, like Server Manager, requesting some 4.0.... version of .NET framework instead, failing to load.

I had the same issue and received zero help or support from Microsoft. Dell support googled and read back to me everything I had googled and tried already. Importing the above registry information fixed it without a reboot.

@DavidSherrill This is the exact fix! For us, our RMM tool stopped working on a server 2019 standard server. It's services wouldn't start. Event Viewer complained about .net. Also server manager wouldn't open with the exact message you mentioned. Applying this fixed it all. thanks!!

YOU ARE AN ABSOLUTE LEGEND! THANK YOU! THIS IS THE ONLY SOLUTION THAT WORKED! Every other solution I've googled of this problem has been some variation of "turn net framework on/off in the "turn windows features on or off" app" or "reinstall the newest version of .net" or "did you try restarting your computer?" (OF COURSE I TRIED RESTARTING MY COMPUTER!! DO THEY THINK I'M AN INFANT??)

Please excuse my novice status displayed in this question, but does one simply copy/paste the text in your registry update file, and does the resulting text file require the line number entries as displayed in your post?

Your project does not reference ".NETFramework,Version=v4.8" framework. Add a reference to ".NETFramework,Version=v4.8" in the "TargetFrameworks" property of your project file and then re-run NuGet restore.

I think it was a bad cache of the project.assets.json file. It must have gotten corrupt when restoring a stash that required a merge. VS didn't automatically load the projects. It isn't related to the TargetFrameworks because when you add that property to the csproj file, a different build step fails.

Get a log file and run it through the MSBuild Structured Log Viewer (see the readme for instructions). If things work with one name but not with the other, it sounds like it's either caching or that the name of the project (DotNetExtensions) conflicts with something in the build process. In either case, the log files will contain clues.

It may also be that a dependent NuGet package has been updated to require .NET Framework 4.7.1, in which case actually re-running the NuGet restore in full might be necessary, particularly on old-style .csprojs where changing the target framework still keeps the current package versions around. In that case you have to delete the packages folder, if it exists, or target the previous package version that made everything work.

Error MSB3644 The reference assemblies for framework ".NETFramework,Version=v4.6.2" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend. C:\RPR\Dev\Libraries\Common\Common.csproj C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets 1111

I've tried installing the .NET Framework 4.6.2 SDK, as well as the 4.6 Targeting Pack, however both error that I already have it installed. I also tried installing Visual Studio 2017 but it still gives the same error.

Starting May, 2019 you can build your project on net20 up to net48 (including ne461) any machine with at least MSBuild or the .NET Core SDK installed without the need of Developer Pack installed.

I was using ubuntu and faced the same problem. Even after I've downloaded latest vscode and mono for ubuntu it was not working. Then I found this.

Basically if you've installed mono then go to settings and set

Check the installed .net framework on your development machine, it must be the same as project file targeting. You need to install the .net framework which the project file targeting after that try again the errors and warnings will disappear.

If you've recently installed Unity on Ubuntu 22 and intend to use VS Code for development, chances are you're reading this after you've tried a number of ways and none of them worked...

Requested system administrator to allow windows update for the PC and new feature update through complete windows update enabled the .Net framework v4.8 in Window 10 Build18363 . Now All the applications that were throwing error is working now.

P.S., After further investigation, it appears the Aspose.PDF v22.2 & v22.3 nuget packages are missing the .NET Standard v2.0 dependency. See last attached screenshot. Can you please fix this ASAP?

We have installed Aspose.PDF for .NET through NuGut and have not found any issue with .NET 4.7, .NET 6.0 and .NET Core. Please clean your application and install it again. You may download the latest version of Aspose.PDF for .NET from here:

Download Aspose.PDF for .NET 22.3

I understand that .NET Core 2.0 is no longer supported, but this is not a .NET Core 2.0 issue! It is a .NET Standard 2.0 issue, can you please reread my ticket! Why is this so hard to explain? Also, just FYI, .NET 7.0 is not even released yet!

.NET Standard 2.0 is released as part of the .NET Framework v4.8, which will continue to be supported for years to come, as will .NET Standard 2.0! We compile a .NET Standard 2.0 assembly so that we are compatible with our apps that run the .NET Framework v4.8.

What??? .NET Standard 2.0 was supported through Aspose.PDF v22.1 and is still supported in the most recent versions of Aspose.Word and Aspose.Email, which we have paid for and are using too.

Furthermore, as I stated above, Microsoft recommends targeting .NET Standard 2.0 for all implementations: .NET Standard - .NET Microsoft Learn. Additionally, .NET Standard 2.1 is not released as part of the .NET Framework 4.8, so it is absolutely not an option for most scenarios where .NET Standard is relevant.

You can use .NET Standard 2.1 with Aspose.PDF for .NET. Regarding your concerns, we have updated the issue PDFNET-51559. We will let you know once there is an update available on it. We apologize for your inconvenience.

As I just stated above, we cannot use .NET Standard 2.1, as it is not supported by .NET Framework 4.8. Please fix this issue/oversight ASAP. It is horrible customer support to randomly drop support for a framework that has been supported by Aspose in the current version and is still fully supported by MS, and is also supported by your other products, such as Aspose.Words and Aspose.Email.

Now that Revit 2025 is out, Naturally, most developers will need to upgrade their existent .Net Framework Projects into .NET Core 8.0 project.

Is there a step by step guide to update an existing .NET Framework 4.8 project into a .NET core 8.0 ?

I`ve been attempting to use microsoft upgrade feature but all attempts of my part have failed miserably so far.

Thanks.

I've just been starting a new visual studio file from the template that @nice3point linked above and bringing in all my code files. I've found that it has been easier for my code base(s) for my tools. I also get access to all the cool features built into those new templates.

What about shared projects? How do I handle the migration to .net 8.0? I have problems with the assembly reference.

Update:

I fixed it and it now works for Revit 2025 with with SharedProject.

After starting a new .net 8.0 class library project. i had it all working perfectly, building the project from revit 19 to 25 seamlessly. Up till i decided to set the Assembly Neutral Language.

After that, i could still build to 2025 version, but versions prior to that all fail resulting on the following error:

Severity Code Description Project File Line Suppression State

Error MC1000 Unknown build error, 'Could not find type 'System.Resources.NeutralResourcesLanguageAttribute' in assembly 'C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.8\Facades\System.Runtime.dll'.' MyAssembly_Core C:\Program Files\dotnet\sdk\8.0.202\Sdks\Microsoft.NET.Sdk.WindowsDesktop\targets\Microsoft.WinFX.targets 211

Any guide?

I cant roll it back, even if i set it back to None. the solution wont rebuild for prior versions to 25

3. Follow the steps in the upgrade wizard ("Upgrade project to a newer .net version" --> "Side by side project upgrade" --> "New project" --> name it something like "projectname-netCore" or whatever)

10. In the Solution Explorer, right-click the Properties folder for the new netCore project --> Add new item --> choose "Assembly Info File" and name it AssemblyInfo.cs. Then open that file and add this line to the bottom: [assembly: SupportedOSPlatform("windows")] . This way you won't get spammed with warnings about '...this call site is reachable on all platforms...'

I've never messed with any Assembly Neutral Language. I just have 2 separate projects in my solution, one for Revit 2021-2024 targeting .net framework 4.8.1, and the other for Revit 2025 targeting .net8.0-windows.

You're getting that error while trying to the build your .net8.0-windows project that is referencing the Revit 2025 .dlls? It's weird that the error refers to .net framework 4.8, since nothing in your project should be referencing .net framework after upgrading. Do you have any .net framework nuget packages being referenced from your .net8.0-windows project? Or maybe you accidentally referenced older Revit .dlls built against .net framework? In the Solution Explorer, do you have any warnings in the Dependencies?

3a8082e126