Any chance for a vs2010 version?

Jun 23, 2010 at 7:26 PM
It seems to work great on VS2008, but we are upgrading to VS2010 (and soon TFS2010) and I'm not sure if this policy would still work. I'm thinking, at a minimum, the installer needs to be upgraded to create the registry entries for VS2010 (HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\TeamFoundation\SourceControl\Checkin Policies). Would it be a matter or recompiling the policy? Does the license allow me to do so?
Coordinator
Jun 29, 2010 at 7:59 PM
Edited Jun 29, 2010 at 8:00 PM

Sorry about that, I must not have notifications turned on for this project in my daily digest.

We're in the process of upgrading to VS2010 as well (but we won't have TFS 2010 for a while) so I'm in the middle of testing compatibility. I need to figure out a better way of handling the VS and StyleCop integration points. Just changing policy registration may work, that's one thing I'm doing right now with what I'm testing, but I do know that the client assemblies TFS 2010 uses will be different than those used by TFS 2008. So much pain involved in this thing it's unreal. Everytime StyleCop does a release the policy falls behind, and every VS release just kills the thing altogether.

Coordinator
Jul 9, 2010 at 11:45 PM

I got the 1.2 RC1 released, which does add support for VS 2010 and TFS 2010 if you're interested.

Jul 12, 2010 at 11:58 AM

Thanks, I will give a shot.