oqtane.framework VS .NET Runtime

#3042 Fixed margins in Control Panel @leigh-pointer #3040 Added html line breaks to error log notifications @sbwalker #3039 Prevented client ServiceBase logging from looping if server is down @sbwalker #3036 Added logic to package installer to ensure assembly version being installed is equal to or greater than existing assembly @sbwalker #3035 Added a ShowProgress parameter to FileManager to control upload behavior @sbwalker #3034 Fixed issue where Page would disappear if a module was published or unpublished @vnetonline #3030 Displayed warning message to user if package service does not return package requested @sbwalker #3026 Fixed FileManager to call SetImage() before the OnSelect event is fired @vnetonline #3025 Added integration for SupportUrl in Module Definitions and Themes @sbwalker #3024 Removed OnSelect call from OnParametersSet() in FileManager which was causing infinite loop @sbwalker #3020 Added null handling for DisplayName during user creation @sbwalker #3019 Fixed bash script line endings and preserved using gitattributes (credit @rcpacheco) @sbwalker #3018 Allowed page themes to be different from site theme (display warning message) @sbwalker #3017 Added logging to ServiceBase to capture HTTP errors @sbwalker #3016 Enhanced User Management with column sorting @leigh-pointer #3011 Added UserManager class to simplify user management for developers @sbwalker #3011 Improved response validation in ServiceBase for missing Controller methods @sbwalker #3011 Allowed Section component to support parameter changes @sbwalker #3009 Replaced primitive RenderFragment in ContainerBuilder with DynamicComponent @ajahangard #3006 Added handling for both 404 and 403 status codes in GET API response (404 should not log) @sbwalker #2998 Added module name to the Module Settings UI (credit @jlidbeck) @sbwalker #2997 Added logging methods to ThemeBase @sbwalker #2996 Added margin between edit and cog icons @sbwalker #2995 Allowed host users and admins to have personalized pages @sbwalker #2994 Prevented logging of error for personalized pages @sbwalker #2993 Made GetHttpClient() in ServiceBase public @sbwalker #2992 Refactored upload so that it is not dependent on Folder Browse permission @sbwalker #2991 Fixed validation issue in FileManager related to Browse permissions @sbwalker #2989 Added API method to get File based on name @sbwalker #2989 Fixed permission validation for Folder using Browse rather than View @sbwalker #2988 Removed Build action for Oqtane Server in external Theme template @leigh-pointer #2985 Fixed the ResourceType in Module Settings with correct Namespace @vnetonline #2984 Removed Build action for Oqtane Server in external Module template @leigh-pointer #2982 Added package enhancements for Marketplace including SupportUrl @sbwalker #2980 Fixed personalized page to user UserName rather than DisplayName @vnetonline #2975 Added IsRead property to Notifications @vnetonline #2967 Removed RazorLangVersion tag from Client project files @leigh-pointer #2964 Fixed issue where full list of themes was not available in Page Management @markdav-is #2961 Fixed issue where unpublish page was missing logic @leigh-pointer #2959 Fixed issue where module action menu was not displaying the correct mouse pointer @leigh-pointer #2956 Enhanced User Roles Effective and Expiry date to use HTML5 data input @leigh-pointer #2954 Improved Folder API to format path during add/update @sbwalker #2953 Fixed progress bar styling in FileManager @sbwalker #2952 Allowed FileManager to support changes in parameters @sbwalker #2950 Allowed admin to navigate to site settings for deleted site @sbwalker #2949 Fixed issue where HasChildren page property was not considering deleted pages @sbwalker #2948 Reversed ordering of page name and site name for page title to improve SEO (credit @iJungleboy) @sbwalker #2947 Changed UI terminology from Aliases to Urls in Site Settings to improve discoverability @sbwalker #2946 Used case insensitive comparison for ActiveTab name in TabStrip component @sbwalker #2945 Set Expanded to lowercase in Section component if specified @sbwalker #2944 Fixed issue where path was not updated correctly when parent page was changed @sbwalker #2940 Added ThemeSettings and ContainerSettings to external Theme template @vnetonline #2939 Filtered deleted sites in Notification job @sbwalker #2937 Added cosmetic fix for input elements within a table introduced with Bootstrap 5.3 @sbwalker

4.0 was released on June 26, 2023 and is a major framework upgrade to .NET 7. This release includes 104 pull requests by 5 different contributors, pushing the total number of project commits all-time to over 3600. The Oqtane framework continues to evolve at a rapid pace to meet the needs of .NET developers. The 4.0 release is available for download on GitHub.

It's still a thing, and the creator of DNN has moved on and created a new project called Oqtane based on Blazor

The release is available for download on Github and running in production at https://www.oqtane.org and https://www.blazorcms.net.

Does anyone have experience with Oqtane? Apparently it's the successor to DotNetNuke. It looks interesting, I don't have any experience with it. Has anyone tried it?

It looks promising

I would certainly look at Oqtane an framework in Blazor and multi https://github.com/oqtane/oqtane.framework http://www.oqtane.org

It's an interesting "time is a circle" problem given that a century only has 100 years and then we loop around again. 2-digit years is convenient for people in many situations but they are very lossy, and horrible for machines.

It reminds me of this breaking change to .Net from last year.[1][2] Maybe AA just needs to update .Net which would pad them out until the 2050's when someone born in the 1950s would be having...exactly the same problem in the article. (It is configurable now so you could just keep pushing it each decade, until it wraps again).

Or they could use 4-digit years.

[1] https://github.com/dotnet/runtime/issues/75148

These can also be passed as arguments to `dotnet publish` if necessary.

Reference:

- https://learn.microsoft.com/en-us/dotnet/core/deploying/nati...

- https://github.com/dotnet/runtime/blob/main/src/coreclr/nati...

- https://github.com/dotnet/runtime/blob/5b4e770daa190ce69f402... (full list of recognized keys for IlcInstructionSet)

Yes, that is true. I'm not sure about JVM implementation details but the reason the comment says "virtual and interface" calls is to outline the difference. Virtual calls in .NET are sufficiently close[0] to virtual calls in C++. Interface calls, however, are coded differently[1].

Also you are correct - virtual calls are not terribly expensive, but they encroach on ever limited* CPU resources like indirect jump and load predictors and, as noted in parent comments, block inlining, which is highly undesirable for small and frequently called methods, particularly when they are in a loop.

* through great effort of our industry to take back whatever performance wins each generation brings with even more abstractions that fail to improve our productivity

[0] https://github.com/dotnet/coreclr/blob/4895a06c/src/vm/amd64...

[1] https://github.com/dotnet/runtime/blob/main/docs/design/core... (mind you, the text was initially written 18 ago, wow)

If you care about portable SIMD and performance, you may want to save yourself trouble and skip to C# instead, it also has an extensive guide to using it: https://github.com/dotnet/runtime/blob/69110bfdcf5590db1d32c...

CoreLib and many new libraries are using it heavily to match performance of manually intensified C++ code.

DEBUG: packageFiles with updates (repository=local) "config": { "nuget": [ { "deps": [ { "datasource": "nuget", "depType": "nuget", "depName": "Microsoft.Extensions.Hosting", "currentValue": "7.0.0", "updates": [ { "bucket": "non-major", "newVersion": "7.0.1", "newValue": "7.0.1", "releaseTimestamp": "2023-02-14T13:21:52.713Z", "newMajor": 7, "newMinor": 0, "updateType": "patch", "branchName": "renovate/dotnet-monorepo" }, { "bucket": "major", "newVersion": "8.0.0", "newValue": "8.0.0", "releaseTimestamp": "2023-11-14T13:23:17.653Z", "newMajor": 8, "newMinor": 0, "updateType": "major", "branchName": "renovate/major-dotnet-monorepo" } ], "packageName": "Microsoft.Extensions.Hosting", "versioning": "nuget", "warnings": [], "sourceUrl": "https://github.com/dotnet/runtime", "registryUrl": "https://api.nuget.org/v3/index.json", "homepage": "https://dot.net/", "currentVersion": "7.0.0", "isSingleVersion": true, "fixedVersion": "7.0.0" } ], "packageFile": "RenovateDemo.csproj" } ] }

https://github.com/dotnet/runtime/issues/59591

Support zstd Content-Encoding:

We might not be that far away already. There is this issue[1] on Github, where Microsoft and the community discuss some significant changes.

There is still a lot of questions unanswered, but initial tests look promising.

Ref: https://github.com/dotnet/runtime/issues/94620

https://github.com/dotnet/dotnet exists for source build that stitches together SDK, Roslyn, runtime and other dependencies. A lot of them can be built and used individually, which is what contributors usually do. For example, you can clone and build https://github.com/dotnet/runtime and use the produced artifacts to execute .NET assemblies or build .NET binaries.

Yeah, it kind of is. There are quite a few of experiments that are conducted to see if they show promise in the prototype form and then are taken further for proper integration if they do.

Unfortunately, object stack allocation was not one of them even though DOTNET_JitObjectStackAllocation configuration knob exists today, enabling it makes zero impact as it almost never kicks in. By the end of the experiment[0], it was concluded that before investing effort in this kind of feature becomes profitable given how a lot of C# code is written, there are many other lower hanging fruits.

To contrast this, in continuation to green threads experiment, a runtime handled tasks experiment[1] which moves async state machine handling from IL emitted by Roslyn to special-cased methods and then handling purely in runtime code has been a massive success and is now being worked on to be integrated in one of the future version of .NET (hopefully 10?)

[0] https://github.com/dotnet/runtime/issues/11192

[1] https://github.com/dotnet/runtimelab/blob/feature/async2-exp...