Category: Features & Releases
August 01, 2012
Ah, networks. As reliable as they’ve gotten, there’s still the occasional hiccup. Speaking as someone who suffers from a bad VPN client, it’s very annoying to see a network transfer hang and not know if it’s just taking a long time or the connection is broken.
June 01, 2012
One unheralded feature of the 2012.1 release is p4vc, which is included with the P4V installer. p4vc lets you access many of P4V's visual tools like Revision Graph and Time-Lapse View from the command line. It's also easy to launch via a system call in a custom tool, so you can for example launch Revision Graph from your favorite text editor:
April 18, 2012
At Perforce we're pretty agnostic about development tools and processes. Whatever your IDE of choice, we want to either offer a great integration or make it easy for someone else to provide one. So, I'm pretty excited to announce our new Perforce Plug-in for Visual Studio (P4VS). This new plugin makes Perforce a first class citizen in the Visual Studio world.
April 05, 2012
Have you ever wished you could literally take your entire development workspace home with you, file history and all? Well, now you can, thanks to P4Sandbox.
P4Sandbox, which is part of the 2012.1 beta release of Perforce, gives you a private repository for local branches and development work. That local repository is very portable. A regular P4Sandbox instance looks like this on disk:
March 30, 2012
Continuous integration and Agile development are two distinct but related trends in software development. Continuous integration (CI) is really about increasing transparency, but usually manifests itself as automated build and test routines. To put it very briefly, building and testing early and often is a great way to make sure that you’re actually building what you wanted to, and expose potential problems early on.
March 26, 2012
Perforce streams let you capture important information about what actually goes into a codeline. Using stream paths, you can select active modules (modules that are branched and worked on), import other modules as read-only dependencies from the parent stream, and so on. (For more information on stream paths, read this post by Laura Wingerd.)