|
|
Rank: Newbie
Groups: Member
Joined: 10/9/2017
Posts: 7
|
Do you have a release date for v.next? Will it include 64bit support? Which version of chromium will this support?
I'm being asked to do some 1st quarter estimating for our internal app (which uses the wpf browser)
thx much!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi,
The next version should be out very soon --- we are doing some final testing on it. As long as that passes it will be out.
The new version is based on Chromium V62. The browser engine will still run on 32 bit mode --- however this is mostly transparent to your application as your application can run in either 32 bit mode or 64 bit mode.
Putting the browser engine in 64 bit mode itself is not a huge issue. The issue is if we compile the browser engine is 64 bit mode, then it would not be able to run on 32 bit systems. However if we compile the browser engine in 32 bit mode, the same set of binary can run on both 32 bit and 64 bit systems, which would save our customers a lot of trouble.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 10/9/2017
Posts: 7
|
Hello EO_Support,
Beauty is in the eye of the beholder ;-) I would like to urge you to reconsider support for a 64 bit engine.
We have developed an internally used kiosk-like, multimedia app; which uses your component.
We have many content authors thru our organization, who are competing with each other, to
produce the most dazzling, multi-media rich, html5 content possible.
Issues arise when the content authors develop\test\debug against a 64 bit desktop Chrome browser... but when we try to run their content in our
in house, 32 bit webbrowser app - we see significant discrepancies in video\graphics performance.
Multi-media content that plays\displays smoothly in the 64 bit desktop Chrome, is sometimes jerky\choppy\slow in our app. This leads to a lot of
frustration, to say the least.
Microsoft has declared end-of-life for Win7 - At some point it would seem that you're holding back more people than you're helping, by sticking with a 32b only binary.
Anyway, it would be a big help in our situation. Thanks for your help, and consideration!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
I completely agree. It's always a balance act --- we are doing our best to strike the best balance among all our customers. While almost all PCs have 64 bit hardware now, many tablets are still on 32 bit hardware, which is a also a major segment that runs our product. I believe this is one of the reasons that Microsoft still offers 32 bit Windows 10. So we will be continuing monitoring the situation for now. The worst case we will have to 2 set of binaries in order to support x86 and x64.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi,
This is just to let you know that the new build is out. You can download it from our download page.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 10/9/2017
Posts: 7
|
Hello EO_Support,
Downloaded new version. Installed. Updated dll's in my app.
Getting error " A license key is provided but is not valid for this build. Each version uses a different license key...."
Obviously pretty self-explanatory - but just like to confirm this isn't an erroneous error condition?
Just purchased v2017 lic. 9/30 ish. Do I need a new lic for v2018?
thx much!
p.s. ReadMe file says its for .Net 2015; dunno if you want to update that
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Thanks for feedback on the read me file. As to the license, you would just need to revisit your license key page. You should see a new option allowing you download license key for the new version.
|
|