None of the items in the selection are valid for this operation.
Could have fooled me. Its a new file in a project, and I want it in Vault too - any way to convince Vault that it is valid for a checkin operation?
"None of the items in the selection are valid for this.
Moderator: SourceGear
Sorry - not thinking straight.
New files I've just added to the Web project (using the standard Add/New WebForm).
I click Check In on the Web project, and it checks in all the other files, and leaves these ones. If I right click on them individually and select Check In, it gives me at above message.
New files I've just added to the Web project (using the standard Add/New WebForm).
I click Check In on the Web project, and it checks in all the other files, and leaves these ones. If I right click on them individually and select Check In, it gives me at above message.
What version of Visual Studio and Vault are you using?
This appears to be Visual Studio that is preventing the operation, but the question is why does it think it can't be checked in?
Did it successfully add the file to source control (and update the project file). Generally when a new file is added to a project, it will automatically put the file and the changed .csproj file in the pending change set (and you have to commit the operation to update the repository).
Does the file ever make it in the repository?
This appears to be Visual Studio that is preventing the operation, but the question is why does it think it can't be checked in?
Did it successfully add the file to source control (and update the project file). Generally when a new file is added to a project, it will automatically put the file and the changed .csproj file in the pending change set (and you have to commit the operation to update the repository).
Does the file ever make it in the repository?
2003 and 3.07
I added the flie, and it had a dark red tick beside it - just like every other file, however it wouldn't add it to Vault.
I manually added it to Vault, and now it seems fine, however I have other files that it flatly refuses to ever add to Vault - no matter what I do, they're invalid, I can add them delete them whatever, but they simply won't be recognised as a valid file for Vault - and it's Global.asax.cs, so not exactly an uncommon file.
I added the flie, and it had a dark red tick beside it - just like every other file, however it wouldn't add it to Vault.
I manually added it to Vault, and now it seems fine, however I have other files that it flatly refuses to ever add to Vault - no matter what I do, they're invalid, I can add them delete them whatever, but they simply won't be recognised as a valid file for Vault - and it's Global.asax.cs, so not exactly an uncommon file.