Do I need to include the Ms-PL licence with commercial app

I know that it isn�t exactly advisable to seek legal advice online, but I�m hoping somebody here has had a similar experience and can save me having to contact a solicitor/lawyer.
Basically, I�m writing a piece of software in C# which I intend to sell and I would like to use the �Extended WPF Toolkit� binaries in my software. However the �library� is licensed under the Microsoft Public License (Ms-PL) and I�m not sure whether I would be required to include that licence with my software. I will not be modifying anything, and my research would suggest not, but I want to be absolutely sure before I put anything on the market.
Does anyone know if the Ms-PL license requires me to display any notices or include the licenses?
Thanks in advance
http://wpftoolkit.codeplex.com/license
Answer #1
don’t remove it IF it’s there. you only have to ADD it if you distribute their source code. this applies.
(C) If you distribute any portion of the software, you must retain all copyright, patent, trademark, and attribution notices that are present in the software.
(D) If you distribute any portion of the software in source code form, you may do so only under this license by including a complete copy of this license with your distribution. If you distribute any portion of the software in compiled or object code form, you may only do so under a license that complies with this license. basically, they want the licence in there.
Answer #2
Ah that makes sense. I didn’t really notice that keyword ‘retain’!
So I’ve downloaded the binaries, which is the only thing I’ll be using, and there is no sign of any license in the .ZIP – so I don’t need to worry about including anything as I won’t be distributing any source code?
Answer #3
Ah that makes sense. I didn't really notice that keyword 'retain'!
So I've downloaded the binaries, which is the only thing I'll be using, and there is no sign of any license in the .ZIP - so I don't need to worry about including anything as I won't be distributing any source code?the license should be encoded in the binaries already.. that’s why they want you to include the license if you distribute the source code.
Answer #4
I understand now, after including the binaries and seeing what happens when I compile the program. Does the license allow me to rename the DLL file?
Answer #5
I understand now, after including the binaries and seeing what happens when I compile the program. Does the license allow me to rename the DLL file?it don’t say a word about that anywhere, so it must be ok..
Answer #6
it don't say a word about that anywhere, so it must be ok..Fair enough, that’s what I would have thought to. I can’t see any reasonable reason why they wouldn’t want you to anyway, but having said that, it is Microsoft! I’ll go ahead and rename it though… Thank you very much for your help.
I do have one more question, it probably won’t be possible, but is it possible to put the DLL within the executable so that my application is only one file?
Answer #7
it don't say a word about that anywhere, so it must be ok..Fair enough, that's what I would have thought to. I can't see any reasonable reason why they wouldn't want you to anyway, but having said that, it is Microsoft! I'll go ahead and rename it though... Thank you very much for your help.
I do have one more question, it probably won't be possible, but is it possible to put the DLL within the executable so that my application is only one file?I don’t think so. I don’t recall ever seeing that. usually, .exe and .dll are separate files..
Answer #8
Aha, thank you for your information – it has been very helpful. Just done a quick Google though (should’ve done that first, I know), and it seems it might be possible to include the DLL in the .exe if I really wanted too – in case anyone else who stumbles across this topic is interested:
http://stackoverflow.com/questions/476993/can-i-include-dll-in-exe-in-visual-studio