Re: GPL question

Tony Caduto wrote:

It's best to try and find opensource stuff with LGPL or BSD licenses which don't require you to release any source code when linking to a DLL.

Or one can buy such a license. Open source does not imply "for free" ;-)

DoDi
.

Relevant Pages

  • Re: incremental build not optimal?
    ... >> Linking is never a part of the .NET Framework concept. ... > version of my application without the dependencies. ... > multiple clients that you have written, ... > your DLL retains backward compatibility. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: crossing dll boundary ...
    ... Dynamic linking if calling LoadLibrary/GetProcAddress instead. ... The only way AFAIK to use exported classes in another DLL is to statically link. ... The member functions are exported functions in DllA. ... Your terminology of "static linking" versus "dynamic linking" is confusing, ...
    (microsoft.public.vc.mfc)
  • Re: how not to expose source code
    ... it's rather easy to take a dll and pop it into full source code ... the salamagar tool even goes as far as ... Compiled dlls have MSIL code but not the real source code. ... The code would compile to a ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: how not to expose source code
    ... I looked at my dll with a hex viewer. ... Compiled dlls have MSIL code but not the real source code. ... The code would compile to a ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: how not to expose source code
    ... Compiled dlls have MSIL code but not the real source code. ... dll and could not be viewed when used in a vs.net project. ... The code would compile to a ... separate dll and could not be viewed when used in a vs.net project. ...
    (microsoft.public.dotnet.framework.aspnet)