CallbackProcess

Control process start and stop operations in Windows and .NET applications

Installing .NET component into Visual Studio

.NET component is contained in CBProcNet.dll, located in subfolders of <CallbackProcess>\dotNET\ folder. CBProcNet.dll requires MSVC Runtime DLLs. Please refer to Deployment instructions for details on installing those Runtime DLLs on your system for development and on target systems during deployment.

To install components to Visual Studio Toolbox

  1. Use Main Menu -> Tools -> Choose Toolbox items to open Toolbox Customization dialog
  2. In the dialog window that appears switch to .NET Framework Components tab
  3. Find CallbackProcess component in the list and check it.
  4. If you don't find the component in the list, use Browse button to find and add the assembly, which contains the component, to the list.
    Assemblies (32-bit and 64-bit) for .NET 4.6 are located in <CallbackProcess>\dotNET\NET_456 folder.
    Assemblies (32-bit and 64-bit) for .NET 4.5.1 are located in <CallbackProcess>\dotNET\NET_451 folder.
    Assemblies (32-bit and 64-bit) for .NET 4.5 are located in <CallbackProcess>\dotNET\NET_45 folder.
    Assemblies (32-bit and 64-bit) for .NET 4.0 are located in <CallbackProcess>\dotNET\NET_40 folder.
    Assemblies (32-bit and 64-bit) for .NET 2.0 are located in <CallbackProcess>\dotNET\NET_20 folder.

Using components

To use CallbackProcess in your project, you need to include CBProcNet.dll to the list of project references. Then in source file add the following line:

  • C#:
    using CBProc;
  • VB.NET:
    imports CBProc;
  • C++:
    #using <CBProcNet.dll>

Referencing platform-specific assemblies from AnyCPU project

To use CallbackProcess in your AnyCPU project, you need to tell the loader, how to find and load the assembly, which matches your architecture. The sample code in C#-based pseudocode is provided below. The code assumes that you have copies of the assembly, stored in "x86" and "x64" subdirectories of your project's directory. Be sure to turn off "Copy local" option for the assembly reference, so that the compiler doesn't make a (wrong) copy of the assembly to the directory with your project assemblies.


AppDomain.CurrentDomain.AssemblyResolve += PlatformDepResolve;
...
private static Assembly PlatformDepResolve(object sender, ResolveEventArgs args)
{
	if (args.Name.StartsWith("CBProcNet"))
	{
		string architecture;
		if (Environment.Is64BitOperatingSystem)
			architecture = "x64";
		else
			architecture = "x86";

		string fileName = Path.Combine(Environment.CurrentDirectory,
			architecture, "CBProcNet.dll");
		Assembly assembly = Assembly.LoadFile(fileName);
		if (args.Name == assembly.FullName)
			return assembly;
		return null;
	}
}
Thanks to Tyrone Erasmus for the custom resolver implementation.

Back to top