Logo
My Account |  Site Map | Contact Us  
Welcome Guest Search | Active Topics | Sign In | Register

WebBrowser x64 build on nuget? Options
Stefan Koell
Posted: Monday, October 25, 2021 6:17:36 AM
Rank: Advanced Member
Groups: Member

Joined: 12/23/2013
Posts: 92
Hi,

I read this topic:
https://www.essentialobjects.com/doc/common/x64.aspx
and as far as I know, the nuget packages you post are x86 only. Is there any chance we get the x64 on nuget as well? Downloading the installer/package is quite cumbersome and makes the whole release pipeline much more complex and error prone as just using the correct nuget package.

Regards,
Stefan
eo_support
Posted: Monday, October 25, 2021 5:14:17 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 23,102
Hi,

We MAY switch our nuget packages to x64 build from x86 build. This is purely a logistic issue since currently we only have one set of nuget packages and it has to be either x86 or x64. If we post x86 there then people will be asking for x64, and if we post x64 build there then people will be asking for x86. Our current plan is eventually everything will be x64 build since newer Windows will no longer support x86.

Thanks!
Stefan Koell
Posted: Tuesday, October 26, 2021 4:57:50 AM
Rank: Advanced Member
Groups: Member

Joined: 12/23/2013
Posts: 92
I understand that users may still need the x86 version but what prevents you to post 2 packages?
For example:
1) switch the existing package to x64 and post a new package called "EO.WebBrowser.Legacy" for the x86 version
2) keep the current package and post a new package called "EO.WebBrowser.x64"
3) unlist the current package and post two new packages with the x86/x64 suffix

At least consider to include a nupkg in you installer for easier deployment in a private feed. Dealing with the DLLs is not very CI/CD friendly.

Regards,
Stefan
eo_support
Posted: Tuesday, October 26, 2021 11:52:37 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 23,102
We could have two nuget packages however the consideration is people use nuget because of its simplicity, and doubling the number of packages does not server that goal. Also considering everything will probably settle down on the x64 version soon, so adding another set of packages at this time does not seem to be a good choice. Including private nuget feed has also been considered but we decided against it due to the size of the packages.
Stefan Koell
Posted: Tuesday, October 26, 2021 1:06:57 PM
Rank: Advanced Member
Groups: Member

Joined: 12/23/2013
Posts: 92
I wasn't referring to a private feed provided by you. I was referring to my own private nuget feed. Having ready made nupkg for each platform included in your installer would make publishin the packages to MY feed much easier. You keep on talking about simplicity with your current approach and your plan to not improve the situation while actually increasing complexity for users like me who only deploy x64.

What I'm asking is nothing unique. In fact, all my 3rd party dependencies provide nupkg files and also provide everything on either the public nuget feed or a company nuget feed. Rebex, DevExpress, TightVNC, just to name a few...

Quite disappointing really. I hope you will reconsider...
eo_support
Posted: Tuesday, October 26, 2021 1:24:29 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 23,102
I get what you are saying. Our nupkg files are huge. That's why we decided against including them in the setup file.
Stefan Koell
Posted: Tuesday, October 26, 2021 1:30:02 PM
Rank: Advanced Member
Groups: Member

Joined: 12/23/2013
Posts: 92
That indeed is problematic. How about providing dedicated downloads for them - just like your dedicated download for the x64 installer. I would prefer to just refer to the correct package on nuget.org but for me it would also be ok to download the nupkg files and put it on my own feed.
Walden
Posted: Wednesday, November 10, 2021 5:18:05 PM
Rank: Member
Groups: Member

Joined: 3/18/2014
Posts: 11
I'm going to throw my support behind a new nuGet package for x64. In my case EO.Pdf.x64 not EO.WebBrowser.x64 but having the 64 bit version on nuGet greatly simplifies deployment pipelines. At worst, please make the .nuPkg available for us to host locally, but putting it on nuGet makes great amounts of sense.
eo_support
Posted: Wednesday, November 10, 2021 5:45:49 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 23,102
Hi,

We will be switching to x64 build as the "main" build from our next release cycle (2022) thus nuget will switch to x64 build by then as well. So this will no longer be an issue after that.

The trade off for this is the small percentage of users (around 2%) who are still using 32 bit Windows thus can only use 32 bit version. They can still request 32 bit builds from us but they would lose the convenience of nugget packages.

Thanks!
Stefan Koell
Posted: Thursday, November 11, 2021 4:31:29 AM
Rank: Advanced Member
Groups: Member

Joined: 12/23/2013
Posts: 92
That's great news! Looking forward to the next release cycle...


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.