SourceGear Support

Sample project - same problem. I'm on a completely different machine, but again with VS.NET 2015 - classic configuration to a completely separate vault store. Same error. Dual checkout on an aspx.cs page. On the .aspx page - no problem.

I can try a sample project and see what it does. I'll also try one on that other computer and see what's up.

VS.NET 2015 v.14.0.24720.00 Update 1

Other machine isn't working with an ASP.NET application. Seems to only happen in those.

And yes - if I just hit one letter (no matter what) I get the double checkout. Just on the .cs files, though - not on the .ascx/.aspx pages.

I'm set to classic.

And yes, all the files are read-only when viewed through windows explorer (when not checked out).

Some further information. This is for an ASP.NET project. When I type on the .aspx page, it checks out all the child files and I don't get the error message. If I try to type in the code-behind when nothing is checked out, I get the error. So it only appears to affect the .aspx.cs and .ascx.cs files...

The pending change set is blank in the vault client. For information, the Pending Checkins are also blank in the VS.NET 2015 IDE.

Further, this only happens when I start typing in a file that's open. If I right-click on the .ascx file, and check it out, I don't have the issue.

Doing this in VS.NET 2015. I don't have the file checked out to another location. I'm on a single computer with singular access to the vault store. Vault's client has no record of the working directory (it's set to "null" or blank all the way up the tree). I don't know where to set the wor...

I'm getting some strange behaviors in Vault Standard 7.1.0. When I start typing in a file, I get this message. But I don't have the file checked out prior to my typing. When I click on the OK box to clear the message, the file is properly checked out to me. I'm not kidding - this happens with every ...

Other than drive size, there's really nothing prohibiting us from keeping this out there. File backups are an issue as well. Nightly backups of an 8 GB DB are slower and take more space than a 2 GB DB. More importantly, this is triggered by something I've been seeing on my local PC in VS.NET 2012. F...

We've been using Vault for years. The database is currently at 7.69 GB. I'm wondering if there's a way to kill off old check-in's prior to 2 years ago. By my calcs, this should take our DB down to about 2 GB and make the listings much more managable. Is there a way to do this?

Thanks,
Mark