4 ms·
That doesn't sound right at all. It's been a number of years since I have been at MS, but any engineering team I worked on would have wanted this feedback and f
by nathantotten 10y ago
That doesn't sound right at all. It's been a number of years since I have been at MS, but any engineering team I worked on would have wanted this feedback and fixed the problem. Not supported officially doesn't mean a dev can't spend an hour on a likely simple fix to help a customer - depending on who saw this feedback there are certainly many devs at MS who would fix this without even being asked. I'm willing to bet that's happening right now and this will be resolved in a few days.
- tracker1 10y agoI was fortunate to participate in a bug fix driven by MS (for the Tedious sql adapter for node), and it was impressive. The issue was noticed by someone who worked on Azure (not Azure SQL), who upstreamed the report to appropriate people in the SQL teams who then dug in and found that there was something that wasn't being set right in the tedious adapter. It wasn't an MS product, or supported, and they still took the time to help. I'd be surprised if one didn't find similar responsiveness from at least some of the o365 developers. More often than not, something is "unsupported" not because it doesn't or shouldn't work, but because it doesn't have the dedicated testing resources and in case there is an edge case bug that would be excessively costly to fix (ex: dealing with stupid flexbox issues with the current version of Safari on mac). In any case, it doesn't matter, the response was a bad, canned response that doesn't take into account the troubleshooting the person reporting it already did.