ReadMe Version 11

Information about the new VDF version 11

All VectorDraw Developers Framework annual subscribers are eligible to download and use version 11.

The customers that are upgrading the VDF components from older versions to this new version 11, need to pay attention to the information below:  

1)The new Version 11 requires a new serial to work. The old serials are still valid for VDF version 10.x and previous. Please contact our sales dpt (sales@vdraw.com) in order to acquire your new serial for version 11.
The developer should not un-Authorize his version 10.x (or prior) serial, just authorize his dev. machine with the new provided version 11 serial using the new vdLic.exe application (see 2 below) that can be downloaded from our website. The machine will have both authorizations so the client will be able to switch his machine from version 11 to version 10  (and prior) and vice versa  (by uninstalling/installing VDF setups) without the need of using vdAuthorizeApp.exe every time.

2) vdAuthorizeApp.exe and vdLic.exe that where used in versions 10.x and prior are substituted from a new vdLic.exe file that can authorize the machine (just like vdAuthorizeApp.exe) and also produce the key for their applications like old vdLic.exe. This new vdLic.exe will work only with version 11 and not for 10.x.
You can download the new vdLic from here.

3) The redistribution has minor changes from version 10.x, please check the new ReadMe_Redis.htm document for more information or the following links depending your environment
.NET
ActiveX/COM

4) VDF Developer's setup creates a VDRAWDEV system variable where the VDF dlls are installed. The vdlic.exe when downloaded from our web site must be placed inside the VDRAWDEV folder so the following PostBuild event "$(VDRAWDEV)vdlic.exe"  "$(TargetPath)"can find the vdlic.exe application.
If the setup has not been installed and the client downloads the vdlic.exe then he must run it once without parameters so the VDRAWDEV variable is created.

5) The application that the client will build will no longer work in the developer machine (Developer machine is the one that is VectorDraw authorized) if not a valid appname.vdlic file is created.
So, a .vdlic file must always be created for the application, even in the developer machine.
In version 10 and previously the application would always run in the developer machine and that was causing confusion when the application was distributed. Now in version 11 the developer must properly create a .vdlic file in the post build event, and this way he can check if the .vdlic file is correct, otherwise the application will either run as evaluation or not at all (in case that the evaluation days have passed).

6) For version 11 there are four packages of development libraries:
a) A setup for COM/ActiveX development that is similar to VDF 10.x. This can be use for COM/ActiveX developent and for .NET 2.0 and later frameworks. For COM/ActiveX it requires .NET 3.5 SP1 and is necessary to use the provided setup. Deployment is done with the provided Merge Modules (msm files) only. See the readm_redis.htm document.
b) a side by side (SxS) package for .NET 4.x and older frameworks (VS2015 and prior) that is similar to VDF 10.x. This can be used for .NET 2.0 and later frameworks. Deployment is done by using the SxS zip that is provided
c) a NUGET package for .NET 4.x and older frameworks that is similar to VDF 10.x. This can be used for VS2017 and later. There is also a NUGET package for this. Deployment is done by a simple copy.
d) a NUGET package for VS2017 and later enciroments that is .NET 6.0 and can be used in .NET 6.0 and later frameworks. There is also a NUGET package for this for VS2017 and later IDE. Deployment is done by a simple copy.