Possibility of adding strong naming build?

Jan 12, 2011 at 4:15 PM

Our projects are all strongly named and I can't reference AutoPoco because it's not strongly named. I could probably build AutoPoco and just use a blank key file but it might be easier if a strongly-named build file was available if we need to sign it.

Jan 12, 2011 at 4:28 PM

Bah, there is always somebody!

I'll start releasing both, I'll probably keep on shipping the NuGet one unsigned though - I personally can't stand signing :-)

Jan 12, 2011 at 4:29 PM

(Can you create one for your own use for now and I'll make sure to do a 1.1 with a signed build? - that'll be sometime next week with a whole heap of features and improvements)

Jan 12, 2011 at 4:53 PM

Yes, I just did that :)

I might report an issue soon; my generation seems to be crashing the test agent :(

Jan 12, 2011 at 4:58 PM

Weird, please do - should be easy enough to fix if I have a stack trace of some sort