added support for .NETStandard1.3

[gdereese]

via upgrading Castle.Core dependency to >= 4.0.0-beta001

See issue #8

[tillig]

Have you tried consuming the .nupkg generated by this build in a netstandard 1.3 project? The reason I ask: If I create a new .csproj-based class library in VS and tell it to target a .NET standard, It adds a project.json file, sets <TargetFrameworkVersion>v5.0</TargetFrameworkVersion> in the .csproj, updates the ProjectTypeGuids node in the .csproj, and so on. If, instead, I tell it that I want it to be a portable project, I get a bunch of other changes in the .csproj to ensure it's targeting the right profile.

I'm curious if this is actually building an assembly that is truly netstandard 1.3 compatible or if it's just building a NuGet package that has a .NET 4.5.1 assembly in it that won't be correctly compatible if consumed.

[tillig]

Note that generally we've found that in order to target a netstandard platform you have to switch the whole project to use the dotnet CLI, use the same build as Autofac core (with the PowerShell module we use, etc.).

The way I've been converting things to the new platform is:

• Switch to .xproj from .csproj.
• Add a project.json based on one of the existing Autofac projects.
• Do a diff between another Autofac project that runs dotnet CLI and the current project to determine what's different - for example, the build script will be different, the appveyor.yml will be different, the tests will be running Xunit, and so on.
• Once everything's been converted and builds pretty identically to the other Autofac projects that also target netstandard1.x, create a test project that also targets netstandard 1.x and try to use a local NuGet repo (a folder specified in a NuGet.config) to make sure you can add a reference to the package you built.

It's... not super fast. That's why it's been taking a long time to get each one correctly converted and tested out.

[gdereese]

To your first question: The package with the changes I made does not support .NET Standard 1.3:

`Package Autofac.Extras.DynamicProxy 4.0.0-beta001 is not compatible with netstandard1.3 (.NETStandard,Version=v1.3). Package Autofac.Extras.DynamicProxy 4.0.0-beta001 supports: net451 (.NETFramework,Version=v4.5.1) Package Autofac 3.3.1 is not compatible with netstandard1.3 (.NETStandard,Version=v1.3). Package Autofac 3.3.1 supports:

• net40 (.NETFramework,Version=v4.0)
• portable-net40+sl5+win8+wp8 (.NETPortable,Version=v0.0,Profile=Profile136) One or more packages are incompatible with .NETStandard,Version=v1.3.`

So it looks like the reference to Autofac needs to be updated to one that supports .NET Standard, which appears to be 4.0.0-rc2-240.

To your next point: Thanks for letting me know your process. I'll work toward that end and add commits once that is done.

[gdereese]

So, since the System.Runtime.Remoting stuff (transparent proxies) has been removed from .NET Core, how should we deal with the RegistrationExtensions.InterceptTransparentProxy() method?

[tillig]

My first instinct on the transparent proxy thing is to do conditional compilation so it will be included for the full framework library but excluded from the netstandard version.

[tillig]

As of version 4.2.0 we have netstandard1.3 support.