|
|
Rank: Newbie
Groups: Member
Joined: 6/12/2013
Posts: 8
|
EO.Pdf.Runtime.AddLicense( mykey)
Dim pdfFile As String = "c:\test.pdf"
Dim i As Integer = 0
Dim curFiles As System.IO.FileInfo() = Root.GetFiles("*.pdf")
Dim docs As PdfDocument() = New PdfDocument(curFiles.Count - 1) {}
For Each file As System.IO.FileInfo In curFiles
docs(i) = New PdfDocument(file.FullName)
i += 1
Next
Dim mergedoc As New PdfDocument
mergedoc = EO.Pdf.PdfDocument.Merge(docs)
mergedoc.Save(pdfFile)
Still get trail version message on pdf.
I installed the current version and using key provided this day.
What am I missing?
I cannot place the key in the global.ascx file. Can't it be placed in the page callback of the routine? Or must it be somewhere else?
Walt
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
Please check whether you indeed have the latest ---- we have just posted EO.Pdf 2013 yesterday night and your key is for that version. So if you have downloaded your version before yesterday night, then you have the older version, which does not match your key.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 6/12/2013
Posts: 8
|
Yes, It was purchased last night but the version of the control says 5.0.15.2 dated 6/12/2013 4:58PM not 2013.0.15
Are you sure you issued the correct key as I purchased about the same time you released.
Walt
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
That's the correct DLL. Version 5 = 2013. Also we have verified your key and it's correct. You can verify the key by inserting the AddLicense code to the Program.Main in the EOPdfDemo sample project at the beginning of the function. You will see that it removes the license banner.
The most common reason when the key does not work is that you called AddLicense too late. For example, if you use our ASPXToPDF and have this control in your page, then call AddLicense in your Page_Load, then it will be too late because at the time your Page_Load is called, ASPXToPDF control has already been created --- which means our library has already been called. The rule for AddLicense is that it must be called BEFORE anything else in our library. That's why we recommend you to call it inside Global class's Application_Start handler.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 6/12/2013
Posts: 8
|
I have reinstalled from the download this morning and used the key as shown. Still no joy.
Walt
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
Please follow the steps in our previous reply to verify your key with the demo app. If the demo app works and your app does not, then it's because you called AddLicense key too late. This is pretty much all that there is.
Thanks
|
|
Rank: Newbie
Groups: Member
Joined: 6/12/2013
Posts: 8
|
I have tried global.asax still unsuccessfull. This is a DNN module and I really can't install changes to global.asax, even so it does not work and this control is of little use to me with your message at the bottom.
Sample of the global.asax file.
<%@ Application Inherits="DotNetNuke.Web.Common.Internal.DotNetNukeHttpApplication" Language="C#" %>
<script runat="server">
void Application_Start(object sender, EventArgs e)
{
EO.Pdf.Runtime.AddLicense( "mykey");
}
</script>
|
|
Rank: Newbie
Groups: Member
Joined: 6/12/2013
Posts: 8
|
Yes it works on your demo for a windows form progam not web.
Walt
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
OK. We will have to modify our code to allow you to call AddLicense any time. We will provide you an update build later today.
Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
We have posted a new build that should solve this issue for you. Please see your private message for the download location.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 6/12/2013
Posts: 8
|
Tried in Global.asax again and in the page_init and still get the message. I don't know what's happening in the DNN Framework but your license scheme just doesn't work. How do I get a refund as your software works but your licenseing does not. I need to move on.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
Did you try the new build? We won't be able to issue a refund once the license key is disclosed, in fact you have to explicitly agree to this policy before you access the license key. The new build allows you to set license key anywhere --- so it's not possible that the license scheme won't work for you --- in fact our product has been on the market several years and you are the first one that reports the license scheme won't work. What we can do is, if you can provide remote access to your environment, we should be able to find it out for you right away. Or if you can produce a test app that can isolate the problem and send the test app to us, we will be able to find it for you as well.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 6/12/2013
Posts: 8
|
It doesn't work with the dnn Framework. I really don't care about the refund I just need a solution. You would have to have a dotnetnuke web install to test. I would be happy to provide a test module but you would have to have the portal already installed to test it (Free at Dotnetnuke.com). Let me know. All my sofwatre is web based not win forms. I like your software but your licensing scheme needs work.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Sure. Please provide test module to us and we will follow through on this. Usually we prefer to look into such issues in the client's environment directly because very often there are some subtle differences between the customers’ environment and ours that we do not know and we can not duplicate, such differences are usually what causes the problem, so we always ends up everything working fine in our environment. But if you can provide a test module and a brief summary of things/steps that you think we should know then we will be happy to try it here. From the product's point of view, there is really no real difference between a Web application and a Windows form application -- the only difference is the time when the license code is called, which can be an issue for the old build. But the new build eliminated this as well. In any case, as long as we can see the problem it should not be difficult for us to find out the root cause.
Please see your private message as to where to send the module.
Thanks!
|
|