4 ms·
I might be running more .NET software than I realize, but it seems to me that .NET isn't anywhere close to becoming the majority "instruction set" of software s
by glhaynes 14y ago
I might be running more .NET software than I realize, but it seems to me that .NET isn't anywhere close to becoming the majority "instruction set" of software shipped on Windows.
- 0x0 14y agoYou can't blame them for lack of trying to push it though, no? :)
- glhaynes 14y agoAgreed. Although Office staying Win32 sure doesn't send the signal to others that its worth the effort to move software like that to .NET. Anyway, I'm always surprised how few things seem to be .NET, here nearly 11 years after it was introduced.
- wslh 14y agoNo, you need to port Win32, COM and other native libs.
- 0x0 14y agoThat's an easy problem to solve, as Microsoft would be around and able to supply that. As long as 3rd party software is delivered as .NET .exe files they should easily run, probably even when p/invoking, as long as the OS comes with the necessary standard .dlls. Actually I'm quite certain Windows RT already has all this solved under the hood.