Jump to content


P4VS NuGet support

nuget packages.json checkout

  • Please log in to reply
6 replies to this topic

#1 Max Pavlov

Max Pavlov

    Advanced Member

  • Members
  • PipPipPip
  • 59 posts

Posted 15 March 2016 - 09:01 AM

There is a well know problem that p4vs does not check out packages.config (a standard file in .net projects now) when NuGet package manager is used to bring extenal packages into a project. There has been a discussion on perforce forums that resulted in this: NuGet is changing packages.config not via IDE calls, thus P4VS can't detect file being changed.

I think since then the situation has changed. I've raised this bug with MS at github and they said there is a way for P4VS to support the automatic checkout of packages.config if P4VS implements DTE.SourceControl. I don't know exactly what DTE.SouceControl is, but Perforce, please, do automate the checkout of packages.json when manipulating NuGet packages. The problem affects great deal of your customers.According to comments in the referenced bug page, MS is to contact Perforce about this via their channels as well.Thanks in advance for help.

#2 Svetlana Kofman

Svetlana Kofman

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 15 March 2016 - 06:15 PM

As Max said, in order to integrate P4VS with NuGet package manager, P4VS should implement DTE.SourceControl interface. Documentation is available here: https://msdn.microso...rcecontrol.aspx
NuGet code is open source, and you can get it from GitHub here: https://github.com/N...nts/VsExtension so you can see exactly what we are doing.

NuGet team can provide technical support for the integration process. You can contact us using support@nuget.org

Thanks,
NuGet Team

#3 pditterline

pditterline

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 27 April 2016 - 02:17 PM

Are there any plans to implement this change?  Our team is regularly bitten by packages.config failing to get checked out as well.

#4 tkoehn

tkoehn

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 01 March 2018 - 01:42 PM

using latest VS version (2017 version 15.5.7) and latest p4vs plugin (version 2017.2.161.4623) and the problem still exists.... please fix! PLEASE!

#5 tkoehn

tkoehn

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 16 May 2018 - 12:47 PM

although paying a lot of money for perforce licenses nothing is happening "in reward" :angry:

#6 p4bill

p4bill

    Advanced Member

  • Members
  • PipPipPip
  • 202 posts

Posted 17 May 2018 - 02:58 PM

Hello. Apologies for the lack of response here. We'll investigate this for the next release of P4VS. It would be helpful if anyone here could provide specific repro steps either here or in an email to support@perforce.com.

#7 p4bill

p4bill

    Advanced Member

  • Members
  • PipPipPip
  • 202 posts

Posted 18 December 2018 - 08:35 PM

This is implemented in 2018.4:
	 #1717269 (Bug #66552, 59357)
		 P4VS now implements some of EnvDTE.SourceControl. Other
		 Visual Studio tools can now call IsItemUnderSCC,
		 IsItemCheckedOut, and CheckOutItem. This will enable files
		 like packages.config to be checked out when they are being
		 edited by NuGet package manager.






Also tagged with one or more of these keywords: nuget, packages.json, checkout

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users