The main difference between the LGPL and the GPL is that the LGPL does not impose any licensing requirements between modules that can be interchanged by the end user.
So as long as the end user can substitute a different but compatible version of the third party assembly, and as long as you obey the other requirements of the LGPL (like giving appropriate attribution if you're distributing that third party assembly) you can license your stuff however you like.
That depends on the nature of the reference. If "having a reference" is similar to "linking a library", you are not forced to license your software under the LGPL. That is where the LGPL and the GPL differ.
Consulting a lawyer is the only way to get complete, accurate advice of this nature.
That being said, you should be fine, provided you leave the LGPL code in the indepdendant, .NET assembly. If you use the code directly within your project, you may run into other issues, but as long as the .NET assembly is left as-is, and just used by your project, you shouldn't have to open up your code (although you do need to follow the other restrictions of LGPL - mainly distributing the appropriate license files, providing access to the code for the assembly, and using proper attribution).
仅在以下情况下才必须将代码开源： 1.您更改库/框架的代码。或者 2. 静态链接库。 （如果动态链接则无需担心。在 Windows 中可以使用 .dll 文件动态链接）
Sorry this thread is very old. But still couldn't find it very clear. So here is my answere
When a library or framework is LGPL , you are free to use the libraries in your commercial project (Yes. you can sell it). You don't need to make your code opensource.
You have to make the code opensource only if: 1. you change the code of library/framework. or 2. You link the libraries statically. (If you link dynamically there is no need to worry about. In windows you can use .dll files to link dynamically)
发布评论
评论（4）
LGPL 和 GPL 之间的主要区别在于 LGPL 不对最终用户可以互换的模块之间强加任何许可要求。
因此，只要最终用户可以替换第三方程序集的不同但兼容版本，并且只要您遵守 LGPL 的其他要求（例如，如果您分发该第三方程序集，则提供适当的归属），您就可以获得许可你喜欢的东西。
The main difference between the LGPL and the GPL is that the LGPL does not impose any licensing requirements between modules that can be interchanged by the end user.
So as long as the end user can substitute a different but compatible version of the third party assembly, and as long as you obey the other requirements of the LGPL (like giving appropriate attribution if you're distributing that third party assembly) you can license your stuff however you like.
这取决于参考文献的性质。如果“拥有引用”类似于“链接库”，则您不必根据 LGPL 来许可您的软件。这就是 LGPL 和 GPL 的不同之处。
That depends on the nature of the reference. If "having a reference" is similar to "linking a library", you are not forced to license your software under the LGPL. That is where the LGPL and the GPL differ.
咨询律师是获得此类完整、准确建议的唯一途径。
话虽如此，只要您将 LGPL 代码保留在独立的 .NET 程序集中，您应该没问题。如果直接在项目中使用代码，则可能会遇到其他问题，但只要 .NET 程序集保持原样，并且仅由项目使用，则不必打开代码（尽管您确实需要遵循 LGPL 的其他限制 - 主要是分发适当的许可证文件、提供对程序集代码的访问以及使用正确的归属）。
Consulting a lawyer is the only way to get complete, accurate advice of this nature.
That being said, you should be fine, provided you leave the LGPL code in the indepdendant, .NET assembly. If you use the code directly within your project, you may run into other issues, but as long as the .NET assembly is left as-is, and just used by your project, you shouldn't have to open up your code (although you do need to follow the other restrictions of LGPL - mainly distributing the appropriate license files, providing access to the code for the assembly, and using proper attribution).
抱歉，这个线程很旧了。但还是没能找到很清楚的。所以这是我的答案
当库或框架是 LGPL 时，您可以在商业项目中自由使用这些库（是的。您可以出售它）。您不需要将代码开源。
仅在以下情况下才必须将代码开源：
1.您更改库/框架的代码。或者
2. 静态链接库。 （如果动态链接则无需担心。在 Windows 中可以使用 .dll 文件动态链接）
Sorry this thread is very old. But still couldn't find it very clear. So here is my answere
When a library or framework is LGPL , you are free to use the libraries in your commercial project (Yes. you can sell it). You don't need to make your code opensource.
You have to make the code opensource only if:
1. you change the code of library/framework. or
2. You link the libraries statically. (If you link dynamically there is no need to worry about. In windows you can use .dll files to link dynamically)