Skip to content
/ P4.net Public

Fork of the official P4.NET project that adds support for .NET 4

Notifications You must be signed in to change notification settings

milang/P4.net

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

28 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

P4.NET

P4.NET is a fork of the original P4.NET component created by Shawn Hladky. It provides managed implementation of Perforce API. Main features of this fork (as opposed to Shawn's original):

  • Support for CLR 2 (.NET 2.0, 3.0, 3.5)
  • Support for CLR 4 (.NET 4.0)
  • Single AnyCPU assembly (works in both 32 and 64 bit .NET runtimes)

Overview

Based on: http://public.perforce.com:8080/guest/shawn_hladky/P4.Net/main/

Current version: 2.0.0.3 (Feb 15, 2011; sources; binaries)

Build requirements: Visual C++ 2010 (free edition should have no problems)

How to build

  1. Download sources from GitHub or clone the repository using Git

  2. Run/double-click (project_root)/p4.net_build.cmd. This will produce the following binaries:

  • bin/Debug_v2.0/P4API.dll (pdb, xml) - signed P4.NET assembly in debug mode, compiled for .NET 2.0 (i.e. usable from .NET 2.0, 3.0 and 3.5)
  • bin/Release_v2.0/P4API.dll (pdb, xml) - signed P4.NET assembly in release mode, compiled for .NET 2.0 (i.e. usable from .NET 2.0, 3.0 and 3.5)
  • bin/Debug_v4.0/P4API.dll (pdb, xml) - signed P4.NET assembly in debug mode, compiled for .NET 4.0
  • bin/Release_v4.0/P4API.dll (pdb, xml) - signed P4.NET assembly in release mode, compiled for .NET 4.0

Note: It is not possible to compile the C++ component of P4.NET (mixed-mode assembly p4dn, embedded in assembly p4api) with statically linked runtime libraries. This means that p4dn.dll is dependent on msvcrt100.dll (or msvcrt100d.dll in debug build). Because different versions of runtime DLLs are needed for different process bitness, it is not possible to distribute a single copy of the runtime DLLs with P4.NET (when running on a 64 bit operating system, a .NET process can run in 32 bit mode where a 32 bit p4dn will be loaded that will require 32 bit msvcrt100.dll, while another .NET process can run in 64 bit mode where a 64 bit p4dn will be loaded that will require 64 bit msvcrt100.dll).

Installing Visual C++ 2010 runtime is the easiest way to solve this problem (if another program already installed the runtime, no action is needed) :

About

Fork of the official P4.NET project that adds support for .NET 4

Resources

Stars

Watchers

Forks

Packages

No packages published