Nuget update puts package.config in renegade state

If you are having a problem using Vault, post a message here.

Posts: 14
Joined: Tue Aug 28, 2007 10:13 am
PostPosted: Tue Jun 27, 2017 3:09 am
As the subject states, whenever a nuget package gets added or updated, package.config enters renegade state instead of checked out.
The client normally also have two actions for an updated package file ( Delete + Add ) instead of Modified..? :roll:

Win7 / Win 10 x64
Vault Pro Visual Studio Extension
VS 2017

Posts: 3570
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
PostPosted: Tue Jun 27, 2017 8:27 am
Is it safe to say you're using the Concurrent Development Style options of 'Require Check Out before Check In' and 'Make all files read-only'? If so, can you try to run 'update-package' from the Package Manager Console, does it check out the packages.config file?

Another option is to change your Development Style, that way when Nuget writes directly to package.config or your solution or project (and bypasses the source control events from within Visual Studio, Vault will automatically pick up the changes.

I've never seen the delete / add in pending issue. It could be something new if Nuget is sending commands to delete and create a file rather than modify the file.
Jeff Clausius

Return to Support (Vault Professional)

Who is online

Users browsing this forum: No registered users and 7 guests