Editions

Win32

• Professional software copy protection and licensing system for
• Windows 32bit
• applications (exe, dll, ocx...)

More info

.NET

• Professional software copy protection and licensing system for
• .NET & Windows 32bit
• applications (exe, dll, ocx...)

More info

Win64

• Professional software copy protection and licensing system for
• Windows 64bit
• applications (exe, dll, ocx...)

More info

.NET64

• Professional software copy protection and licensing system for
• x64 .NET & Windows 64bit
• applications (exe, dll, ocx...)

More info

Choosing Your PC Guard: A Simple Walkthrough

1. Welcome! Let's Find Your Perfect Fit

Welcome to PC Guard! Selecting the right edition for your software protection needs is a straightforward process. This guide will walk you through a simple decision path based on the type of application you are developing.

A key insight to keep in mind is this: All four PC Guard editions share the same core features and flexible licensing, so your choice is purely about matching the tool to your technology. This means applications you protect with different editions can share license information and even be activated with a single code, creating a seamless experience for your end-users.

2. The First Big Question: What Are You Building?

Your decision boils down to one primary question: "Are you developing a native Windows application or a .NET application?" Let's break down what each of these means to help you find your answer.

2.1. Native Windows Applications

A native Windows application contains compiled (unmanaged) code that runs directly on the operating system. If you're using a programming language like C++, VB, or Delphi, you are likely building a native application.

Based on your application's architecture, here is your choice:

• For 32-bit native Windows applications (which run on both 32-bit and 64-bit Windows), you need PC Guard for Win32.
• For 64-bit native Windows applications (which require a 64-bit Windows OS), you need PC Guard for Win64.

2.2. .NET Applications

A .NET application requires a .NET runtime (.NET Framework, .NET, or .NET Core) to run. It contains IL (intermediate language) code and is typically developed in languages like VB.NET, C#, or J#.

Based on your application's target platform, here is your choice:

• For 32-bit (x86/AnyCpu) .NET applications, you need PC Guard for .NET.
• For 64-bit (x64) .NET applications, you need PC Guard for .NET64.

While this is straightforward, the .NET editions include a powerful bonus feature for developers with diverse projects.

3. A Powerful Tip for Mixed Development

If you develop both native Windows and .NET applications, the .NET editions of PC Guard offer a significant advantage. They are the most versatile option because they can protect both application types.

• PC Guard for .NET also protects 32-bit native Windows applications.
• PC Guard for .NET64 also protects 64-bit native Windows applications.

Choosing the appropriate .NET edition can cover all your protection needs in a single tool.

But what if your application wasn't built with a standard programming tool, and you're not sure if it's a 32-bit, 64-bit, or even a .NET application?

4. Still Unsure? The Easiest Way to Find Out

If you are not certain about your application's type, there is a simple and definitive way to determine the correct PC Guard edition.

Here are the steps:

1. Download the demo version of PC Guard for Win32.
2. Try to protect your application with it.
3. If it works, PC Guard for Win32 is a suitable choice. If it fails, the demo will display a message telling you exactly which edition of PC Guard you need.

This simple test removes all guesswork and is the recommended first step if you are not sure what kind of application you have.

5. Your Decision at a Glance

To bring it all together, here is a quick-reference table summarizing which PC Guard edition you need based on your project.

With this guide, your choice is clear. You can now proceed confidently with the exact PC Guard edition built for your technology.