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 - 93.1.x #3780

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

Release Notification - 93.1.x #3780

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

Comments

@amaitland
Copy link
Member

amaitland commented Aug 29, 2021

Due to upstream changes this version will require that we update the minimum VC++ version from 2015 to 2019 see #3636 for details.

Release 93.1.x-pre

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

Release 93.1.x

  • Resolve remaining issues attached to 93 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 93.1.x packages to nuget.org
@amaitland amaitland self-assigned this Aug 29, 2021
@amaitland amaitland added this to the 93.1.x milestone Aug 29, 2021
@amaitland amaitland pinned this issue Aug 29, 2021
@amaitland amaitland mentioned this issue Aug 30, 2021
10 tasks
@amaitland
Copy link
Member Author

Looks like creating a release from commit a16f16d caused a problem. The Readme.md changes don't trigger a build as they are text only, so creating a release from the same commit also doesn't trigger a build.

I've had to delete the release and tag, update some xml doc to trigger a build and recreate the release.

@amaitland
Copy link
Member Author

The 93.1.110-pre release packages have been pushed to Nuget.org and should be available shortly.

All packages require Visual C++ 2019

For the .Net 4.5.2 and above

For .Net Core 3.1/.Net 5.0

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 93.1.111 release packages have been pushed to Nuget.org and should be available shortly.

All packages require Visual C++ 2019

For the .Net 4.5.2 and above

For .Net Core 3.1/.Net 5.0

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 93.1.140 release packages have been pushed to Nuget.org and should be available shortly.

All packages require Visual C++ 2019

For the .Net 4.5.2 and above

For .Net Core 3.1/.Net 5.0

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 CefSharp.Wpf.HwndHost is also available on Nuget.org. Designed as a drop in replacement for the CefSharp.Wpf control for those that want a native control (similar to using a WindowsFormsHost) that supports WPF Binding etc. Standard AirSpace issues apply.

@amaitland amaitland unpinned this issue Sep 20, 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