Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release Notification - 92.0.x #3740

Closed
11 tasks done
amaitland opened this issue Aug 10, 2021 · 5 comments
Closed
11 tasks done

Release Notification - 92.0.x #3740

amaitland opened this issue Aug 10, 2021 · 5 comments
Assignees
Milestone

Comments

@amaitland
Copy link
Member

amaitland commented Aug 10, 2021

Release 92.0.x-pre

  • Update to latest CEF build
  • Create release notes
  • Update DevTools client API
  • Create cefsharp/92 release branch
  • Release -pre packages to nuget.org

Release 92.0.x

  • Resolve remaining issues attached to 92 Milestone
  • Create release notes
  • Update General Usage API doc links
  • Update Issue Template CEF Sample application links
  • Generate new API Doc and upload to http://cefsharp.github.io/api/
  • Release 92.0.x packages to nuget.org

@amaitland amaitland added this to the 92.0.x milestone Aug 10, 2021
@amaitland amaitland self-assigned this Aug 10, 2021
@amaitland amaitland pinned this issue Aug 10, 2021
@amaitland
Copy link
Member Author

The 92.0.250-pre release packages are now on Nuget.org.

For the .Net 4.5.2 and above

These packages required Visual C++ 2015 or greater

For .Net Core 3.1/.Net 5.0

These packages required Visual C++ 2019

NOTE A minimum of .Net Core 3.1 is required (for .Net 3.0 which is no longer supported by Microsoft you'll need to use the older packages).


Known Issues

  • Older Non-SdkStyle projects (packages.config) when using VS2017 still have issues when opening a fresh checkout workaround I had attempted didn't work (details in Nuget Package Restructure #3319 (comment)). For now closing/opening the project will resolve the issue. A message is displayed to the build output log when the files weren't copied as expected.

Ijwhost.dll
To support C++/CLI libraries in .NET Core, ijwhost was created as a shim for finding and loading the runtime. All C++/CLI libraries are linked to this shim, such that ijwhost.dll is found/loaded when the C++/CLI library is loaded.

@amaitland
Copy link
Member Author

This release was delayed as unfortunately I have been sick again (my son seems to have brought every possible cold/flu home from daycare this winter).

It will likely only be a few days before the first official 92 release is available.

@amaitland
Copy link
Member Author

I accidentally made a mistake and tagged the latest release as 92.0.230 rather than 92.0.260, the release/tag have been deleted and a new set of packages is being created.

@amaitland
Copy link
Member Author

The 92.0.251 release packages were released to Nuget.org a few days ago.

For the .Net 4.5.2 and above

These packages required Visual C++ 2015 or greater

For .Net Core 3.1/.Net 5.0

These packages required Visual C++ 2019

NOTE A minimum of .Net Core 3.1 is required (for .Net 3.0 which is no longer supported by Microsoft you'll need to use the older packages).


Known Issues

  • Older Non-SdkStyle projects (packages.config) when using VS2017 still have issues when opening a fresh checkout workaround I had attempted didn't work (details in Nuget Package Restructure #3319 (comment)). For now closing/opening the project will resolve the issue. A message is displayed to the build output log when the files weren't copied as expected.

Ijwhost.dll
To support C++/CLI libraries in .NET Core, ijwhost was created as a shim for finding and loading the runtime. All C++/CLI libraries are linked to this shim, such that ijwhost.dll is found/loaded when the C++/CLI library is loaded.

@amaitland
Copy link
Member Author

The 92.0.260 release packages are now available on Nuget.org.

For the .Net 4.5.2 and above

These packages required Visual C++ 2015 or greater

For .Net Core 3.1/.Net 5.0

These packages required Visual C++ 2019

NOTE A minimum of .Net Core 3.1 is required (for .Net 3.0 which is no longer supported by Microsoft you'll need to use the older packages).


Known Issues

  • Older Non-SdkStyle projects (packages.config) when using VS2017 still have issues when opening a fresh checkout workaround I had attempted didn't work (details in Nuget Package Restructure #3319 (comment)). For now closing/opening the project will resolve the issue. A message is displayed to the build output log when the files weren't copied as expected.

Ijwhost.dll
To support C++/CLI libraries in .NET Core, ijwhost was created as a shim for finding and loading the runtime. All C++/CLI libraries are linked to this shim, such that ijwhost.dll is found/loaded when the C++/CLI library is loaded.

@amaitland amaitland unpinned this issue Aug 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant