Closed yln closed 12 years ago
Hi Julian
Thanks for reporting this bug. If you have a bugfix already then please provide a pull request on github.It will speed up the fixing it.
Thanks, Remo
Am 27.09.2011 um 15:53 schrieb Julian Lettnerreply@reply.github.com:
The current NuGet package (2.2.0.6) does not work well with .NET 4.0.
Ninject.MockingKernel.Moq.MoqMockProvider.Create(IContext context)
throwsSystem.TypeAccessException
because of the new security transparency model introduced in .NET 4.0. This is already fixed in the source (by applying the[System.Security.SecuritySafeCritical]
attribute).Workaround: Build Ninject.MockingKernel yourself.
Proposed fix: Update package in the NuGet gallary.
More information: https://groups.google.com/d/msg/ninject/xInlcd2b1l8/TwIAbkzHhWUJ
Reply to this email directly or view it on GitHub: https://github.com/ninject/ninject.mockingkernel/issues/7
The issue is already fixed in the source (see here), but the package on the NuGet gallary is outdated. Proposed fix: Release a new NuGet package by building from the current source and upload it to the NuGet gallary.
Hi Remo,
Thanks for your great work on this Ninject extension. Could you please update the NuGet gallery to the latest version?
Cheers, Stuart
Nuget will be updated with the upcomming 3.0 RC1
Thanks Remo!
Why not release a fixed v2.2.0.7 to NuGet now? As it stands, this issue is a PITA.
Because there it the stable 3.0.0-rc3 which most likely will be 100% binary compatible with 3.0.0 final.
The current NuGet package (2.2.0.6) does not work well with .NET 4.0.
Ninject.MockingKernel.Moq.MoqMockProvider.Create(IContext context)
throwsSystem.TypeAccessException
because of the new security transparency model introduced in .NET 4.0. This is already fixed in the source (by applying the[System.Security.SecuritySafeCritical]
attribute).Workaround: Build Ninject.MockingKernel yourself.
Proposed fix: Update package in the NuGet gallary.
More information: https://groups.google.com/d/msg/ninject/xInlcd2b1l8/TwIAbkzHhWUJ