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

Bump Castle.Core from 4.4.1 to 5.0.0 #28035

Merged
merged 2 commits into from
Jul 5, 2022

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 16, 2022

Bumps Castle.Core from 4.4.1 to 5.0.0.

Release notes

Sourced from Castle.Core's releases.

5.0.0

Enhancements

  • .NET 6.0 support (@​Jevonius, #616)
  • .NET Standard 2.0 and 2.1 support (@​lg2de, #485)
  • Non-intercepted methods on a class proxy with target are now forwarded to the target (@​stakx, #571)
  • Significant performance improvements with proxy type generation for interface proxies without target. Up until now, DynamicProxy generated a separate IInvocation implementation type for every single proxied method – it is now able to reuse a single predefined type in many cases, thereby reducing the total amount of dynamic type generation. (@​stakx, #573)

Bugfixes

  • Generic method with differently named generic arguments to parent throws KeyNotFoundException (@​stakx, #106)
  • Proxying certain [Serializable] classes produces proxy types that fail PEVerify test (@​stakx, #367)
  • private protected methods are not intercepted (@​CrispyDrone, #535)
  • System.UIntPtr unsupported (@​stakx, #546)
  • DynamicProxy generates two modules when proceeding from a class proxy's protected method to the target, causing an InvalidOperationException when saving the generated assembly to disk (@​stakx, #569)
  • Upgrade log4net to v2.0.13 (@​jonorossi, @​stakx, @​dschwartzni, #574, #605)

Deprecations

  • Removed support for the .NET Framework < 4.6.2 and .NET Standard 1.x. (@​stakx, #495, #496; @​Jevonius, #614)
  • Removed support for Code Access Security (CAS). (@​stakx, #502)
  • Removed support for Remoting. This library no longer defines any types deriving from MarshalByRefObject, and ProxyUtil.IsProxy (which used to recognize remoting/"transparent" proxies) now tests only for DynamicProxy proxies. (@​stakx, #507)
  • The following public members have been removed:
    • Castle.Core.Internal.CollectionExtensions (class)
    • Castle.Core.Internal.Lock (class) along with all related types and methods
    • Castle.Core.Internal.PermissionUtil.IsGranted (method)
    • Castle.Core.Pair<,> (type). Use System.ValueTuple<,> or System.Tuple<,> instead.
    • all type members in Castle.DynamicProxy.ModuleScope that gave direct access to DynamicProxy's type cache and ModuleBuilders. Only SaveAssembly, LoadAssemblyIntoCache, and members supporting these two facilities are left public.
    • almost all types and type members in the Castle.DynamicProxy.* sub-namespaces, as most of them are intended for internal use only.
    • DynamicProxy's custom exception types have been replaced by standard BCL exceptions (where appropriate), and by a single DynamicProxyException type for internal DynamicProxy errors.

5.0.0-beta001

Full release notes will be available in the future.

Changelog

Sourced from Castle.Core's changelog.

5.0.0 (2022-05-11)

Enhancements:

  • .NET 6.0 support (@​Jevonius, #616)
  • .NET Standard 2.0 and 2.1 support (@​lg2de, #485)
  • Non-intercepted methods on a class proxy with target are now forwarded to the target (@​stakx, #571)
  • Significant performance improvements with proxy type generation for interface proxies without target. Up until now, DynamicProxy generated a separate IInvocation implementation type for every single proxied method – it is now able to reuse a single predefined type in many cases, thereby reducing the total amount of dynamic type generation. (@​stakx, #573)

Bugfixes:

  • Generic method with differently named generic arguments to parent throws KeyNotFoundException (@​stakx, #106)
  • Proxying certain [Serializable] classes produces proxy types that fail PEVerify test (@​stakx, #367)
  • private protected methods are not intercepted (@​CrispyDrone, #535)
  • System.UIntPtr unsupported (@​stakx, #546)
  • DynamicProxy generates two modules when proceeding from a class proxy's protected method to the target, causing an InvalidOperationException when saving the generated assembly to disk (@​stakx, #569)
  • Upgrade log4net to v2.0.13 (@​jonorossi, @​stakx, @​dschwartzni, #574, #605)

Deprecations:

  • Removed support for the .NET Framework < 4.6.2 and .NET Standard 1.x. (@​stakx, #495, #496; @​Jevonius, #614)
  • Removed support for Code Access Security (CAS). (@​stakx, #502)
  • Removed support for Remoting. This library no longer defines any types deriving from MarshalByRefObject, and ProxyUtil.IsProxy (which used to recognize remoting/"transparent" proxies) now tests only for DynamicProxy proxies. (@​stakx, #507)
  • The following public members have been removed:
    • Castle.Core.Internal.CollectionExtensions (class)
    • Castle.Core.Internal.Lock (class) along with all related types and methods
    • Castle.Core.Internal.PermissionUtil.IsGranted (method)
    • Castle.Core.Pair<,> (type). Use System.ValueTuple<,> or System.Tuple<,> instead.
    • all type members in Castle.DynamicProxy.ModuleScope that gave direct access to DynamicProxy's type cache and ModuleBuilders. Only SaveAssembly, LoadAssemblyIntoCache, and members supporting these two facilities are left public.
    • almost all types and type members in the Castle.DynamicProxy.* sub-namespaces, as most of them are intended for internal use only.
    • DynamicProxy's custom exception types have been replaced by standard BCL exceptions (where appropriate), and by a single DynamicProxyException type for internal DynamicProxy errors.
Commits
  • 652a250 Update changelog
  • 773ed6b Update changelog for 5.0.0 release
  • f49b72a Readme: Update conditional compilation symbols
  • 51f4f92 Merge pull request #616 from Jevonius/add-net6-targets
  • 0076083 Switch to preprocessor directives to avoid need for System.Runtime.InteropSer...
  • 9da21a7 Switch SYSLIB0003 suppression to pragma rather than project-level
  • 2de4707 Update CHANGELOG and README to reflect net6.0 change
  • 3e6e22d Remove references of DOTNET462 as no longer used
  • 8641c5f Update missed copyright header year for changed test file
  • 14264bc Update PublicApiTestCase platform filtering to use NUnit attribute
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dougbu
Copy link
Member

dougbu commented May 16, 2022

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@dougbu
Copy link
Member

dougbu commented May 16, 2022

@bricelam now failing due to breaking changes. Over to you…

D:\a\_work\1\s\test\EFCore.Proxies.Tests\ProxyTests.cs(209,23): error CS0246: The type or namespace name 'GeneratorException' could not be found (are you missing a using directive or an assembly reference?) [D:\a\_work\1\s\test\EFCore.Proxies.Tests\EFCore.Proxies.Tests.csproj]
D:\a\_work\1\s\test\EFCore.Proxies.Tests\ProxyTests.cs(216,23): error CS0246: The type or namespace name 'InvalidProxyConstructorArgumentsException' could not be found (are you missing a using directive or an assembly reference?) [D:\a\_work\1\s\test\EFCore.Proxies.Tests\EFCore.Proxies.Tests.csproj]
D:\a\_work\1\s\test\EFCore.Proxies.Tests\ProxyTests.cs(223,23): error CS0246: The type or namespace name 'InvalidProxyConstructorArgumentsException' could not be found (are you missing a using directive or an assembly reference?) [D:\a\_work\1\s\test\EFCore.Proxies.Tests\EFCore.Proxies.Tests.csproj]
D:\a\_work\1\s\test\EFCore.Proxies.Tests\ProxyTests.cs(230,23): error CS0246: The type or namespace name 'InvalidProxyConstructorArgumentsException' could not be found (are you missing a using directive or an assembly reference?) [D:\a\_work\1\s\test\EFCore.Proxies.Tests\EFCore.Proxies.Tests.csproj]

dependabot bot and others added 2 commits July 5, 2022 21:30
Bumps [Castle.Core](https://github.com/castleproject/Core) from 4.4.1 to 5.0.0.
- [Release notes](https://github.com/castleproject/Core/releases)
- [Changelog](https://github.com/castleproject/Core/blob/master/CHANGELOG.md)
- [Commits](castleproject/Core@v4.4.1...v5.0.0)

---
updated-dependencies:
- dependency-name: Castle.Core
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@ajcvickers ajcvickers force-pushed the dependabot/nuget/Castle.Core-5.0.0 branch from 22cffbc to 2897911 Compare July 5, 2022 20:39
@ajcvickers ajcvickers merged commit b417140 into main Jul 5, 2022
@ajcvickers ajcvickers deleted the dependabot/nuget/Castle.Core-5.0.0 branch July 5, 2022 22:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants