.net Framework V4.8
Eugene Aubry
My code is from Visual Studio 8.9 and only supports up to 4.8 on the .net frameworksHowever when I look at the ' ' 4.8 is not available. Only 5.0 is available.5.0 is apparently supported in Visual Studio 8.10 but is not a formal release yet.
I ran into this exact error on my Jenkins server performing a job using MSBUILD: error MSB3644: The reference assemblies for .NETFramework,Version=v4.8 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. There was some back and forth about Visual Studio and about MacOS which muddled things a little, but for me, installing ".NET Framework 4.8 Developer Pack Offline Installer" as suggested by Alsein corrected my problem. Link here -us/download/dotnet-framework/thank-you/net48-developer-pack-offline-installer
fixed almost exactly same error in a project with around 20 dependent projects (and multiple target frameworks) by retargetting the parent project to target no higher frameworks than were targetted by any of child projects.
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...
@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?
I know the nuget runs fine with the .netfull dependency init-parser 2.5.2 (my project is targetting .net6), but there's various forks out there, some even with published packages on nuget.org that do multi-targetting. Why not use one of them?
The present SDK supports multi targets with support to .netstandard2.0.
While I see ini-parser has limited support wrt frameworks it can target to , did you see any compatibility issue with platform-sdk, with .net6
We can add a new feature request to use a different library for parsing ini like ini-parser-netstandard, but interested to know about any existing compatibility problems or restrictions you are facing because of it.
no it works fine with .net6 (and .net7) on windows. However, we may end up running the solution in a linux docker environment - that's what I'm a bit concerned about. We've been using other libs that throw these warnings at restore for years on net5/6/7 without problems, but never on any other architecture.
I'm not sure how .net reacts when it's running on another platform.. if it just doesn't work if you call a method that would require the .net4.x dependency, if it would crash, etc.
You would potentially have a problem there, but you don't have to use the native listener, you can add in a 3rd party of your own choosing and use it. A socket listener is a socket listener, nothing special about theirs.
I can confirm that the choice of WebSocketSharp is unimportant; I'm the one who made that choice a long time ago. It was an off-the-shelf solution for WebSockets that worked at the time; it doesn't do anything unique. Feel free to copy the source code for the NotificationHandler classes into your own app and use whatever libraries you like.
If either of you have a suggestion for a better package to use that has better support, please do share it. We (most of Genesys R&D) aren't .NET developers by trade, so it's helpful to hear from the community that uses it day-to-day.
Set a listener to subscribe to a queue and exit the first response it got (which was heartbeat in this case) but apparently the targeting is fine though utilizing the native System.Net.WebSockets directly may be prudent longer term.
Nice! I'm pretty sure we were on .NET Framework 4.0 when the feature was first added. It looks like the native support wasn't added till 4.5. I'll make sure this gets on the list for consideration. The team that owns the SDKs now is going to be taking a pass at each of them to modernize them (e.g. currently working on a new native TypeScript web-first JS SDK).
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.
Could not install package 'Infragistics.WinForms.Shared 19.2.134'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.8', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
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