ProEssentials WinForm interfaces are used when creating stand-alone client-side EXEs to be distributed and ran on an end-users machine.

Thank you for reading this and above FAQ section as it will speed your development and maximize your implementation's overall quality. Knowing our demo and demo project will be your best source of info.

More helpful info can be found here .NET Overview

Walk-Through:

1) Start Visual Studio.NET and create a new project targeting a [Windows Application] using Visual Basic as your language. Accept the default name of [WindowsApplication1].

Note: Under the Project menu, select "Project Properties". From the Compile tab, select the "Advanced Compile Options..." button. Change the "Target CPU" setting to x86. This is necessary as the following ProEssentials assembly links to a native 32 bit DLL. This setting will allow the resulting exe to run on both 32 and 64 bit systems and provide the easiest deployment. 

2) When the new project opens, you will be presented the design view of "Form1.vb".

If you have already installed the ProEssentials WinForm interfaces, skip to step 4.

Form1.vb [Design]...

Adding ProEssentials to a Form...

4) Double click the [Pego] tool within the toolbox. This places an instance of the Pego component within "Form1.vb". Left click bottom-right corner of control and drag down-right to fill up client area of Form1. The adjacent image shows what you see.   This represents the default state of a ProEssentials Graph. The default state has one subset with four data points. In the course of constructing your own charts, you'll set the properties PeData.Subsets and PeData.Points which define the quantity of data your chart will hold. You'll then pass data via the PeData.Y(subset, point) two dimensional property array. The following section shows example code of passing data.   ProEssentials uses the terms Subsets and Points but you can think of these as Rows and Columns. Passing data is as simple as filling each Subset with Points worth of data.

Adjusting design time settings...

5) Note, when setting color and font size attributes, we recommend setting the parent Form's versions as ProEssentials will use the parent form's settings to help facilitate a uniform look among sibling controls. If new to Visual Basic, the (Name) property is probably the most fundamental property as its name is reflected in all code. For example,  Pego1.PeData.Subsets = 1 is a line of code, and it shows how the (Name) property (Pego1) starts the line.

6) Double click Form1's Title/Caption Bar to open the code view for "Form1.vb" with default Form1_Load event initialized.

The cursor will be within the Form1_Load code section, enter the following code into this section.

You can copy and paste, but hand-typing a few lines of this code will really help familiarize yourself with the Gigasoft.ProEssentials namespace.  

Note: adding the following Imports declaration at the top of "Form1.vb" will shorten enumeration syntax.

Imports Gigasoft.ProEssentials.Enums

7) The code above enabled the DataHotSpot event, so we should place some appropriate code in the DataHotSpot event.

Within the two drop-down combo boxes at top of code view window, select [Pego1] within the left combo box. Select [PeDataHotSpot] within the right combo box.  The cursor should be within the Pego1_PeDataHotSpot event.  Or see the red annotations in the bitmap below to add the hot spot event.

Add the following code to the Pego1_PeDataHotSpot event.

The "Form1.vb" code window should contain...

8) Save and run the project. Your project will show an image as follows. Move the mouse over a bar and click to trigger the DataHotSpot event.

This completes this walkthrough.

Please read the remaining sections within Chapter 2 and review the demo code and documentation that's installed with the eval/product.

Once installed, the demo program can be accessed via shortcut...

Start / All Programs / ProEssentials v10 / PEDemo

Note that our main demo is replicated in VB.NET, C#.NET,  WPF, and MFC projects all accessible from the start menu. These are great for modifying an existing demo to test potential modifications before implementing within your applications.