In order to eliminate the confusion and the issue, it seems that I shouldn’t have the option of changing the checkbox “Add schema name to VCS File” unless Subfolders are being used. So it seems like the overall screen layout is off, in that either we have subfolders and an option to remove the schema name, or we don’t have subfolders and so we don’t have choice on the schema name.
From a different perspective, I also understand the heartburn on the duplicated file names, but it almost seems like this should be managed a user issue. The tool should just handle the fact that two objects can exist with the same name and the tool should correctly stop the creation of the Team Coding object saying that it can’t be added because without the schema name, it would cause a duplicate. Then put in a check on enabling and disabling the schema name on the file option such that you can’t disable it without proving there are not any duplicates. Doing it this way gives more choices to the user on how files are to be saved and structured while still protecting the product from causing issues.
Anyways, this give you something to think about while working through the issue.
Thanks (especially on the quick responses!!!),
p.s. Today we will removing our Team Coding project and all references to TFS to see if we recreating it like you described will allow us to remove the schema name.