I appreciate that providing support for VS2005 is a low priority when we're now two releases of VS further on up the road but for many developers, such as myself, using VS2005 is not a choice but a necessity.
What seems a little odd about this decision is that the issue is not whether to implement support for VS2005 but to remove it. Why take away something that many developers would continue to benefit from ?
I develop and maintain, with several other developers, a number of applications that are written in VS2005, VS2008, and we've already started some VS2010 projects. We have all three versions of VS installed. Removing VS2005 integration appears
to be an unnecessary step and it's causing us a problem.
I know there's a workaround to provide StyleCop analysis functionality in VS2005 but it doesn't provide the full integration (StyleCop settings, etc) that we've had in previous versions of StyleCop. So now we have the problem that we can either keep using
an older version of StyleCop with full integration in VS2005 and VS2008 but no VS2010 support, or we install a current version with limited VS2005 support and full integration with VS2008 and VS2010.
If StyleCop 4.4.0 onwards won't support VS2005 then is it at least possible to update the installer to do a side-by-side install with earlier versions of StyleCop that do support VS2005 ? Ideally, I'd like to stick with 4.3.x for VS2005 but use 4.4.x onwards