Windows Net Framework 3.5

[Hadi Sapre]

Inorder to install Windows onto the expansion card, it is necessary to manually create the required partitions, then copy the Windows image over manually. This manual process is entirely accomplished from within the Windows installer itself, by dropping into a command prompt rather than installing graphically as usual.

Once booted into the Windows installer, proceed page by page until you have accepted the license agreement, then on the next page hit Shift+F10 to open a command prompt.

From this point on, ignore the graphical installer, everything will be done manually via the command prompt.

In my case, running Debian Bullseye on my internal drive, I ran the sudo update-grub command and it automatically generated a grub boot menu entry for the Windows Boot Manager. This allows for choosing which OS to boot without having to manually override using the F12 key.

So from the sound of it, if you were to install Windows 10 Pro with /Apply-Image above and then leave this as /index 1, if you were to eventually restore your OS via the recovery partition you would have your install changed to Windows 10 Home

You can then boot back into the Windows installer, repeat the assign letter="" commands from Partition the disk (it seems to forget a few of the letters when you exit the installer), then continue to Copy Windows data to the newly created partitions.

The only difference now is that instead of copying install.esd from X:\sources\ you copy it from your primary Windows partition - in the guide this is W:\ but for me it was C:\. After that I was able to follow the rest of the steps without any hiccups.

And that was it! After Rufus was done, I unplugged my storage card from the other machine and put it back in my framework laptop. I turned it on, spammed f12, selected the storage card as my boot media, and voila: I was in Windows.

The Windows bootloader is installed to a second ESP on the expansion card, so that the only evidence of Windows with the card removed is a useless GRUB menu entry. With the card installed, that entry chainloads Windows.

Brief summary of my dual boot installation. Got Framework naked. The target config was Windows10 and Kubuntu (KDE flavored Ubuntu). Windows would not install from a DVD using USB-A. I had to turn off secure boot and use Rufus to create a thumb drive of the Windows installation. Then fine.

I installed Kubuntu 20.04 (via DVD) only to learn that will not support Framework Wifi and Bluetooth. It appears there are actual problems with the Kubuntu 21.04 installer which are not caused by Framework. Eventually I had to use Windows/Rufus to create a thumb drive of the installer and then it worked.

I have successfully installed dual boot on the NVME drive for Win10 Pro + Ubuntu 21.04. Works like a charm. Even had no need to disable secure boot. Really enjoy the GRUB tiny console window in the left top corner when I boot my laptop.

I plan using Windows 10 Pro installed on the 1TB NVMe SSD as my main OS on my batch 3 Professional specked DIY Edition FW laptop. I do however also spend time in Linux. I don't want to mess around with VM's in windows as I want to be able use all of the machines resources regardless of what OS I am in and don't want to have to go through an additional layer of software to access it. I also do not want to partition the NVMe SSD as I want that to be only for Windows.

Boot Windows 10 Pro from the 1TB NVMe SSD and then use storage expansion cards as boot devices for Linux OS's so that I can just swop out the expansion cards depending on what Linux OS I want to use. Almost like booting from a USB but fully installed.

I am still a amateur to Linux and am often on and off with it as a main OS, so I don't know too much about advanced technical stuff. I do have multiple OS's on Multiple HDD's and SSD's on my custom built PC, but I cant boot into Windows from the boot menu. I have to go into my BIOS and change the boot order any time I want to get into windows which is a pain especially with windows updates. I'm hoping that with this I can just plug in my Linux expansion card(s) and then boot and then pick Windows or Ubuntu/Mint/PopOS and then when I remove the card It will just boot right into windows. Is that easily possible? Any thoughts or suggestions are welcome.

If you install Windows first and then install something like UBuntu next to it, GRUB will give you an option to start Windows before any OS starts to Boot. Using something like Grub Customizer on Linux to change the GRUB default boot option, etc.

@malachid - I just rebooted into the bios and checked. You can reorder the entries using the + and - keys to move down or up while an entry is highlighted and auto-ordering is off. In my case, I have Pop!_OS set up on the internal drive, with windows on an expansion card. I installed refind and left only it enabled, so I can choose what to boot into from there.

I developed the code by creating the project with Windows framework compatibility and created a local package. The folder structure in the local package seem to look good. Please note that the package will be published to the local folder using Studio and is then pushed to orchestrator through Jenkins job

However when the package been pushed to orchestrator, it is recognized as Windows-Legacy. When I try to run in a robot machine, it fails with the error as "Could not find a part of the path 'C:\Users.nuget\packages\lib\net45\project.json

We just started using Windows for new projects and were using legacy earlier. We figured out that the Jenkins pipeline is causing the trouble. Any idea/suggestions on what could be causing the trouble exactly and any solution we have?

Could you verify Project.json once and see if it says Windows there, also from external artefactory verify the project( Convert and unzip if you have to) and then check json file details if you see any difference.

The .NET Framework (pronounced as "dot net") is a proprietary software framework developed by Microsoft that runs primarily on Microsoft Windows. It was the predominant implementation of the Common Language Infrastructure (CLI) until being superseded by the cross-platform .NET project. It includes a large class library called Framework Class Library (FCL) and provides language interoperability (each language can use code written in other languages) across several programming languages. Programs written for .NET Framework execute in a software environment (in contrast to a hardware environment) named the Common Language Runtime (CLR). The CLR is an application virtual machine that provides services such as security, memory management, and exception handling. As such, computer code written using .NET Framework is called "managed code". FCL and CLR together constitute the .NET Framework.

FCL provides the user interface, data access, database connectivity, cryptography, web application development, numeric algorithms, and network communications. Programmers produce software by combining their source code with the .NET Framework and other libraries. The framework is intended to be used by most new applications created for the Windows platform. Microsoft also produces an integrated development environment for .NET software called Visual Studio.

.NET Framework began as proprietary software, although the firm worked to standardize the software stack almost immediately, even before its first release. Despite the standardization efforts, developers, mainly those in the free and open-source software communities, expressed their unease with the selected terms and the prospects of any free and open-source implementation, especially regarding software patents. Since then, Microsoft has changed .NET development to more closely follow a contemporary model of a community-developed software project, including issuing an update to its patent promising to address the concerns.[2]

In April 2019, Microsoft released .NET Framework 4.8, the last major version of the framework as a proprietary offering, followed by .NET Framework 4.8.1 in August 2022. Only monthly security and reliability bug fixes to that version have been released since then. No further changes to that version are planned. The .NET Framework will continue to be included with future releases of Windows and continue to receive security updates, with no plans to remove it as of November 2023.[3]

Microsoft began developing .NET Framework in the late 1990s, originally under the name of Next Generation Windows Services (NGWS), as part of the .NET strategy. By early 2000, the first beta versions of .NET 1.0 were released.

In August 2000, Microsoft, and Intel worked to standardize Common Language Infrastructure (CLI) and C#. By December 2001, both were ratified ECMA standards.[4][5] International Organization for Standardization (ISO) followed in April 2003. The current version of ISO standards are ISO/IEC 23271:2012 and ISO/IEC 23270:2006.[6][7]

While Microsoft and their partners hold patents for CLI and C#, ECMA and ISO require that all patents essential to implementation be made available under "reasonable and non-discriminatory terms". The firms agreed to meet these terms, and to make the patents available royalty-free. However, this did not apply to the part of the .NET Framework not covered by ECMA-ISO standards, which included Windows Forms, ADO.NET, and ASP.NET. Patents that Microsoft holds in these areas may have deterred non-Microsoft implementations of the full framework.[8]

On October 3, 2007, Microsoft announced that the source code for .NET Framework 3.5 libraries was to become available under the Microsoft Reference Source License (Ms-RSL[a]).[9] The source code repository became available online on January 16, 2008, and included BCL, ASP.NET, ADO.NET, Windows Forms, WPF, and XML. Scott Guthrie of Microsoft promised that LINQ, WCF, and WF libraries were being added.[10]

The .NET Compact Framework and .NET Micro Framework variants of the .NET Framework provided support for other Microsoft platforms such as Windows Mobile, Windows CE and other resource-constrained embedded devices. Silverlight provided support for web browsers via plug-ins.

3a8082e126