<< Click to Display Table of Contents >> Navigation:  Code Virtualizer > FAQ > General > When I add some Code Virtualizer macros my application requires VirtualizerSDK.dll. I don't want to rely on that DLL, what can I do?

There are three ways to insert our protection macros in your application:

 

1) Via inline assembly: This method does not require VirtualizerSDK.dll

 

2) Via calling to a function in VirtualizerSDK.dll: This method links with VirtualizerSDK.dll

 

3) Via an external assembly module: This method does not require VirtualizerSDK.dll

 

When using Visual Studio or Embarcadero compilers, they accept "inline assembly" for 32-bit applications, so Code Virtualizer uses the inline assembly method to insert the protection macros. That is, for 32-bit applications, the linking with VirtualizerSDK.dll is not required, so your 32-bit application does not need the VirtualizerSDK.dll library to run.

 

When you compile for 64-bit, the protection macros are inserted via calling functions inside the VirtualizerSDK.dll, so that DLL is required for your unprotected application. In any case, when you protect your application with Code Virtualizer, the linking with VirtualizerSDK.dll is removed, so your protected application does not required the VirtualizerSDK.dll library to run.

 

In any case, the VirtualizerSDK.dll file is *not* required by your protected application.