Getting Started

In this page you can learn what is included in Hypernova UI Components package, including the documentation, code samples, demonstration applications and the underlying Component assemblies / libraries themselves.
Additionally, you can also find out where to get the package from, and how to go about installing the pakcage locally so you use them in your applications.

For a list of the new features, bug fixes, and API changes, see the Hypernova release notes.

What is included in Hypernova .NET UI Components package?

Hypernova .NET UI Components package(s) includes:

  • Hypernova WinForms .NET Components
  • Hypernova WPF .NET Components
  • Demonstration applications across Hypernova WinForms and WPF .NET Components
  • Sample projects with full source code written in C# .NET, which is made available so it can be useful as your reference / example implementations of how to use the Components in your own projects

Where to get the Hypernova UI Components packages from?

Hypernova .NET packages can be downloaded from here: Binarymission Home.

Download and Setup the Hypernova .NET for use in your application

This section describes how to install Hypernova. It involves the following three steps:

  • Verify and install the minimum system requirements.
  • Download and extract the Hypernova package.
  • Reference and use the Hypernova .NET Assemblies in your Application(s).

Step 1: Verify and Install the Minimum System Requirements

Operating System

Hypernova is designed to run on any current mainstream releases of Windows Operating System including the Windows 10 or later.

It can also support running on earlier versions such as Microsoft Windows 8 desktop, Microsoft Windows 7 or the Windows Server platforms.

.NET Framework

Before you can use the Hypernova .NET Components, the following must be installed in the target system:

  • Microsoft .NET Framework 4.8 or greater
  • Microsoft Visual Studio 2019 or greater (Visual Studio 2022 recommended)

The minimum .NET Framework requirement above lines up with Microsoft's LTS (Long Term Support) supported .NET Framework builds policy.

Step 2: Ask for and get an evaluation license key

You can start to use and evaluate the evaluation build of the .NET assemblies provided in the download package straight after your download.

However, in order to use the example projects' source code, you will need an evaluation license key to extract them.

You can request the license key by sending an email to Support. Thereafter, you will receive to your email address a time-limited evaluation key which you can also use to extract the downloaded zip file which is evaluation-license key protected (as its password).

Step 3: Download and Extract the Hypernova Package

Download the package file

The latest build of Hypernova .NET Components package can be downloaded from Binarymission website.

Extract the package


Note

See Step 2 above for the password / license key to extract the example projects' source code downloaded zip file)

The download file is just a .zip file that directly contains the content, containing the .NET Controls, sample projects, et al. organised into various Control/Component specific folders.

There are no installers / setup to run. You can simply download the file and extract the contents directly to a desired folder of your choice, and it is ready to use.


Note

You may need to unblock the zip file in your machine

Just ensure that once you have downloaded the .zip file, you right-click on the file, click on the Properties context menu item, and at the bottom of the General tab page, you will find the section named Security. Ensure you tick the Unblock checkbox and then click Apply.


Without the above action, Windows OS may not allow the contents to work properly.

Step 4: Reference and Use the Hypernova .NET Assemblies in your Application(s)


Note

  • Customers, who have purhcased the license(s) to our produts, have access to the retail version of our NuGet packages for all of our .NET 6.0, 7.0 and 8.0 Components' assemblies.

  • Evaluating customers will need to directly reference the dll assemblies into their projects, like detailed below.

Once you have extracted the package to a desired folder (as per Step 3 above), you can now proceed to referencing any of the components from that extracted components folder as follows:

  • Browse / explore into extracted folder with Windows Explorer, and you will find a folder named WinForms (and WPF, if you had extracted the Full .NET package containing both WinForms and WPF components).
  • Inside the selected component type folder (either WinForms or WPF), you will find multiple sub-folders, one folder per .NET Component.
  • Each folder contains within it, the demo program(s) and also the corresponding .NET Component assembly files / .dll(s).
  • With your application project opened in Visual Studio instance, you can probably (for convenience), create a dedicated section in your Visual Studio (2019 / 2022) Toolbox for Binarymission Components.
  • Keep the Windows Explorer on top of the visual studio (with explorer sized to a smaller sized window), and directly drag-and-drop the desired .dll file(s) into the VS Toolbox's new section you have created (in step above). Note that it is not neccessary to create that dedicated section. You can drag-and-drop the .dll files into VS Toolbox wherever you want.

Note

Pretty much all of the .dll files can be dropped on to the VS Toolbox view, excepting some .dll files which host .NET Components (and not .NET Controls), such as these specific ones below, for example. They cannot be loaded into toolbox, since they are top-level .net components, and Visual studio will not allow them to be hosted inside toolbox session).

These are some of those specific components cannot go into the VS Toolbox, as VS hosts only .NET Controls into the Toolbox (not Components such as Form, etc.)

  • AlerttPopup
  • ModernChromeWindow
  • Menu
  • PostIt
  • SuperTooltip
  • Tooltips

Subject to the above, you should be able to drag-and-drop all of the other .dll files (from other sibling folders) into VS Toolbox, directly from explorer window.


Having said the above note, the .NET Components such as the above, can be used in your project, by directly referencing them into your projects, as mentioned below:

  • Expand your project node tree (in the Solution Explorer view)
  • Locate the References node
  • Right-click on the references node, and click on the Add Reference.. menu command
  • Click the Browse... button at the bottom
  • Now locate the sub-folder where you extracted the Components to (such as inside the C:\Program files (x86)\Binarymission - if that is where you got the Hypernova package extracted into)
  • Select the desired .dll file and click OK in that Browe file dialog of Visual Studio, to get that dll added into your project's references
  • Once you have done that, you can use the components as you will normally use any other .NET class, by creating instance of the classes available in those added components

That is all to it. Now you are all set to enjoy the components in your projects.