Tag Info

Hot answers tagged

9

This seems to be a bug in the dialog. This seems to consistently happen when you try to check in code that hasn't been saved, confusing the feature to a sufficient degree to throw up its hands in the air with this error. The solution is simple: save your files before committing them.


5

I had the same problem and noticed that your share name "sql dump" has a space in it, just like mine. I removed the space character and it worked fine!!


5

I have experienced a similar issue. The work around that we are now using for it is to run VS using our domain credentials. For some reason, your TFS credentials are not enough when running on machines where you are not logged into the domain. runas /netonly /user: "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe"


3

Have you installed Windows 7 Service Pack 1? That's what the error is complaining about. Follow the instructions here to check: http://windows.microsoft.com/en-US/windows7/install-windows-7-service-pack-1 learn if Windows 7 SP1 is already installed Click the Start button , right-click Computer, and then click Properties. If Service Pack 1 is listed ...


2

There is Git support for Visual Studio, which apparently works with all editions (VS Express and up) but requires at least 2012.2. Scott Hanselman: Git support for Visual Studio - Git, TFS, and VS put into Context Getting Started with Git in Visual Studio and Team Foundation Service Visual Studio Tools for Git (download) I haven't used it myself, but ...


1

I suspect that this will not work. See the post below from Microsoft in regards to Visual Studio 2013 and issues connecting with Team Foundation Server 2008. Since they're saying that it is not compatible with TFS2008, I would think that it's safe to assume that even earlier versions of TFS would also not be supported. ...


1

Use Process Monitor from the Sysinternals Suite. Launch ProcMon then add a filter for devenv.exe: Filter -> Filter or Ctrl+L Set the filter to Process Name is devenv.exe then Include Click Add Click OK Launch then close VS 2008 and use ProcMon to see what it's trying (and possibly failing) to do when it closes.


1

To publish Start Date and Finish Date you need to download TFS project field mapping XML change property "PublishOnly" to "false" and then upload XML back to TFS. This is how it should look like: <Mapping WorkItemTrackingFieldReferenceName="Microsoft.VSTS.Scheduling.StartDate" ProjectField="pjTaskStart" PublishOnly="false" />


1

Look into Code Churn reports: http://blogs.msdn.com/b/jampick/archive/2010/07/06/tfs-2010-code-churn-report-getting-additional-detail.aspx they should tell you what (generally) and how much has changed over time.


1

In TFS deny always wins so don't use deny, just uncheck allow. See this question P.s. you don't let developers check in? Wtf


1

This isn't possible with TFS online: http://social.msdn.microsoft.com/Forums/vstudio/en-US/ac56447d-2a58-4620-b3cf-d73025552f97/are-there-any-reports-for-the-agile-template-in-tfs-online


1

I solved the problem by removing Team Foundation Server cache directory on the machine which had problems. Apparently, the old references to a previous Team Foudation Server were causing some conflicts when trying to connect to the new server. The cache directory is located in the Local Settings\Application Data\Microsoft\Team Foundation directory. Delete ...


1

Unfortunately no. Only thing supported with any SVN plug-in would be source control. Team functionality is not supported via SVN.


1

I regularly login to the Windows 2003 interface rather than use the WHS console. I don't have experience with install MOSS or SQL, etc but it wouldn't hurt to check out We Got Served and see if someone else has done it. They are a good resource for WHS tips and tricks.


1

Does the account you are using to run the backup also have full control (or at least write) on the file system folder that is shared (i.e. both share and folder permissions allow writing)? Remember that the account creating the job isn't necessarily the account running it (this might not apply as, IIRC, Power Toys backup doesn't use SQL Agent). Try ...


1

You could try resetting the window layout in Visual Studio. On the Window menu, click Reset Window Layout and see if that resolves it.


1

This is likely because the users mentioned have been added to a group named Work Item Only View Users found at the server level on TFS (in TFS 2010). Here is a blog post that covers this well. Adding users to this group sets it up so that they can only see the ones they create. It also means that they do not require a Client Access License (CAL) for TFS; ...


1

Make sure when you change the run as admin, you change it for all users.


1

Here is links for documentation.. Maybe you ll find something who help you


1

Try these instructions to get detailed tracing information about what is going on in your TFS server.


1

I eventually managed to find the source of the problem! It turns out theat for reasons unknown, the affected users appeared more than once in the Constants table (based on their name that is stored in the DisplayPart column) which resides in our TfsDefaultCollection TFS database. This query highlighted all the records with duplicate DisplayName's: SELECT * ...


1

Firstly, add your project to source control, then go to Solution Explorer, right-click and choose Add | Existing Item, then browse to the files you want to add. Notice that you have the option to add the file as a link. The way that works is that if you add the file then VS moves the file to the project's location, thus creating a second copy of the file - ...



Only top voted, non community-wiki answers of a minimum length are eligible