|
|
Rank: Advanced Member
Groups: Member
Joined: 10/30/2017
Posts: 43
|
I am getting a message I need to buy the 2020 license. Did you change something on how the license is "added"? Let me give you some more context. The first time I upgraded I had to reconcile several of our programs. So I created a dll with two functions. One called the AddLicense function and the other returned a hardcode string of the year. That way I could print in the about form the dll version and the year to verify that the correct dll AddLicense dll is there. Did something change in 2020 that would make that technique not work any longer? When I upgraded to 2019, all I had to do is copy the new EO and my AddLicense dll's. Also, I was getting some compile errors, I notice there are two more dll than 2019, I guess some function/assemblies names changed?
Code: Visual Basic.NET
Imports EO.WebBrowser
Namespace VB_ClassLib
Public Class AddLicense
Public Shared Sub AddLicense()
'2020 License
EO.WebBrowser.Runtime.AddLicense(
"...")
End Sub
Public Shared Function LicenseYear() As String
Return "2020"
End Function
End Class
End Namespace
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Hi, We do adjust DLLs from time to time and we did do so in 2020 in order to provide better support for .NET Core. You can find exactly which DLL is needed here: https://www.essentialobjects.com/doc/common/refdll.aspxHowever this should not have anything to do with your license key and your license key applying technique is fine. If you are getting the license warning message, then it's because your AddLicense code is NOT called. So you will want to check that part instead. Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 10/30/2017
Posts: 43
|
eo_support wrote:
However, this should not have anything to do with your license key and your license key applying technique is fine. If you are getting the license warning message, then it's because your AddLicense code is NOT called. So you will want to check that part instead.
When adding the AddLicense to the code it seems to work.
Code: Visual Basic.NET
Public Sub New()
' This call is required by the designer.
InitializeComponent()
' Add any initialization after the InitializeComponent() call.
AddLicense.AddLicense()
'EO.WebBrowser.Runtime.AddLicense(
' ".....")
EO.Base.Runtime.EnableEOWP = True
End Sub
Here is an example of how I tested. After adding the EO AddLicense and remarking my, it did load. Now that I know it should work, let me go back with new confidence. Also when I went back to double-check the license string, it looks like it keeps changing. Does it change every time you inquire what the license string look like?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Hi,
Glad to hear that the license is working for you.
As to license key, it is very normal that every time you visit the page you will receive a different license key. This is because the license key is time stamped.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 10/30/2017
Posts: 43
|
eo_support wrote:As to license key, it is very normal that every time you visit the page you will receive a different license key. That makes sense. I was just trying to double check that I had the right key. Confused me at first. eo_support wrote:
Glad to hear that the license is working for you.
Actually my original problem is still there. What worked is adding the EO AddLicense to the code instead of running it from the DLL. BTW switching back to the 2019 version seems to work. I could try and create a Hello World example if that helps.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
You have a version mismatch somewhere. There should be no difference when EO.WebBrowser.Runtime.AddLicense is called directly, or from a separate DLL. The only case there can be a difference is when they are calling EO.WebBrowser.Runtime.AddLicense on different version of EO DLLs. For example, if your main project uses EO v2020 thus it needs AddLicense on v2020, but your DLL uses v2019 and calls EO.WebBrowser.Runtime.AddLicense on v2019, then this means it did not apply v2020 license key and you will get the license error.
Please double check the references and rebuild your DLLs. This should be something very simple and straight forward.
|
|