Hi All,
We are in process of designing a GUI application using PowerShell Studio 2015. We are planning to distribute application for commercial use.
Can someone please let us know what all things we need to keep in mind before the application can be ready for commercial distribution? For example, how about PowerShell cmdlets licensing? Similarly, how about control licenses such as Treeview, Datagridview, etc.
Basically, we would like to know what license terms to include.
By the way, is there any way to create a license term using PowerShell studio?
Thanks heaps!
Nratawa
Commercial use
Forum rules
Do not post any licensing information in this forum.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Do not post any licensing information in this forum.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
- Alexander Riedel
- Posts: 8488
- Last visit: Tue Apr 16, 2024 8:42 am
- Been upvoted: 37 times
Re: Commercial use
We don't really know what your application does and what it uses, so we cannot give any legal advise on what you need to do or not.
The PowerShell cmdlets and standard UI controls are part of the Windows operating system and of course require no additional licensing.
They are just on the target system. If you have specific PowerShell version requirements you should check for those in the installer.
If you require any third party controls or modules then you need to contact the specific vendor.
I am not sure what you mean by "create a license term".
The PowerShell cmdlets and standard UI controls are part of the Windows operating system and of course require no additional licensing.
They are just on the target system. If you have specific PowerShell version requirements you should check for those in the installer.
If you require any third party controls or modules then you need to contact the specific vendor.
I am not sure what you mean by "create a license term".
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Commercial use
Thanks for taking the time to respond!Alexander Riedel wrote:We don't really know what your application does and what it uses, so we cannot give any legal advise on what you need to do or not.
The PowerShell cmdlets and standard UI controls are part of the Windows operating system and of course require no additional licensing.
They are just on the target system. If you have specific PowerShell version requirements you should check for those in the installer.
If you require any third party controls or modules then you need to contact the specific vendor.
I am not sure what you mean by "create a license term".
Is there any way to generate a license or use the License text file in PowerShell Studio MSI builder?