Author |
|
janeh Newbie
Joined: 28 September 2007
Online Status: Offline Posts: 1
|
Posted: 28 September 2007 at 9:57am | IP Logged
|
|
|
I have a few questions for you:
1. The sample code comes with the download are in 2003 VS format. That makes me to think what Framework you are using for the MailBee.NET dll.
2. In the sample code, The license property on Mailbee.ImapMail.Imap has to set every manually in the code. Is that the limitation of the trial download? When the license is purchased, I would assume we don't have to specify that anymore if we use your tool to set the license info in the registry. Is that a correct assumption?
3. For a paid license, what kind of support is expected?
Thanks for your help.
Jane H.
|
Back to Top |
|
|
Alex AfterLogic Support
Joined: 19 November 2003
Online Status: Offline Posts: 2206
|
Posted: 28 September 2007 at 10:19am | IP Logged
|
|
|
Code:
The sample code comes with the download are in 2003 VS format. That makes me to think what Framework you are using for the MailBee.NET dll. |
|
|
MailBee.NET.dll can be used with .NET 1.1 and above (2.0, etc). .NET 1.0 is not supported.
Code:
2. In the sample code, The license property on Mailbee.ImapMail.Imap has to set every manually in the code. |
|
|
The only difference between trial and permanent version is a key. There are no separate packages for both. You can set the key in the code, in the registry, in .config file regardless if you are using the software in trial or permanent mode.
If you are going to redistribute the software, the license key may not be placed into location visible to end user (such as .config file or the source code if the app is shipped as a source code). If your app is not shipped as a source code, you're free to put the key into the code. If not, you should use the utility to put it into the registry (in the registry, the key is stored in encoded form).
Quote:
3. For a paid license, what kind of support is expected? |
|
|
For now, it's free email and forum support.
Regards,
Alex
|
Back to Top |
|
|