P4VS, the Helix Plugin for Visual Studio , enables you to use Helix Core as your source control from within Visual Studio.
Fix bug #123
).
Changelists are assigned numbers by Helix Core so you can track them. Changelists enable you to
group related files and submit them together.The following diagram shows the relationship between workspace and depot:
Solution Explorer provides access to most P4VS functionality and status information.
Badges on file icons indicate Helix Core status:
![]() |
Marked for add |
![]() |
Marked for delete |
![]() |
Checked out by you |
![]() |
Checked out by another user |
![]() |
Locked |
![]() |
Version in workspace is not latest version |
![]() |
Workspace version is up to date |
![]() |
Needs resolve (conflicting changes have been made) |
![]() |
File not in Helix Core depot |
![]() |
Marked for integrate |
![]() |
Ignored |
![]() |
File is lazily loaded, whenever operated on by P4VS |
Context-click a file and select Refresh in the context menu to refresh Helix Core status information for the file and any of its children.
If you select Automatically update files status when selection changes in the P4VS Preferences, the file’s Helix Core status updates automatically when you click or hover over the file icon, without having to click Refresh.
P4VS provides the following toolbars that you can use with Visual Studio:
To enable these toolbars, select View > Toolbars.
To enable these toolbars and customize them to show only a subset of the available options, select Tools > Customize.
Watch our P4VS tutorial video: https://www.perforce.com/video-tutorials/plugin-visual-studio
For more information about how to use Helix Core, see Solutions Overview: Helix Version Control System.
For the P4VS release notes, see https://www.perforce.com/perforce/doc.current/user/p4vsnotes.txt.