SharpDevelop and General question about LPGL licence when integrateopensource in a commercial applic

[SQACSharp]

General licensing question
==========================

I'm looking to integrate a full C#/VB.net code editor/compiler in my
application with all debuging and intellisense things. It's for a
commercial product.

I start looking at SharpDevelop (http://www.icsharpcode.net/OpenSource/
SD/Default.aspx) and wondering what are the LPGL restrictions? After
reading a lots about licensing i'm still really confused

Is it possible to directly use the entire SharpDev project and modify
it to create a commercial application?
Is the LGPL license type allow only the use of the 'library' to
integrate features in my application?

Is anybody can clarify the limitations and obligations of this kind of
licensing in simple words?

Is anybody know a good example that integrate SharpDevelop features in
a C# application?

Thanks!

 

[Arne Vajhøj]

General licensing question
==========================

I'm looking to integrate a full C#/VB.net code editor/compiler in my
application with all debuging and intellisense things. It's for a
commercial product.

I start looking at SharpDevelop (http://www.icsharpcode.net/OpenSource/
SD/Default.aspx) and wondering what are the LPGL restrictions? After
reading a lots about licensing i'm still really confused

Is it possible to directly use the entire SharpDev project and modify
it to create a commercial application?
Is the LGPL license type allow only the use of the 'library' to
integrate features in my application?

Is anybody can clarify the limitations and obligations of this kind of
licensing in simple words?

Is anybody know a good example that integrate SharpDevelop features in
a C# application?

For a commercial product you should have a lawyer give you
recommendation.

The common understanding of LGPL is that:
- your changes to the LGPL code will be under LGPL
and you need to make the source available for those
- you do not need to make the source available for
your own code that just call LGPL code residing in a DLL

Arne

 

[SQACSharp]

For a commercial product you should have a lawyer give you
recommendation.

The common understanding of LGPL is that:
- your changes to the LGPL code will be under LGPL
   and you  need to make the source available for those
- you do not need  to make the source available for
   your own code that just call LGPL code residing in a DLL

Arne- Hide quoted text -

- Show quoted text -

Ok I can just call the LGPL code in the dll without doing any change
on their code....so using directly the entire sharpdevelop projet and
build my stuff in it is defenitively not a good idea for a commercial
product.

Thanks.

 

[Arne Vajhøj]

Ok I can just call the LGPL code in the dll without doing any change
on their code...

You can do that.

You can also modify the source code, build the DLL from modified source,
use that DLL from your app and only release your modifications to the
modified code but keep your main app code closed source.

so using directly the entire sharpdevelop projet and
build my stuff in it is defenitively not a good idea for a commercial
product.

LGPL does not allow you to keep your code closed source in
that case.

Arne