Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have seen a lot of libraries that are released in multiple frameworks. In any framework you choose, the library namespaces are the same, but the dll is compiled in .net 2.0, 3.5 or 4.0.
What is the standard or best practice way of having the same code built in the various frameworks? I’m curious if there is code duplication going on or if there is a better way.
a viable way would be to have a solution with multiple projects or even multiple solutions which you open one by one in Visual Studio but the project files (C# or VB.NET) always point to the same file in the file system.
for example, multiple projects in the same solution, one project contains the file normally and the other projects have a link to the file, added by using right click on project, add existing item, selecting the file then click arrow down in Add button and select
Add as Link.of course if inside the file contains code which belongs to certain frameworks only you should put the
ifor#ifdefand so on…