I want to distribute a .NET library that is .NET 3.5 compliant. The library holds references only to external managed libraries that are targeted against .NET 3.5 client profile or lower. Is there any point in distributing my library as separate .NET 3.5 and 4.0 targeted assembly?
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
If you build an application that targets 4.0, you can reference your library even if it's targeted to 3.5. There's no need to have a separate version for 4.0. Unless of course, you use features specific to 4.0 such as default method arguments or parallel classes among others.
BTW, using a <3.5 library in 4.0 will not cause any warnings about mixed assemblies (that i know of).