Bump Autofac from 6.2.0 to 7.0.0

[dependabot]

Bumps Autofac from 6.2.0 to 7.0.0.

Release notes

Sourced from Autofac's releases.

v7.0.0

What's Changed

• Add documentation links to common exceptions by @​tillig in autofac/Autofac#1359
• Fix #1360: Unify the "no constructors found" reporting by @​tillig in autofac/Autofac#1362
• Add support for required properties by @​alistairjevans in autofac/Autofac#1364
• Mark RegisterGeneratedFactory obsolete by @​tillig in autofac/Autofac#1366
• Isolate service information computed in child scopes from the parent scope by @​alistairjevans in autofac/Autofac#1350

Full Changelog: autofac/Autofac@v6.5.0...v7.0.0

v6.5.0

• Reflection caches have moved to a central location Autofac.Core.ReflectionCacheSet (#1341). This is part of an effort to support unloading AssemblyLoadContexts associated with child scopes and enable better plugin support (#1324).
• IDecoratorContext now extends IComponentContext so decorator decisions can be made based on the constructed container (#1338, #1352).
• Fix memory leak regression (#1353 - Thanks @​botinko!)

Full Changelog: autofac/Autofac@v6.4.0...v6.5.0

v6.4.0

• Fix typos in exception messages (#1301, #1302, #1323)
• Enable open generic assembly scanning to use WithMetadata and generate metadata (#1299 - thanks @​romerod!)
• Package targets .NET 6 TFM (#1306)
• README included in NuGet package (#1295, #1308)
• Symbols published in .snupkg format (#995, #1309)
• Fix issue where changing type parameter names caused generic resolution to fail (#1315, #1316)
• Added generic delegates to make registering lambda components easier (#1320, #1321)
• Optimization of reflection activation for components that only have one constructor - specifically, if there is only one constructor on a component, that constructor is cached as the one for activation and IConstructorSelector invocation is skipped (#1325)

The new feature to be aware of here is the generic delegates for making lambda registrations easier (#1320, #1321). It makes resolving dependencies in lambdas more straightforward.

The old way meant injecting an IComponentContext and resolving the dependencies manually.

builder.Register(
  ctx =>
  {
    var dep1 = ctx.Resolve<IDependency1>();
    var dep2 = ctx.Resolve<IDependency2>();
    return new Component(dep1, dep2, "configuration-value");
  });

That old way still works and is not deprecated. You can keep doing that.

However, you can now skip the manual resolutions and just provide the dependencies as the parameters to the lambda:

builder.Register(
  (IDependency dep1, IDependency dep2) =>
    new Component(dep1, dep2, "configuration-value"));
</tr></table> 

... (truncated)

Commits

• 1910177 Merge pull request #1369 from autofac/feature/ignore-required-props-in-prop-a...
• 2f5418f Merge pull request #1370 from autofac/test/load-context-combined-enumerable-test
• 93c02c1 Enumerables in load context test
• 6f335e7 Ignore required properties in the default property selector.
• 3489ad3 Merge pull request #1368 from autofac/version-change-7.0
• 9bb7a0f Change appveyor version.
• f446abb Merge pull request #1350 from autofac/feature/do-not-retain-isolated-service-...
• 430e28b Added tests to prove unload works ok with modules and onactivated in the loop.
• 7a3aaee Factored duplicated logic into a TypeAssemblyReferenceProvider method.
• 6e00847 Switch to using <ReferenceOutputAssembly>false</> rather than changing the bu...
• Additional commits viewable in compare view

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)