There are two files for the NumericInputBox.
  1. TnTinMn.NIB.dll
  2. TnTinMn.NIB.Design.dll

The first is the control itself and the second provides the design-time support for the control.  Only TnTinMn.NIB.dll needs to be packaged with your project to provide the functionality as their is no need for design-time support for the the run-time environment.

I recommend that the files be placed together in a directory where you store your custom controls.  This folder may be placed anywhere on your system.

The control is designed to be added to the Visual Studio toolbox.  Depending on your system’s configuration, the control will either appear under the .Net controls tab or your will need to select the browse option to add it to the Toolbox.

I personally like to the registry method for referencing custom controls as described in the documentation at:

This  following is an except from this link describing the method.

Set a registry key that specifies the location of assemblies to display:

For a 32-bit operating system, add one of the following registry keys.



For a 64-bit operating system, add one of the following registry keys in a 32-bit registry hive.



VersionMinimum is the lowest .NET Framework version that applies. If VersionMinimum is v3.0, folders specified in AssemblyFoldersEx apply to projects that target .NET Framework 3.0 and later.

When using the above method, please note the following items.

  1. The main registry path “.NETFramework” may not exist.  Note that the key name begins with a period (.).


  2. “AssemblyLocation” is the folder path terminated with a final backslash (\). i.e.: D:\My Documents\VS Custom Controls\

The files supplied with this project were compiled to target the .Net 3.5 version and will work with higher versions.

The designer library requires the full .Net version where-as the control itself was compiled against the .Net 3.5 Client version.  Therefore, you may target the Client framework in your projects.

Do not place both files in the “PublicAssemblies” folder as doing so will cause multiple versions of the control to to loaded into Visual Studio and cause a failure in the code generation.

i.e.: C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\PublicAssemblies

[Back to Documentation]

Last edited Feb 21, 2013 at 1:59 AM by TnTInMN, version 9


No comments yet.