Skip to content
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

Review compared to "Open-source library guidance" #402

Closed
martincostello opened this issue Oct 17, 2018 · 11 comments · Fixed by #577
Closed

Review compared to "Open-source library guidance" #402

martincostello opened this issue Oct 17, 2018 · 11 comments · Fixed by #577
Assignees
Milestone

Comments

@martincostello
Copy link
Member

Before we release version 7.0.0, we should review the codebase with respect to the new "Open-source library guidance" documentation from Microsoft and determine what, if anything, we should do for JustSaying while we have the opportunity to make breaking changes.

The only obvious thing to consider that we don't currently do is strong-naming, which would allow the library to be consumed by applications/libraries that are/need strong-naming themselves.

Similar changes elsewhere on the same theme include:

@martincostello martincostello added this to the v7.0.0 milestone Oct 17, 2018
@AnthonySteele
Copy link
Contributor

I'm sure that we will debate strong naming.

@AnthonySteele
Copy link
Contributor

We have agreed to allow strong naming.

@martincostello
Copy link
Member Author

I'll look at doing a PR like the other two, unless someone else has a burning desire to do it.

@slang25
Copy link
Member

slang25 commented Nov 25, 2018

On strong-naming, JustBehave is now signed, but structuremap isn't and it looks like there is no intention from them to do it, not sure the best way forwards with this 😕

@martincostello
Copy link
Member Author

This might fit in with what I'm doing in #431, where I'm trying to make the DI more pluggable as a whole.

If that all works, we could replace StructureMap with something else that is, like the Microsoft one?

@slang25
Copy link
Member

slang25 commented Nov 25, 2018

image

@stale
Copy link

stale bot commented Jan 20, 2019

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jan 20, 2019
@martincostello
Copy link
Member Author

Re-reviewing this, it looks like the path forward is to move the tests for StructureMap into their own test assembly that doesn't need [assembly: InternalsVisibleTo("...")] and by necessity not strong-name JustSaying.Extensions.DependencyInjection.StructureMap. Then everything else should be sign-able and we can turn it on for the rest of the assemblies.

@stale
Copy link

stale bot commented Apr 21, 2019

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Apr 21, 2019
@stale
Copy link

stale bot commented Jun 17, 2019

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jun 17, 2019
@martincostello martincostello self-assigned this Jun 29, 2019
@stale
Copy link

stale bot commented Aug 24, 2019

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

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

Successfully merging a pull request may close this issue.

3 participants