Mark Fody as development dependency about methodboundaryaspect.fody

[Ralf1108]

never heard of "development dependency" before.. so I will have to investigate this first

[Ralf1108]

do you mind make the required change and provide a pull request? :-)

[damageboy]

I think he means that the MethodBoundayAspect.csproj should contain the package references as explained in the basicfodyaddin README.md:

https://github.com/Fody/BasicFodyAddin/blob/9e28d1dd2b89bc77588f510dfe7174b5623b13ee/BasicFodyAddin/BasicFodyAddin.csproj#L11:

  <ItemGroup>
    <PackageReference Include="Fody" Version="3.0.3" PrivateAssets="None" />
    <PackageReference Include="FodyPackaging" Version="3.0.3" PrivateAssets="All" />
  </ItemGroup>

The PrivateAssets=... attributes (also) control how the resulting nupkg will look

[Ralf1108]

we try to separate the weaver stuff and the OnMethodBoundary base class into separate assemblies. Then we could remove the dependency to fody for the latter one.

[PulsarFX]

Um, there is no dependency on Fody or Cecil from MethodBoundaryAspect.dll - that is fine.

I think it is enough to modify the nuget package spec like shown in comment by damageboy.
There is also a spec page on this at https://blog.nuget.org/20170316/NuGet-now-fully-integrated-into-MSBuild.html

[marcells]

We also want to use a lower Target Framework (e.g. 4.5.2) for our base class. That is only possible by separating the base class and runtime attributes from the weaving code. The weaving code is dependent on FodyCecil, why it has to be at lease 4.6.

[PulsarFX]

ah ok, fair enough ;)
I had to go back to v0.35 to get .net4.5.2 support on a project where I was not able to set .net 4.6.2 as the base because of contract stuff

[marcells]

I made released a new version (1.0.41) right now. It should be possible to use the aspect under .NET 4.5.1. I did also mark the packages a developmentDependency.

Could you check, if it is working for you and reopen the issue, if not?