New Release of Perforce Visual Studio Plugin: Better Performance and Easier Configuration
The latest release of the Perforce Visual Studio Plugin, P4VS, makes a good thing even better. The updates provide targeted improvements to performance, configuration and usability.
Starting with performance and configuration, the P4VS installation defaults have changed to enable treating solutions/projects as directories. This setting is exposed on the “Perforce – General” page under the “Source Control” section of the Visual Studio options:
If checked, P4VS will execute one command for the entire solution/project directory (when possible) rather than executing a command for each file. This can improve performance for a number of tasks including file sync and the most common background operations.
Also new in the configuration department is the option whether to prompt for the latest revision when checking out a file. This brings P4VS into parity with the Perforce Visual Client, P4V, and helps tailor its behavior to each developer’s preference.
The usability changes include two items. First, P4VS now provides a message about the character set in use when connecting to a Unicode-enabled server. Secondly, it’s now easier to pass Perforce Server connection parameters to custom tools and other processes run by Visual Studio. When the option is enabled, the host connection, user name and client workspace name are passed in the P4VS_PORT, P4VS_USER, and P4VS_CLIENT environment variables, respectively.
Collectively these updates make it easier for developers to write more general scripts and other tools for use from within Visual Studio. So go forth and leverage all the power of Perforce version management with your custom tools!