Couldn't .Net framework be portable, if the main files were created as symbolic links pointing to the already installed files on portable?
New: r3dfox (July 15, 2025), Platform 30.0.4 (July 15, 2025)
1,100+ portable packages, 1.2 billion downloads
We are operating at a loss, please donate today
If they merely point to the installed local files, that wouldn't be portable. If you have them on the drive but not installed they don't work. If you repackage them in a way that can be carried and work portably, it's a violation of the license... at least the only packages of it I've ever seen. .NET is designed to be OS-integrated, so it's not portable.
Sometimes, the impossible can become possible, if you're awesome!