Important note about installed version

This section of the documentation applies to the full purchased version only: the trial version of the component comes with an internal protection schema against fraudulent uses which will reset properties of 3D buttons and will turn them into black or gray rectangles when the component is redistributed outside of the development machine where the trial version was originally installed through the provided setup program.

Important note about the folder chosen for installing our files

In order to avoid the "DLL Hell" problem, it's strongly recommended that you install the mentioned files into the same folder in which you will install the EXE of your container application on the target system and not inside the Windows\System32 or Windows\SysWOW64 folders.

Important update regarding the assembly naming convention for Ctl3dMagic components for users of versions prior to 3.5

As part of our commitment to improving performance and streamlining long-term maintenance, starting from version 3.5 we are updating the naming convention of our .NET modern assemblies (for .NET Core 3.1, .NET 5 and higher versions).

Previously, each version of our component carried a specific suffix linked to the target framework (e.g., Ctl3dMagicCore3.dll, Ctl3dMagicF5.dll, Ctl3dMagicF6.dll). To eliminate version fragmentation and adopt Microsoft's best practices, we are consolidating all modern .NET versions (from .NET Core 3.1 up to .NET 10) into a single, unified file name: Ctl3dMagicNet.dll.

How this affects you and your backward compatibility:
We understand that maintaining backward compatibility is critical for your existing projects. We want to reassure you that no code changes or logic rewrites are required. Because modern .NET runtimes feature excellent forward compatibility, the new Ctl3dMagicNet.dll remains fully compatible with your older environments.

If you added the reference to the assembly by adding the component's NuGet package through the "NuGet Package Manager", you simply need to update the package to its latest available version installed through our setup program.

If you manually added the previous version of the assembly as a reference to your project, without using the NuGet package, in order to transition your existing project to the new release without losing compatibility, you will only need to perform a brief, one-time manual adjustment:

The benefit for your future updates:
By making this one-time switch to the unified naming convention, you will never have to break or update your references again. Future updates of our component will seamlessly overwrite the library, allowing your projects to upgrade smoothly via a simple rebuild.