4 ms·
What was the bug that remained open for 9 years? Was it part of the .net framework or a Windows SDK issue? What sort of projects did you have the most trouble
by alex_hitchins 9y ago
What was the bug that remained open for 9 years? Was it part of the .net framework or a Windows SDK issue?
What sort of projects did you have the most trouble with? Where were your pain points?
- setquk 9y agoSorry was 8 years ... ClickOnce refused to launch on over 2000 machines when they removed download prompting from IE9. This sits between the .net framework and the IE team, neither of which would take responsibility for fixing. Eventually we got a registry fix out of them from bottom line support which turned download prompting back on which was removed from the IE UI but still left in there. The registry fix we had to deploy to hundreds of clients and had a massive support cost. This is still broken in IE11. It was reported on an IE9 beta. Pain points: large project performance, high concurrency projects, IDE reliability, cost, odd time sinks, bugs in the framework, lack of automation possibility for a vast number of project types (try building VSTO applications on a CI server), deprecations (WWF/WCF changes, AppFabric, Velocity etc) all sorts.
- alex_hitchins 9y agoThank you for this response. I'll not counter each point as that will get us nowhere and serve no purpose. I'm just very interested in how two people can have such polar views on the same technology.
- setquk 9y agoI think it's a matter of luck and/or scale. On tiny projects it seems fine but we're huuuuge.
- alex_hitchins 9y agoI'm not familiar with the size of your code estate so I can't compare. I've certainly worked on some 'big' projects with .Net. In terms of users and application structure.