Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
netslave
Starting Member
9 Posts |
 Posted - 2009-01-12 : 14:16:09
|
| A few months ago, my team started using Team Foundation Server to store our scripts. Usually, when I would create a new project, I would get a prompt to navigate to the folder in TFS to save the project files under. Example: Server>>DBA>>Conversion Projects>>New ProjectNow, I do not get that prompt and it automatically selects a current project and creates my new project in a subfolder. It always select the same project to create the new project under. Example:Server>>DBA>>Conversion Projects>>Old Existsing Project>>New ProjectSo it seems is though there's a default path saved somewhere that is telling either TFS or SQL Server Management Studio to save it in that one project. Any ideas how I can stop this? |
|
|
netslave
Starting Member
9 Posts |
Posted - 2009-01-15 : 08:54:32
|
| FYI - I figured out how to stop it.I still don't know what the problem was, I'm assuming it was the binding for the project that it kept creating subfolders for. I don't know, but to solve the issue, I first tried to reinstall the MSSCCI Provider that allows SSMS to talk to the Team Foundation Server but that didn't help. The only thing that worked was opening a new project from source control. Once I did that, I could start creating new projects and choosing their locations again. |
 |
|
|
|
|
|
Team Foundation Server