A recent bug discovery showcased how effective our organization can be at resolving issues when we collaborate across Taylor.
While working on automation with the platform, the NSite development team discovered a bug in Microsoft’s Visual Studio tool that was impacting their efforts. Due to the architecture of NSite, the development team working on automating deployments needed a way to deploy only certain parts of the codebase. While Microsoft provides a standard method to accomplish this, it wasn’t working in the newest version of Visual Studio.
Once they confirmed the bug, the NSite team reported it to Microsoft through a community forum post. They then called upon the substantial developer community within the Taylor organization—other CCM team members, Taylor, and Northern Lights—to help upvote the forum post and escalate its importance. With the power of the Taylor team at work, Microsoft responded quickly, providing a temporary work-around with promises for a fix in the next release of Visual Studio (version 18.3).
The solutions Microsoft provided ended up helping not just the NSite team, but Taylor at large, too. Other Taylor developers started noticing this issue in their own codebases, but they have now been able to make use of the same workaround as the NSite team while waiting for the official bug fix. When the resources of Taylor combine to resolve an issue, we can see how it results in a win-win for everyone.
