3 ms·
This has annoyed me going back to Silverlight. They really just don't care users have to install extra things to get your program working. First-party toolkit
by Andrex 5y ago
This has annoyed me going back to Silverlight. They really just don't care users have to install extra things to get your program working.
First-party toolkit stuff like this should be built into the OS.
- andrew_ 5y agoJava and .NET have entered the chat
- Andrex 5y agoI've never quite understood why the .NET runtime didn't ship with Windows. And Microsoft presumably controls Windows Update too, right? :thinking:
- pitterpatter 5y agoOne reason why some have preferred not to ship with Windows is so that they aren't tied to the Windows release cycle. Not to mention, getting fixes into the monthly updates in a whole thing in and of itself.
- tssva 5y agoA .NET runtime does ship with Windows . It is just often not the version being targeted by a developer which means the targeted runtime needs to be installed.
- my123 5y agoThe new (.NET Core then .NET 5 onwards) runtimes aren't installed automatically. But when you install them manually, they are serviced for security updates through Windows Update, so that you don't have to do that manually.
- passivate 5y agoSorry, but I disagree with you, this is a packaging issue. The average user is not in a position to make a determination of which toolkit is required for which binary. The only entity with that information is the developer. The developer should make sure all dependencies are either in the OS, or shipped along with the binary.