Skip to content

Conversation

adbre
Copy link
Contributor

@adbre adbre commented May 31, 2014

I recently did some work in a project where the assembly including TinyIoC built XML documentation, and they had enabled 'Treat warning as errors', so TinyIoC caused compile errors out of the box.
This PR fixes this.

@ghostsquad
Copy link

A better fix is to not include the raw CS file, but rather a built DLL in the nuget package.

see issue #54

@grumpydev
Copy link
Owner

@ghostsquad the whole point of tinyioc is to not do that.. so no, that's not a "better fix"

@adbre
Copy link
Contributor Author

adbre commented Jun 2, 2014

I agree with @grumpydev, in my case TinyIoC must be included as a cs-file, and made internal. Exactly the point why TinyIoC is distributed as it is.

@thomaswurtz
Copy link

Any plans on getting this merged? :)

As a workaround I'm adding some pragma statements to the file in the project I'm currently working on.

#pragma warning disable 1574, 1591, 1711, 1712

@niemyjski
Copy link
Collaborator

Can you fix the merge conflicts and we'll accept this pr with the documentation changes.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants