3 ms·

Previous experience tells me that developers will use this "feature" and write software that requires users to have it enabled. Previous examples for example b

• rubber_duck 10y ago
  >Previous examples for example being software that requires Microsoft SQL server to be installed on client machines as the software needs certain dll files that comes with Microsoft SQL server. This is on Microsoft as much as it's on the said devs - Windows packaging/distribution is such a mess - registry being the primary source of problems. And Microsoft doesn't do a good job of packaging stuff. At least they are moving in the right direction with .NET core and nuget, ship the whole VM with the app, reference stuff that you need as packages - hopefully you will be able to zip the dist folder and everything will run without the user needing to install anything.
• taspeotis 10y ago
  > Previous examples for example being software that requires Microsoft SQL server to be installed on client machines as the software needs certain dll files that comes with Microsoft SQL server. I don't think this is true, Microsoft ship all the client-side components of SQL Server as a bunch of MSIs you can pick-and-choose between. Since at least SQL Server 2005 [1]. [1] https://www.microsoft.com/en-au/download/details.aspx?id=24793 https://www.microsoft.com/en-au/download/details.aspx?id=247...
  • deleted 10y ago
    [deleted]