GPA Logo   GPA Software Download FAQ

Should I download the nightly-build or the last released version?

The formal release is recommended for first-time users wanting to learn more about a GPA product. The nightly-build is for users who want to help test new features that are actively under development. The nightly-build may also be best for users that have experienced specific problems which have been fixed but are not yet included in the formal release. Once the nightly-build becomes a "release candidate", this version is the generally the preferred download. It has been tested to a limited degree and it includes all bug fixes and new features.

Do all GPA products have nightly-builds?

No. Currently, just the synchrophasor products have nightly-builds -- the Grid Solutions Framework, openPDC, substationSBG, PDQ Tracker, openHistorian, and SIEGate. See: Nightly Build Location Links.  While the source code stays up-to-date with each daily change for other GPA products, please contact us for access to the best install package to use as we're in the process of implementing new features in products not listed on the nightly-build site.

Do I need to download the source code to try out a GPA product?

No. Both release versions and the nightly-build include windows installers. You only need to download the source code if you want to contribute to the project or customize the solution.

Do I need an account on CodePlex to download product install packages?

No. In fact, the nightly-build install packages are not located on CodePlex. GPA hosts access this service directly.

Do I need software beyond what's included in the downloaded install package to make a product work?

All products require .NET 4.5 to be available on the host platform. Beyond that, it depends. For example, the openPDC is designed work with multiple databases including free ones like MySQL. However, openXDA requires MS SQL Server. These requirements are provided on the individual CodePlex sites for each product.

Do any GPA products include components that require me to buy a software license?

Only one project, openSEE, incorporates components (HighCharts) that may require the user to purchase a license. See the CodePlex site on openSEE for details. To insure that users properly license these components, they are not included in the product install package but must be acquired and installed by the user.

Why are some GPA products on both CodePlex and GitHub?

Most GPA products use CodePlex as their primary hosting repository. As a .NET development shop, GPA's software development tools integrate best with CodePlex. However, due to GitHub's popularity GPA has begun (1) using GitHub as the primary repository for some products (such as Broccoli-Sharp) as well as (2) mirroring release source code and install packages on GitHub as a way to make the source code more accessible.

What do I need if I want to customize and compile the code?

Microsoft Visual Studio 2012 or later (.NET 4.5 framework) will compile most code code. There are components that have other dependencies. For example, the installers require the WiX toolkit.

How can I keep my GPA software up to date?

On CodePlex you can subscribe to a range of notification services including the availability of new downloads. GPA offers service agreements where GPA will recommend and assist with the installation of updates to individual product libraries based on improvements and bug fixes.

Who can I contact if I have problems installing a GPA product?

Some products offer more installation help than others through documentation posted on CodePlex. In general, the more mature a product, the better documentation. GPA offers services to assist those that need help beyond what this documentation provides.

Is there a way to download all GPA products at once?

No. You must go to each CodePlex site individually.

How do I report a problem or a bug?

On both CodePlex and GitHub there are issue tracker systems. GPA reviews and addresses issues posted on both sites as we are able. We deeply appreciate all the feedback provided as users discover issues. Many, many product improvements have been made as a result of this feedback.