Discuss this help topic in SecureBlackbox Forum

Installing and using .NET components

Using the components in your projects

Add the references to needed assemblies to your project. Please note that the separate set of assemblies is provided for each support target platform. See the list of directories below to choose and reference the correct assemblies.

Be sure to reference all indirectly used assemblies in your project, as described in "Deployment of .NET components" topic.

Installing .NET components into Visual Studio Toolbox

The components are integrated into Visual Studio automatically. If you need to add the components to Toolbox manually, please do the following: In Visual Studio

  1. Use Main Menu -> Tools -> Choose Toolbox items to open Toolbox Customization dialog
  2. In the dialog that appears activate .NET Framework Components tab
  3. Use a filter to show only those components, which contain "SecureBlackbox" in the assembly name. To do this put "SecureBlackbox" to the filter box.
  4. Check all components that appear.
  5. If you don't find some component in the list, use Browse button to find and add the assembly, which contains the component, to the list. The assemblies are located in <SecureBlackbox>\Assebmlies\XX folder, where XX depend on which development tools you are using and what platforms you are targeting (see below).

The assemblies for use and deployment can be found in <SecureBlackbox>\Assemblies directory, which includes several subdirectories, namely

  • MONO_20 - the assemblies that work on MONO 2 and 3
  • MONO_40 - the assemblies that work on MONO 4
  • NET_20 - the assemblies that work on .NET 2.0, .NET 3.5
  • NET_40 - the assemblies that work on .NET 4.0
  • NET_45_Desktop - the assemblies that work on .NET 4.5 on Win32 Desktop
  • NET_45_WinRT - the assemblies that work on .NET 4.5 / Windows RT (not for Windows Store)
  • NET_45_WinStore - the assemblies that work on .NET 4.5 / Windows RT (for Windows Store)
  • NET_451_Desktop - the assemblies that work on .NET 4.5.1 on Win32 Desktop
  • NET_451_WinRT - the assemblies that work on .NET 4.5.1 / Windows RT (not for Windows Store)
  • NET_451_WinStore - the assemblies that work on .NET 4.5.1 / Windows RT (for Windows Store)
  • NET_46_Desktop - the assemblies that work on .NET 4.6 / Win32 Desktop
  • NET_CF20 - the assemblies that work on .NET Compact Framework 3.9, 3.5 and 2.0
  • Silverlight_50_Windows - the assemblies that work on Silverlight 5 (with Windows bindings, such as Certificate Storage, PKCS#11, NTLM auth)
  • Silverlight_50_XPlatform - the assemblies that work on Silverlight 5 (cross-platform version, without Windows bindings)
  • WindowsPhone_8 - the assemblies that work on Windows Phone 8
  • WindowsPhone_8.1 - the assemblies that work on Windows Phone 8.1
  • Xamarin.Android - the assemblies that work on Xamarin.Android
  • Xamarin.iOS - the assemblies that work on Xamarin.iOS
You choose, what assembly sets you need to use with your application. For example, if your application is designed for Windows Desktop, you need to deploy .NET assemblies, but not MONO or .NET CF. If your application is based on .NET 4.0, then there's no need to use .NET 2.0 assemblies. If you developed the application for Windows Phone, then you only need Windows Phone assemblies.

Discuss this help topic in SecureBlackbox Forum