LogicNP Software Knowledge Base And FAQ

CryptoLicensing For ActiveX :: HOWTO: Use a single license service for multiple project files.

v2010 or later of CryptoLicensing supports using a single license service for multiple project files.

The license service settings file (named settings.xml by default and located in the App_Data folder) is simply an XML file which specifies which license project file to use when servicing requests (and the database connection string). Thus there is a one-to-one correspondence with the settings file and the license project file specified therein.

To use same license service for multiple project files, make a copy of the settings.xml file. You can then manually edit them to specify the license project file and database connection string or you can use the install/install.aspx page that comes with the license service.

Once the settings files are configured, loading the correct settings file when communicating with the license service works by using the CryptoLicense.LicenseServiceSettingsFilePath property: This property explicitly specifies the settings file to use when communicating with the license service. When this property is specified, the LicenseService.DefaultSettingsFilePath property (see note below)is ignored.

Example

You wish to use the same license service for two products: MyProduct1 and MyProduct2. In this case, the App_Data folder will contain the following files:

MyProduct1.ocxlicproj (the license project file for MyProduct1)
MyProduct2.ocxlicproj (the license project file for MyProduct2)
MyProduct1_settings.xml (the settings file for MyProduct1 which specifies the MyProduct1.ocxlicproj file above)
MyProduct2_settings.xml (the settings file for MyProduct2 which specifies the MyProduct2.ocxlicproj file above)

When validating licenses from MyProduct1, use the following code:

Code:

Code:

cryLic.ValidationKey="...";
cryLic.LicenseCode="...";
cryLic.LicenseServiceURL="...";
cryLic.LicenseServiceSettingsFilePath="%AppDomainAppPath%App_Data\MyProduct1_settings.xml";
if(cryLic.Status==LicenseStatus.LS_Valid)
{
...
...
}

When validating licenses from MyProduct2, use the following code:

Code:

Code:

cryLic.ValidationKey="...";
cryLic.LicenseCode="...";
cryLic.LicenseServiceURL="...";
cryLic.LicenseServiceSettingsFilePath="%AppDomainAppPath%App_Data\MyProduct2_settings.xml";
if(cryLic.Status==LicenseStatus.LS_Valid)
{
...
...
}

Note

LicenseService.DefaultSettingsFilePath property: When you create a new license service, the LicenseService.DefaultSettingsFilePath property is set to the path of the one and only settings.xml file created in the App-Data folder. This is the settings file that is used if no CryptoLicense.LicenseServiceSettingsFilePath property (see above) is specified.

CryptoLicensing For MFC :: HOWTO: Use a single license service for multiple project files.

v2010 or later of CryptoLicensing supports using a single license service for multiple project files.

The license service settings file (named settings.xml by default and located in the App_Data folder) is simply an XML file which specifies which license project file to use when servicing requests (and the database connection string). Thus there is a one-to-one correspondence with the settings file and the license project file specified therein.

To use same license service for multiple project files, make a copy of the settings.xml file. You can then manually edit them to specify the license project file and database connection string or you can use the install/install.aspx page that comes with the license service.

Once the settings files are configured, loading the correct settings file when communicating with the license service works by using the CryptoLicense.LicenseServiceSettingsFilePath property: This property explicitly specifies the settings file to use when communicating with the license service. When this property is specified, the LicenseService.DefaultSettingsFilePath property (see note below)is ignored.

Example

You wish to use the same license service for two products: MyProduct1 and MyProduct2. In this case, the App_Data folder will contain the following files:

MyProduct1.mfclicproj (the license project file for MyProduct1)
MyProduct2.mfclicproj (the license project file for MyProduct2)
MyProduct1_settings.xml (the settings file for MyProduct1 which specifies the MyProduct1.mfclicproj file above)
MyProduct2_settings.xml (the settings file for MyProduct2 which specifies the MyProduct2.mfclicproj file above)

When validating licenses from MyProduct1, use the following code:

Code:

Code:

cryLic.SetValidationKey(_T("..."));
cryLic.SetLicenseCode(_T("..."));
cryLic.SetLicenseServiceURL(_T("..."));
cryLic.SetLicenseServiceSettingsFilePath(_T("%AppDomainAppPath%App_Data\MyProduct1_settings.xml"));
if(cryLic->GetStatus()!=LS_Valid)
{
...
...
}

When validating licenses from MyProduct2, use the following code:

Code:

Code:

cryLic.SetValidationKey(_T("..."));
cryLic.SetLicenseCode(_T("..."));
cryLic.SetLicenseServiceURL(_T("..."));
cryLic.SetLicenseServiceSettingsFilePath(_T("%AppDomainAppPath%App_Data\MyProduct2_settings.xml"));
if(cryLic->GetStatus()!=LS_Valid)
{
...
...
}

CryptoLicensing For .Net :: HOWTO: Use a single license service for multiple project files.

v2010 or later of CryptoLicensing supports using a single license service for multiple project files.

The license service settings file (named settings.xml by default and located in the App_Data folder) is simply an XML file which specifies which license project file to use when servicing requests (and the database connection string). Thus there is a one-to-one correspondence with the settings file and the license project file specified therein.

To use same license service for multiple project files, make a copy of the settings.xml file. You can then manually edit them to specify the license project file and database connection string or you can use the install/install.aspx page that comes with the license service.

Once the settings files are configured, loading the correct settings file when communicating with the license service works by using the CryptoLicense.LicenseServiceSettingsFilePath property: This property explicitly specifies the settings file to use when communicating with the license service. When this property is specified, the LicenseService.DefaultSettingsFilePath property (see note below)is ignored.

Example

You wish to use the same license service for two products: MyProduct1 and MyProduct2. In this case, the App_Data folder will contain the following files:

MyProduct1.netlicproj (the license project file for MyProduct1)
MyProduct2.netlicproj (the license project file for MyProduct2)
MyProduct1_settings.xml (the settings file for MyProduct1 which specifies the MyProduct1.netlicproj file above)
MyProduct2_settings.xml (the settings file for MyProduct2 which specifies the MyProduct2.netlicproj file above)

When validating licenses from MyProduct1, use the following code:

Code:

When validating licenses from MyProduct2, use the following code:

Code:

cryLic.ValidationKey="...";
cryLic.LicenseCode="...";
cryLic.LicenseServiceURL="...";
cryLic.LicenseServiceSettingsFilePath="%AppDomainAppPath%App_Data\MyProduct2_settings.xml";
if(cryLic.Status==LicenseStatus.Valid)
{
...
...
}

EZShellExtensionsMFC :: INFO: Basic trouble-shooting guide.

Extension not showing?

Does the sample extension(s) that come with the installation work?
If yes, then the issue is within your project. Continue reading below for other potential solutions.

Is the extension properly registered?
When you register the extension from the command line, do you get any error message?
For Vista or higher, also see INFO: Registering/unregistering and debugging shell extensions on Windows Vista or higher

Is the extension getting loaded?
You can test this by putting a MessageBox.Show in the constructor, then restart explorer, rebuild project and test your extension again.

Are any exceptions being thrown?
See INFO: Using debugging to track potential problems.

Extension not working as expected?

Is the corresponding functionality in our sample(s) working?
If so, there is probably some minor issue with your code. See the very useful topic 'Most common errors...' in the help file.

EZShellExtensionsMFC :: INFO: Using debugging to track potential problems.

Many times, certain functionality of your shell extension does not work due to coding issues. One way to determine the potential cause is to see if any exceptions are being raised/thrown. To do this, :

1. Under Project settings--> Debugging, specify Windows Explorer as the command (the typical path is "c:\windows\explorer.exe")

2. Under Debug Menu -->Exceptions, check 'Common Language Runtime Exceptions' and click OK.

3. Start the project under debug mode using F5. Windows Explorer will start running. If this does not work, start Windows Explorer externally (for example, by pressing the Windows+E key combination) and then attach to this Windows Explorer process (explorer.exe) using the 'Attach...' menu option from the 'Debug' menu in Visual Studio.

4. In Visual Studio, switch to the 'Output' tab where all diagnostic messages including exception information is displayed.

5. Browse the Windows Explorer and try to execute that functionality of the shell extension which is not working. If any exceptions are raised/thrown, information about the same will be shown in the 'Output' window. This information can be used to diagnose the possible cause of the problem, or the entire contents of the 'Output' window can be sent to technical support as a supporting document.

EZNamespaceExtensionsMFC :: INFO: Using debugging to track potential problems.

Many times, certain functionality of your namespace extension does not work due to coding issues. One way to determine the potential cause is to see if any exceptions are being raised/thrown. To do this, :

1. Under Project settings--> Debugging, specify Windows Explorer as the command (the typical path is "c:\windows\explorer.exe")

2.Under Debug Menu -->Exceptions, check 'Common Language Runtime Exceptions' and click OK.

3. Start the project under debug mode using F5. Windows Explorer will start running. If this does not work, start Windows Explorer externally (for example, by pressing the Windows+E key combination) and then attach to this Windows Explorer process (explorer.exe) using the 'Attach...' menu option from the 'Debug' menu in Visual Studio.

4. In Visual Studio, switch to the 'Output' tab where all diagnostic messages including exception information is displayed.

5. Browse to your namespace extension in the Windows Explorer and try to execute that functionality of the namespace extension which is not working. If any exceptions are raised/thrown, information about the same will be shown in the 'Output' window. This information can be used to diagnose the possible cause of the problem, or the entire contents of the 'Output' window can be sent to technical support as a supporting document.

EZNamespaceExtensionsMFC :: INFO: Basic trouble-shooting guide.

Extension not showing?

Does the sample extension(s) that come with the installation work?
If yes, then the issue is within your project. Continue reading below for other potential solutions.

Is the extension properly registered?
When you register the extension from the command line, do you get any error message?
For Vista or higher, also see INFO: Registering/unregistering and debugging namespace extensions on Windows Vista or higher

Is the extension getting loaded?
You can test this by putting a MessageBox.Show in the constructor, then restart explorer, rebuild project and test your extension again.

Are any exceptions being thrown?
See INFO: Using debugging to track potential problems.

Using Windows 7?
By default, a namespace extension will not show in the tree view (left side) of Windows Explorer. See INFO: Display namespace extension in the tree view (left side) of Windows Explorer in Windows 7

Extension not working as expected?

Is the corresponding functionality in our sample(s) working?
If so, there is probably some minor issue with your code. See the very useful topic 'Most common errors...' in the help file.

EZShellExtensions.Net :: INFO: Basic trouble-shooting guide.

EZNamespaceExtensions.Net :: INFO: Basic trouble-shooting guide.

Extension not showing?

Does the sample extension(s) that come with the installation work?
If yes, then the issue is within your project. Continue reading below for other potential solutions.

Is the extension properly registered?
When you register the extension from the command line, do you get any error message?
For Vista or higher, also see INFO: Registering/unregistering and debugging namespace extensions on Windows Vista or higher

Is the extension getting loaded?
You can test this by putting a MessageBox.Show in the constructor, then restart explorer, rebuild project and test your extension again.

Are any exceptions being thrown?
See INFO: Using debugging to track potential problems.

Using Windows 7?
By default, a namespace extension will not show in the tree view (left side) of Windows Explorer. See INFO: Display namespace extension in the tree view (left side) of Windows Explorer in Windows 7

Extension not working as expected?

Is the corresponding functionality in our sample(s) working?
If so, there is probably some minor issue with your code. See the very useful topic 'Most common errors...' in the help file.

EZShellExtensions.Net :: HOWTO: Target a context menu extension for 'My Computer' or other special folders

To target a context menu extension for 'My Computer' or other special folders, use the following code:

Code:

[Guid("B084EEB5-C144-4006-A7C3-8DB4ED46C54B"), ComVisible(true)]
[TargetExtension(SpecialProgIDTargets.AllFolders, false)]
public class RegisterExtensionCtxExt : ContextMenuExtension
{
public RegisterExtensionCtxExt()
{
}

protected override bool OnInitializeEx(LogicNP.EZShellExtensions.Interop.IOleDataObject dataObject)
{
// Get PIDL of folder for which context menu is being shown
IntPtr[] pidls = Utils.GetPIDLListFromDataObject(dataObject);

// Get PIDL of 'My Computer'
IntPtr myComp = Utils.GetSpecialFolderPIDL(SpecialFolders.DRIVES);

// Only enable the extension for 'My Computer'
if (Utils.PIDLCompare(pidls[0], myComp) == 0)
return true;
else
return false;

}

protected override void OnGetMenuItems(LogicNP.EZShellExtensions.GetMenuitemsEventArgs e)
{
// Add our menu items
e.Menu.AddItem("MyMenuItem", "MyMenuItem", "MyMenuItem");
}

protected override bool OnExecuteMenuItem(LogicNP.EZShellExtensions.ExecuteItemEventArgs e)
{
if (e.MenuItem.Verb == "MyMenuItem")
{
// Simply display the verb
MessageBox.Show(e.MenuItem.Verb);
return true;
}
// MUST return false if called for other verbs
return false;
}

[ComRegisterFunction]
public static void Register(System.Type t)
{
ContextMenuExtension.RegisterExtension(typeof(RegisterExtensionCtxExt));
}

[ComUnregisterFunction]
public static void UnRegister(System.Type t)
{
ContextMenuExtension.UnRegisterExtension(typeof(RegisterExtensionCtxExt));
}
}

Note

To target other special folders, use the appropriate SpecialFolders.XXXX enum in the OnInitializeEx method above.

EZNamespaceExtensionsMFC :: INFO: Display namespace extension in the tree view (left side) of Windows Explorer in Windows 7

By default, Windows 7 does not show the root node of a namespace extension in the tree view (left side) of Windows Explorer. It does show it in the list view (left side).
To display it in the tree view, you need to specify a per-computer setting as follows :

1. In Windows Explorer, press Alt key to display the menu bar. Then select Tools menu --> Folder Options...
2. Check 'Show All Folders' in the General tab.
3. Click OK.

EZNamespaceExtensions.Net :: INFO: Display namespace extension in the tree view (left side) of Windows Explorer in Windows 7

FileView.Net/WPF :: HOWTO : Add custom columns in Report mode.

You should use the AddCustomColumn method. You can set the column text for individual items by using the GetColumnText method of ListItem in the AfterItemAdd event or anytime after that.

CryptoLicensing For ActiveX :: HOWTO: Transfer machine-locked licenses manually from one machine to another machine

When you cannot host a license service, you need to manually transfer a machine-locked license from one machine to another. To do this, perform the following steps:

1. In your software, use the CCryptoLicense.DeactivateLocally method to deactivate the license from the first machine. This method will return a deactivation code. Display this code to the user and allow him to copy it so that he/she can send it to you in step 3 below.

2. On the new machine, in your software, use the CCryptoLicense.GetLocalMachineCodeAsString method; display the return value of this method (machine code of the new machine) to the user and allow him to copy it so that he/she can send it to you in step 3 below.

3. Have the customer send the deactivation code and the new machine code to you (via email or by some other means).

4. In the CryptoLicensing Generator App, input the deactivation code in the bottom text box, then click on the dropdown part of the 'Validate' button and click the 'Validate Deactivation Code' menu item. If the specified deactivation code is valid, this means that the customer has actually and successfully deactivated the license from the old machine.

5. Now check the 'Lock To Machine' check box and specify the machine code of the new machine that the customer sent you. Then click 'Generate' to generate a new license machine-locked to the new machine. Send this to the customer to use on the new machine.

Note
You can use the CryptoLicensing Generator API to automate your part of the tasks (Steps 4 and 5). Use the CryptoLicenseGenerator.ValidateDeactivationCode method for Step 4 and the CryptoLicenseGenerator.Generate method (after specifying the new machine code via CryptoLicenseGenerator.MachineCode) for Step 5.

CryptoLicensing For MFC :: Transfer machine-locked licenses manually from one machine to another machine