In what version(s) of .NET should a library be released?
-
Greetings. I have a library written in C# 2.0 which will soon be re-released with minor documentation changes. The library was originally developed using VS 2005; I am now using VS 2013. Given that programs which use the library could be written in any version of C#, and that I wish to make using the library as convenient as reasonably possible, should I re-release the compiled library only in C# 2.0 or a combination of versions? I understand that C# 2.0, 3.0 and 3.5 use the same version of the CLR, whereas C# 4.x uses a newer version. I've read that mixing pre 4.0 libraries and 4.x applications might be an issue. Would the best option then be to release versions compiled with C# 2.0 and 4.0 ? There is no plan to update the code in the library to use newer (> 2.0) C# language features. Note that I have found related discussions on StackOverflow, but nothing which directly addresses the issue of releasing multiple versions of compiled libraries for different versions of .NET. Thanks everyone in advance for their insight and suggestions! Graham
-
Greetings. I have a library written in C# 2.0 which will soon be re-released with minor documentation changes. The library was originally developed using VS 2005; I am now using VS 2013. Given that programs which use the library could be written in any version of C#, and that I wish to make using the library as convenient as reasonably possible, should I re-release the compiled library only in C# 2.0 or a combination of versions? I understand that C# 2.0, 3.0 and 3.5 use the same version of the CLR, whereas C# 4.x uses a newer version. I've read that mixing pre 4.0 libraries and 4.x applications might be an issue. Would the best option then be to release versions compiled with C# 2.0 and 4.0 ? There is no plan to update the code in the library to use newer (> 2.0) C# language features. Note that I have found related discussions on StackOverflow, but nothing which directly addresses the issue of releasing multiple versions of compiled libraries for different versions of .NET. Thanks everyone in advance for their insight and suggestions! Graham
If you do not change code, do not change .NET Framework version...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
Greetings. I have a library written in C# 2.0 which will soon be re-released with minor documentation changes. The library was originally developed using VS 2005; I am now using VS 2013. Given that programs which use the library could be written in any version of C#, and that I wish to make using the library as convenient as reasonably possible, should I re-release the compiled library only in C# 2.0 or a combination of versions? I understand that C# 2.0, 3.0 and 3.5 use the same version of the CLR, whereas C# 4.x uses a newer version. I've read that mixing pre 4.0 libraries and 4.x applications might be an issue. Would the best option then be to release versions compiled with C# 2.0 and 4.0 ? There is no plan to update the code in the library to use newer (> 2.0) C# language features. Note that I have found related discussions on StackOverflow, but nothing which directly addresses the issue of releasing multiple versions of compiled libraries for different versions of .NET. Thanks everyone in advance for their insight and suggestions! Graham
Stay with .Net framework 2, but tell users of your library who wish to use more recent versions of the framework that they may need to add an entry in app.config:
<startup useLegacyV2RuntimeActivationPolicy="true" />
-
Greetings. I have a library written in C# 2.0 which will soon be re-released with minor documentation changes. The library was originally developed using VS 2005; I am now using VS 2013. Given that programs which use the library could be written in any version of C#, and that I wish to make using the library as convenient as reasonably possible, should I re-release the compiled library only in C# 2.0 or a combination of versions? I understand that C# 2.0, 3.0 and 3.5 use the same version of the CLR, whereas C# 4.x uses a newer version. I've read that mixing pre 4.0 libraries and 4.x applications might be an issue. Would the best option then be to release versions compiled with C# 2.0 and 4.0 ? There is no plan to update the code in the library to use newer (> 2.0) C# language features. Note that I have found related discussions on StackOverflow, but nothing which directly addresses the issue of releasing multiple versions of compiled libraries for different versions of .NET. Thanks everyone in advance for their insight and suggestions! Graham
