top of page

Doc Mac Coaching Group

Public·17 members
James Cruz
James Cruz

All In One Runtimes V2.4.6


.NET Framework 4.6.2 shipped nearly 5 years ago, and .NET Framework 4.8 shipped 2 years ago, so both versions are solid, stable runtimes for your applications. .NET Framework 4.6.2 and 4.8 are highly compatible in-place updates (replacements) for .NET 4.5.2, 4.6, and 4.6.1 and broadly deployed to hundreds of millions of computers via Windows Update (WU). If your computer is configured to take the latest updates from WU your application is likely already running on .NET Framework 4.8.




All in One Runtimes v2.4.6



Things have gotten a little clearer recently with better documentation from Microsoft and clearer designations on what versions of the various .NET runtimes support what version of .NET Standard. With more implementations out in the wild now too, it's easier to see and realize the benefits of .NET Standard whereas in the early days of .NET Core and .NET Standard much of .NET Standard seemed sort of academic.


Any one of those runtimes that want to support .NET Standard have to implement a specific set of .NET features that are defined by .NET Standard. .NET Standard describes the base CoreFx library - what we used to think of as the Base Class Libraries (BCL/FCL) in full framework that make up the core features of the platform.


The big win with .NET Standard is that it provides a common interface to runtime implementers, who have to make sure that their runtimes support the Standard's features and for component implementers that know what features they can use reliably across the platforms supported by the .NET Standard version they are using.


.NET 4.6.1, 4.6.2, .NET 4.7 and 4.7.1 all have partial .NET Standard 2.0 support in the natively shipped runtimes, but they still are .NET Standard 2.0 compliant by adding additional runtime dependencies into your output folder to provide the missing functionality. NuGet along with the runtime targeting handles automatically adding those dependencies to your projects to provide the needed runtime support for those extra features. A lot of those assemblies override behavior from the base framework and .NET uses runtime redirects to route api calls to the appropriate assemblies rather than than mscorlib.dll or other system assemblies.


One way to simplify the installation of the runtime packages is to integrate them by slipstreaming to the Windows installation disc which will require some knowledge in doing that. An easier way is to simply download a program called All in One Runtimes, extract and run it which will automatically install all the required runtimes without any hassle.


All in One Runtimes contains all versions of .NET Framework from 1.1 to 4.5 with hotfixes, Java Runtime Environment 7, DirectX, Visual C++ Runtimes, Adobe Flash Player, Adobe Shockwave Player, Silverlight v5 and Microsoft Visual J# 2.0 SE. All you need to do is download the All in One Runtimes, extract it using an archiver that supports 7z format, and run the aio-runtimes.exe file that is in the svcpack folder. A really nice feature found on AiO Runtimes is the ability to automatically skip the runtimes that are already installed on the computer to prevent an unnecessary reinstallation which may cause more problems.


The Detailliert tab shows more detailed information about the runtimes such as the id, path, parameters, description and prerequisites. Another difference is you get to disable the specific runtime versions from installation. For example, you only see Visual C++ Runtimes at the Installation tab but at the Detailliert shows Visual C++ 2005, 2008, 2010 and 2012. You will also see two different types of Adobe Flash Player which is the ActiveX for Internet Explorer and Plugin for third party web browsers such as Firefox.


The All in One Runtimes is an offline installer which means all the runtimes are already included in the setup file and you can install it on a computer without an Internet connection. However this would also mean that the package will get outdated after sometime due to the constant update of the runtimes to fix any known problems. So make sure you have the latest version before running the All in One Runtimes installer.


.NET Framework 4.6.2 (shipped almost six years ago) and .NET Framework 4.8 (shipped three years ago) are both compatible in-place replacements and stable runtimes already "broadly deployed to hundreds of millions of computers via Windows Update (WU)."


Developers use the .NET Framework to create Windows desktop and server-based applications. This includes ASP.NET web applications. On the other hand, .NET Core is used to create server applications that run on Windows, Linux and Mac. It does not currently support creating desktop applications with a user interface. Developers can write applications and libraries in VB.NET, C# and F# in both runtimes.


By specifying multiple runtimes, they will attempt to be used in the order given, i.e. in the above example if .NET framework 3.5 is installed on a machine (v2.0.50727 indicates CLR 2.0), the application will use it, else it will run on the latest .NET framework version installed.


  • This update for flatpak, libostree, xdg-desktop-portal,xdg-desktop-portal-gtk fixes the following issues:libostree:Update to version 2020.8Enable LTO. (bsc#1133120)

  • This update contains scalability improvements and bugfixes.

  • Caching-related HTTP headers are now supported on summaries and signatures, so that they do not have to be re-downloaded if not changed in the meanwhile.

  • Summaries and delta have been reworked to allow more fine-grained fetching.

  • Fixes several bugs related to atomic variables, HTTP timeouts, and 32-bit architectures.

  • Static deltas can now be signed to more easily support offline verification.

  • There's now support for multiple initramfs images; Is it possible to have a "main" initramfs image and a secondary one which represents local configuration.

  • The documentation is now moved to

  • Fix for an assertion failure when upgrading from systems before ostree supported devicetree.

  • ostree no longer hardlinks zero sized files to avoid hitting filesystem maximum link counts.

  • ostree now supports `/` and `/boot` being on the same filesystem.

  • Improvements to the GObject Introspection metadata, some (cosmetic) static analyzer fixes, a fix for the immutable bit on s390x, dropping a deprecated bit in the systemd unit file.

  • Fix a regression 2020.4 where the "readonly sysroot" changes incorrectly left the sysroot read-only on systems that started out with a read-only `/` (most of them, e.g. Fedora Silverblue/IoT at least).

  • The default dracut config now enables reproducibility.

  • There is a new ostree admin unlock `--transient`. This should to be a foundation for further support for "live" updates.

  • New `ed25519` signing support, powered by `libsodium`.

  • stree commit gained a new `--base` argument, which significantly simplifies constructing "derived" commits, particularly for systems using SELinux.

  • Handling of the read-only sysroot was reimplemented to run in the initramfs and be more reliable. Enabling the `readonly=true` flag in the repo config is recommended.

  • Several fixes in locking for the temporary "staging" directories OSTree creates, particularly on NFS.

  • A new `timestamp-check-from-rev` option was added for pulls, which makes downgrade protection more reliable and will be used by Fedora CoreOS.

  • Several fixes and enhancements made for "collection" pulls including a new `--mirror` option.

  • The ostree commit command learned a new `--mode-ro-executables` which enforces `W^R` semantics on all executables.

  • Added a new commit metadata key `OSTREE_COMMIT_META_KEY_ARCHITECTURE` to help standardize the architecture of the OSTree commit. This could be used on the client side for example to sanity-check that the commit matches the architecture of the machine before deploying.

  • Stop invalid usage of `%_libexecdir`: + Use `%_prefix/lib` where appropriate. + Use `_systemdgeneratordir` for the systemd-generators. + Define `_dracutmodulesdir` based on `dracut.pc`. Add BuildRequires(dracut) for this to work.

  • xdg-desktop-portal:Update to version 1.8.0:Ensure systemd rpm macros are called at install/uninstall times for systemd user services.

  • Add BuildRequires on systemd-rpm-macros.

  • openuri: - Allow skipping the chooser for more URL tyles - Robustness fixes

  • filechooser: - Return the current filter - Add a "directory" option - Document the "writable" option

  • camera: - Make the client node visible - Don't leak pipewire proxy

  • Fix file descriptor leaks

  • Testsuite improvements

  • Updated translations.

  • document: - Reduce the use of open fds - Add more tests and fix issues they found - Expose directories with their proper name - Support exporting directories - New fuse implementation

  • background: Avoid a segfault

  • screencast: Require pipewire 0.3

  • Better support for snap and toolbox

  • Require `/usr/bin/fusermount`: `xdg-document-portal` calls out to the binary. (bsc#1175899) Without it, files or dirs can be selected, but whatever is done with or in them, will not have any effect

  • Fixes for `%_libexecdir` changing to `/usr/libexec`

  • xdg-desktop-portal-gtk:Update to version 1.8.0:filechooser: - Return the current filter - Handle the "directory" option to select directories - Only show preview when we have an image

  • screenshot: Fix cancellation

  • appchooser: Avoid a crash

  • wallpaper: - Properly preview placement settings - Drop the lockscreen option

  • printing: Improve the notification

  • Updated translations.

  • settings: Fall back to gsettings for enable-animations

  • screencast: Support Mutter version to 3 (New pipewire api ver 3).

  • flatpak: Update to version 1.10.2 (jsc#SLE-17238, ECO-3148)

  • This is a security update which fixes a potential attack where a flatpak application could use custom formated `.desktop` file to gain access to files on the host system.

  • Fix memory leaks

  • Documentation and translations updates

  • Spawn portal better handles non-utf8 filenames

  • Fix flatpak build on systems with setuid bwrap

  • Fix crash on updating apps with no deploy data

  • Remove deprecated texinfo packaging macros.

  • Support for the new repo format which should make updates faster and download less data.

  • The systemd generator snippets now call flatpak `--print-updated-env` in place of a bunch of shell for better login performance.

  • The `.profile` snippets now disable GVfs when calling flatpak to avoid spawning a gvfs daemon when logging in via ssh.

  • Flatpak now finds the pulseaudio sockets better in uncommon configurations.

  • Sandboxes with network access it now also has access to the `systemd-resolved` socket to do dns lookups.

  • Flatpak supports unsetting environment variables in the sandbox using `--unset-env`, and `--env=FOO=` now sets FOO to the empty string instead of unsetting it.

  • The spawn portal now has an option to share the pid namespace with the sub-sandbox.

  • This security update fixes a sandbox escape where a malicious application can execute code outside the sandbox by controlling the environment of the "flatpak run" command when spawning a sub-sandbox (bsc#1180996, CVE-2021-21261)

  • Fix support for ppc64.

  • Move flatpak-bisect and flatpak-coredumpctl to devel subpackage, allow to remove python3 dependency on main package.

  • Enable LTO as gobject-introspection works fine with LTO. (bsc#1133124)

  • Fixed progress reporting for OCI and extra-data.

  • The in-memory summary cache is more efficient.

  • Fixed authentication getting stuck in a loop in some cases.

  • Fixed authentication error reporting.

  • Extract OCI info for runtimes as well as apps.

  • Fixed crash if anonymous authentication fails and `-y` is specified.

  • flatpak info now only looks at the specified installation if one is specified.

  • Better error reporting for server HTTP errors during download.

  • Uninstall now removes applications before the runtime it depends on.

  • Avoid updating metadata from the remote when uninstalling.

  • FlatpakTransaction now verifies all passed in refs to avoid.

  • Added validation of collection id settings for remotes.

  • Fix seccomp filters on s390.

  • Robustness fixes to the spawn portal.

  • Fix support for masking update in the system installation.

  • Better support for distros with uncommon models of merged `/usr`.

  • Cache responses from localed/AccountService.

  • Fix hangs in cases where `xdg-dbus-proxy` fails to start.

  • Fix double-free in cups socket detection.

  • OCI authenticator now doesn't ask for auth in case of http errors.

  • Fix invalid usage of `%_libexecdir` to reference systemd directories.

  • Fixes for `%_libexecdir` changing to `/usr/libexec`

  • Avoid calling authenticator in update if ref didn't change

  • Don't fail transaction if ref is already installed (after transaction start)

  • Fix flatpak run handling of userns in the `--device=all` case

  • Fix handling of extensions from different remotes

  • Fix flatpak run `--no-session-bus`

  • `FlatpakTransaction` has a new signal `install-authenticator` which clients can handle to install authenticators needed for the transaction. This is done in the CLI commands.

  • Now the host timezone data is always exposed, fixing several apps that had timezone issues.

  • There's a new systemd unit (not installed by default) to automatically detect plugged in usb sticks with sideload repos.

  • By default the `gdm env.d` file is no longer installed because the systemd generators work better.

  • `create-usb` now exports partial commits by default

  • Fix handling of docker media types in oci remotes

  • Fix subjects in `remote-info --log` output

  • This release is also able to host flatpak images on e.g. docker hub.


About

Welcome to the group! You can connect with other members, ge...

Members

bottom of page