Lex Mitchell

Hi there,

my team has been using the 1.2 Power Tools for while now and one tool that is a favourite is the Annotate function. We have a large codebase and tracking changesets line by line really helps make things more manageable (especially with the enforced comments checkin policy).

Simple question is; why can't we annotate sql text files I'm not sure if this is a config issue, becuase we use a DBP project file (we're looking at DB Pro) or simply due to the need to limit file types that Annotate works on. However I can't spot anywhere a basis for this behaviour i.e. a list of supported filetypes or more to the point a way to include filetypes.

Is there a reason .sql files aren't supported Can we customise the list of supported filetypes And finally out of interest just what filetypes are supported out of the box


Re: Team Foundation Server 每 Power Tools & Add-ons Using the Annotate Power Tool with .sql (or other) files

Jeff B.

I'm not sure what the difference is but the Annotate feature seems to work fine on SQL text files. I am able to Annotate any of the SQL files we have in TFS version control.

I'm running Visual Studio 2005 Team Suite w/SP1.






Re: Team Foundation Server 每 Power Tools & Add-ons Using the Annotate Power Tool with .sql (or other) files

Lex Mitchell

Interesting, are you currently using a .DBP (database project file) for your .sql files I did wonder if this might have been the cause (due to .DBP being non msbuild etc...). We're hopefully moving away from DBP soon (they are are pretty much an ambomination) so if that's all it is then fair enough.



Re: Team Foundation Server 每 Power Tools & Add-ons Using the Annotate Power Tool with .sql (or other) files

Jeff B.

We're using a ".dbproj" file (from VS for DB Pro) to house our .sql files (which is then referenced via a standard VS .sln file). Maybe that's making the difference