Nuget as DLL not CS

[ghostsquad]

When installed via NuGet it adds a CS file to your project(s). If you have multiple projects, and they reference each other, you can't put TinyIoC into both projects, as the build will fail with ambiguous call errors. It also may prevent builds due to stylecop or fxcop errors.

[Daniel15]

I usually put TinyIoC in a "core" project and have all the other projects use that version.

[damianh]

@grumpydev I'd suggest distributing this as a .pp so people can get benefit of namespace transformations when installing. Also consider putting the content in an App_Packages folder following this convention?

@ghostsquad, @Daniel15 Future version will let you internalize the container via conditional compilation symbol #59

[ghostsquad]

I suppose have 2 nuget packages would solve this as well. TinyIoc.Dll and TinyIoc (CS file)

[goldsam]

I don't understand how a DLL is less convenient. The .CS file packaging is a pain. Our team solved this in the same way suggested by @Daniel15, but it seems messy and unnecessary.