Adding Custom Target beyond Common Framework and Profile Targets

Topics: General
Apr 6, 2013 at 2:12 AM
The concept of target is awesome as it pertains to a framework or profile name. Is it not possible to define a custom target that extend the list based on the presence of other assemblies included in a given project other than the preset list I'm finding in documentation? If a feature like this does not exist any thoughts on the best way to work around this?
Apr 6, 2013 at 7:17 PM
Can you give a concrete example?
Apr 7, 2013 at 1:13 AM
I'd like to drop code via a nuget package that is built against the existence of foobar assembly version 1. Other users may be using foobar version 2. So the code I include with my nuget package should look pretty different for version 2. Clear as mud or does that help any?