I'm not sure if this is a TFS issue or a VS.NET source control plug-in issue, so please let me know if I've posted this to the wrong forum:

I'm seeing an issue with the algorithm that determines whether files in the /bin directory of a web project should be automatically added to source control. In my solution, the web projects only have 'Project Dependencies' (or .NET SDK dependencies). This triggers VS.NET to copy the binaries for the dependent projects into the /bin directory of the ASP.NET projects at build time. VS.NET/TFS is generally smart enough to realize that the files copied into the /bin directory as a result of this operation are dynamic and should not be added to source control.

However, some of these assemblies contain localized resources and thus generate satellite assemblies. The satellite assemblies and associated folders are correctly copied into the /bin directory of the ASP.NET Web projects. However, VS.NET/TFS incorrectly decides that the satellite assemblies need to be checked into source control and executes an Add operation.

It's possible to undo the add, as VS.NET has not checked in that changeset, but this happens often enough that it could easily lead to errors where some of our developers don't notice that update and accidentally check in these files.

Anyone else seen this? Is there a workaround? Is there some other mechanism for submitting bug reports that I should follow?

Thanks,
Aaron