According to the SDK documentation, signing the package assembly is required, but a co-worker claims he was able to successfully deploy and register and unsigned package. Is the signing actually being enforced, or has this been relaxed with the later releases?
This wouldn't be a big issue except for the fact that we have a third-party dependency that doesn't incorporate strong naming, which forces us to do the IL recompile trick on that assembly every time we do a NuGet upgrade, until we have time to replace it. It'd be really convenient not to have to do that.
Package Assembly Signing
Moderator: Phil Barton
-
- Posts: 82
- Joined: Tue Jan 21, 2014 11:35 am
- Location: Austin, TX
-
- Posts: 1377
- Joined: Wed Jan 15, 2014 3:50 pm
- Location: Raleigh, NC
- Contact: