4 ms·
Microsoft could have fixed it with Win 64bit (Win64). They had done such a step before with the switch from Win16 to Win32 and the help of Win32s. With Win32 t
by frik 10y ago
Microsoft could have fixed it with Win 64bit (Win64).
They had done such a step before with the switch from Win16 to Win32 and the help of Win32s. With Win32 they cleaned up the old API, fixed things yet kept it source compatible when possible. Microsoft could have fixed so many things with Win64 starting with Windows 2003 64-bit. But no, Microsoft invested little on native Windows API between 2002 and 2012 - Longhorn (later Vista) and dotNet were the latest hype.
- problems 10y agoSeems like they're just starting to fix it now with Win10 and only on applications that ship a special manifest (or on entire machines if you set a specific registry entry).
- mikequinlan 10y agoMicrosoft has partially fixed this in Windows 10 but it is not simple or easy. https://blogs.msdn.microsoft.com/jeremykuhne/2016/07/30/net-4-6-2-and-long-paths-on-windows-10/ https://blogs.msdn.microsoft.com/jeremykuhne/2016/07/30/net-...
- Dylan16807 10y ago> Microsoft could have fixed it with Win 64bit (Win64). Ha, they wouldn't even rename System32 when converting it to 64 bit. There was no chance of an API cleanup.
- yuhong 10y agoIt would not be as simple as you think though. Example: https://msdn.microsoft.com/en-us/library/windows/desktop/bb762181(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/desktop/bb7...