-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get rid of .NET Framework 3.5 (2.0 & 3.0) requirement #64
Comments
I've been thinking about it for a while now... as well as dropping Windows XP support. :-) |
hmm.. i hope it works in WinNT Server 2003 because Reactos.org .. : |
I have zero knowledge of ReactOS. It emulates a Windows Server 2003 system? Does Path Copy Copy work on ReactOS currently? |
Reactos emulate it not, reactos it is a WinNT System written under GPL2 and later free, like a free beer for all ! A Gamechanger because them of Microsoft WinNT, "Reactos is a reaction of the MS Windows policy" overpriced, closed source and many more.. Reactos it is at moment in direction of WinNT Server 2003 so, the Win"XP"Server i have it not tested because lack of the time.. but would interested if it works.. |
Interesting. Thank you for the info! |
you're welcome ! 💯 :) |
be nice to get rid of this requirement. Got to use it just to see my settings? |
@bexier Yes, the requirement is just for the Settings application. |
This change has been implemented. Starting from next version (tentatively known as 17.0), the Settings application will require .NET Framework 4 instead of 2. The installer will no longer attempt to install/enable .NET Framework so for older OSes, the requirement will have to be installed manually. |
Would it be a big deal to migrate the tool to run against a newer version of .NET framework, like 4.xx?
The old framework is really outdated by now and for most software it's not required anymore to install it. So, there should be many systems that have not installed .NET 3.5 by default and having it installed just for path-copy-copy seems quite an overhead...
The text was updated successfully, but these errors were encountered: