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

Update NuGet package #7

Closed
yln opened this Issue Sep 27, 2011 · 7 comments

Comments

Projects
None yet
3 participants
@yln

yln commented Sep 27, 2011

The current NuGet package (2.2.0.6) does not work well with .NET 4.0.
Ninject.MockingKernel.Moq.MoqMockProvider.Create(IContext context) throws System.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

@remogloor

This comment has been minimized.

Show comment
Hide comment
@remogloor

remogloor Sep 29, 2011

Member

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) throws System.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:
#7

Member

remogloor commented Sep 29, 2011

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) throws System.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:
#7

@yln

This comment has been minimized.

Show comment
Hide comment
@yln

yln Sep 29, 2011

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.

yln commented Sep 29, 2011

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.

@StuartLeitch

This comment has been minimized.

Show comment
Hide comment
@StuartLeitch

StuartLeitch Nov 25, 2011

Hi Remo,

Thanks for your great work on this Ninject extension. Could you please update the NuGet gallery to the latest version?

Cheers,
Stuart

StuartLeitch commented Nov 25, 2011

Hi Remo,

Thanks for your great work on this Ninject extension. Could you please update the NuGet gallery to the latest version?

Cheers,
Stuart

@remogloor

This comment has been minimized.

Show comment
Hide comment
@remogloor

remogloor Dec 19, 2011

Member

Nuget will be updated with the upcomming 3.0 RC1

Member

remogloor commented Dec 19, 2011

Nuget will be updated with the upcomming 3.0 RC1

@remogloor remogloor closed this Dec 19, 2011

@StuartLeitch

This comment has been minimized.

Show comment
Hide comment
@StuartLeitch

StuartLeitch Dec 19, 2011

Thanks Remo!

StuartLeitch commented Dec 19, 2011

Thanks Remo!

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Feb 3, 2012

Why not release a fixed v2.2.0.7 to NuGet now? As it stands, this issue is a PITA.

ghost commented Feb 3, 2012

Why not release a fixed v2.2.0.7 to NuGet now? As it stands, this issue is a PITA.

@remogloor

This comment has been minimized.

Show comment
Hide comment
@remogloor

remogloor Feb 3, 2012

Member

Because there it the stable 3.0.0-rc3 which most likely will be 100% binary compatible with 3.0.0 final.

Member

remogloor commented Feb 3, 2012

Because there it the stable 3.0.0-rc3 which most likely will be 100% binary compatible with 3.0.0 final.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment