01-20-2017, 12:12 AM
I am glad that adding references fixed the problems.
Adding the references is also described in the "DXEngine Quick start" guide that is available in the "Ab3d.DXEngine Help.chm" help file (installed into the same folder as Ab3d.DXEngine).
The reason for the differences between evaluation and commercial version is that the previous version of DXEngine installed SharpDX dlls into GAC, but the latest version of DXEngine do not do that any more.
When SharpDX dlls were in GAC, the compiler could get them when compiling your project.
The reason to not install SharpDX into GAC was that that there are two different versions of SharpDX with the same assembly version 2.6.3.0 - one for DirectX 11 and one for DirectX 11.1.
The core assemblies (Ab3d.DXEngine.dll and Ab3d.DXEngine.Wpf.dll) are still installed into GAC. In some cases this can make using the libraries easier.
But sometimes this can lead to some problems that are not very easy to resolved (also because of some unclear compiler errors). For example when the SpecificVersion is set to false (by default), the compiler can take the version from GAC instead of the version that you have explicitly specified with selecting the dll file.
Therefore I am thinking of removing the GAC installation from installers or at least uncheck GAC install by default.
One of the reasons why the assemblies were installed into GAC was also to make the sample project compile without user needed to fix the references. But this is not needed any more because a new CustomAction in the installer now updates the csproj fles and sets the correct paths to the references.
Adding the references is also described in the "DXEngine Quick start" guide that is available in the "Ab3d.DXEngine Help.chm" help file (installed into the same folder as Ab3d.DXEngine).
The reason for the differences between evaluation and commercial version is that the previous version of DXEngine installed SharpDX dlls into GAC, but the latest version of DXEngine do not do that any more.
When SharpDX dlls were in GAC, the compiler could get them when compiling your project.
The reason to not install SharpDX into GAC was that that there are two different versions of SharpDX with the same assembly version 2.6.3.0 - one for DirectX 11 and one for DirectX 11.1.
The core assemblies (Ab3d.DXEngine.dll and Ab3d.DXEngine.Wpf.dll) are still installed into GAC. In some cases this can make using the libraries easier.
But sometimes this can lead to some problems that are not very easy to resolved (also because of some unclear compiler errors). For example when the SpecificVersion is set to false (by default), the compiler can take the version from GAC instead of the version that you have explicitly specified with selecting the dll file.
Therefore I am thinking of removing the GAC installation from installers or at least uncheck GAC install by default.
One of the reasons why the assemblies were installed into GAC was also to make the sample project compile without user needed to fix the references. But this is not needed any more because a new CustomAction in the installer now updates the csproj fles and sets the correct paths to the references.
Andrej Benedik