Q: What is the Open Source VWG SDK? 
A: It is a free development environment for creating new LGPL (open source) web applications and porting existing legacy applications to the web using WinForms toolkit and controls, ASP.net integration and wrapping capabilities. The VWG SDK can also serve as open source runtime for Visual WebGui LGPL applications.
|
| |
| Q: What is the open source Silverlight SDK?
A: In the current beta phase of Silverlight capabilities within Visual WebGui, you can develop and deploy Silverlight applications with the Visual WebGui SDK and the Professional Studio. When the Silverlight SDK is released it will be packed as a separate product and no longer included within the VWG SDK and the Professional Studio.
|
| |
Q: What is the Open Source Express Studio?
A: Visual WebGui Express Studio contains the entire capabilities of the designer within MS Visual Web Developer Express Edition 2008. The entire set of limitations is derived from this environment's features. For example, Visual Studio integration is not available in this edition therefore, is not available with Visual WebGui Express Studio.
Learn more about the Visual Studio Express Edition features. |
| |
Q: What are the main differences between the Visual WebGui SDK and the Professional Studio?
A: The Visual WebGui SDK doesn’t include the full Visual WebGui designer and the Technical Support package which are provided with the Professional Studio. The SDK is free and licensed with (open source) LGPL. Therefore, applications developed with it can only be deployed as LGPL projects.
Click here for a full specifications table |
| |
| Q: What is the difference between beta release, pre-release and release candidate?
A: Pre-release is a commercial release which is not a completely finalized version that is offered at a reduced pre-release price. A beta release can be either not a feature complete product or an unstable product which is offered for free until a pre-release or release candidate versions are offered. A release candidate is a version which is released after thorough testing by Gizmox.
|
| |
| Q: What product should I use if I am planning to use one of the server extensions in the future?
A: Any Visual WebGui development environment (SDK or Studio) will enable extending with any server capability. In case the API will be exposed in specific development environment you will be able to upgrade the project seamlessly upon purchasing an advanced product.
|
| |
| Q: Do I get the Office & Charting Extensions with the Professional Studio?
A: The free beta version of the Professional Controls Suite that includes the Office & Charting extensions is provided as part of the Visual WebGui development environments (SDK & Express/Pro Studio). Upon release, the Professional Controls Suite will be available for purchase as a separate product and will not be included in the SDK or Studio Suites. However, if you purchase a Professional Studio before the Professional Controls Suite was released seperately, you are entitled to keep developing and deploying with those controls for free.
|
| |
| Q: What is the difference between Subscription and Perpetual?
A: The subscription provides free deployment and unlimited version updates as well as technical support within the subscription period regardless of the version number, whereas perpetual license updates are limited to major version numbers (6.x, 7.x, etc. See next question). Gizmox is obligated to support each major version for at least 1 year from the initial major version's release date. Technical support is only valid for the specified term.
|
| |
| Q: What is the difference between major version, minor version and stabilization version?
A: A major version stands for significant changes such as added functionalities and capabilities and is represented by the left number (6.x, 7.x, etc.). A minor version is a large set of fixes and adjustments which are incorporated within a major version and is represented by the first number after the decimal point (x.3, x.4, etc.). A stabilization version is a revision of the last minor or major version and which fixes the last known issues in the version. It is represented by the number to the right of the second decimal point (x.y.2, x.y.3, etc).
|
| |
| Q: What portion of Visual WebGui is free open source?
A: Visual WebGui SDK has always been and will always be open source in the parts where the community has customization capabilities. Visual WebGui runtime and design time assemblies have never been open source and will probably remain that way. All of the current available development environments can be downloaded freely with or without sources. In addition, there is a public SVN branch from which the sources can be downloaded at any given time.
|
| |
| Q: What obligations do I have with licensing my applications / products when I use Visual WebGui LGPL licensed products such as SDK or Express Studio?
A: You may license your application / products to your users under whatever license you choose provided that the Visual WebGui library and code within the combined work are licensed to your end user organization as open source LGPL and that you notify your combined work application end user organization that it contains Visual WebGui Copyrighted open source library and code and you must maintain Visual WebGui copyright LGPL waiver.
|
| |
| Q: What if I do not want to present the LGPL Waiver?
A: In case you want to remove the LGPL waiver you would need to buy a commercial design time license or a OEM/SaaS license if your product/service is distributed to more than 5 end user organizations.
|
| |
| Q: What about GPL Silverlight SDK?
A: Very similar to LGPL, only that with GPL license you are required to keep your entire application's source open, and not only the Visual WebGui’s library as in the case with LGPL open source combined work applications.
|
| |
| Q: Do I have a warranty from Gizmox, when I use LGPL or GPL licensed products?
A: No. LGPL or GPL licensed product do not carry any kind of warranty with them, you may use them at your own risk.
|
| |
Q: What about the Professional Studio? Do I have warranty?
A: Yes. Commercial products have a warranty and also include the Technical Support package as presented on the website see here. Perpetual license provides you with Technical Support for a limited period of time for either 1, 4, or 8 months depends on the Perpetual package (detailed in the store). |
| |
| Q: What happens at the end of the subscription period?
A: In order to keep receiving updates and technical support you need to renew your subscription. If you do not need the technical support any more, you might want to buy a perpetual license of the last updated version you got with the subscription, which offers you updates within that major version.
|
| |
| Q: Can I deploy applications even though my subscription expired?
A: Yes, as long as it is customized applications or that the same named application is not deployed on more than 5 end-user organizations. In that case you will need OEM / SaaS license.
|
| |
| Q: I have purchased a Subscription in the past and the license is still valid. Do I need to purchase a new commercial license?
A: No. Your license and subscription remain valid until the original expiry date and can be used with the latest Professional Studio.
|
| |
| Q: I purchased a Professional Studio. Where do I get the license key and how do I activate it?
A: After receiving confirmation for purchasing a Visual WebGui product, you can get the license key from the "My Licenses" section inside the store. The license should be typed in when asked during the installation/activation process of the product.
|
| |
| Q: What if I use more than a single computer?
A: If you use more than 1 computer (A work station and a laptop for example) you are allowed to receive upon request up to 3 activations for the same license, given that they are all used by the same developer and not simultaneously.
|
| Q: In what cases do I need an OEM / SaaS license?
A: OEM / SaaS license agreements are required when your application combines the Visual WebGui (VWG) SDK and is distributed to more than 5 end-user organizations or servers, or more than 5 end-user organizations as SaaS. However, if you developed customized applications for customers/organizations (a unique application that is not resold to other customers or offered as a product) even if they have more than 5 end-users in it there is no need for OEM / SaaS license.
|
| |
| Q: How do I count applications or SaaS end-user organizations that make my liability for OEM / SaaS license?
A: If the combined application (your application plus the VWG SDK), for example was sold to 4 organization only, you don’t need an OEM License, however if you sell it to more than 5 different organizations, or if you choose to provide a service using an application that combines the VWG SDK, and you have more than 5 users from different organizations, you will have to distribute it with a Visual WebGui OEM license.
|
| |
| Q: How to define an end-user organization?
A: Organization is an entity which acts as an end-user of the application, or uses the application as SaaS, whether by an individual or multiple users within the corporation, company, partnership or any other entity.
|
| |
| Q: When do I have to pay for OEM / SaaS license?
A: You may pay just before you reach application deployment to your 5th user/organization. You may, however, pre-pay a lump sum of $5000 per named application for a lifetime royalty free deployment of the specific named application.
|
| |
| Q: Do I always have to pay for OEM / SaaS license agreement if I commercially distribute my named application?
A: No, if the Visual WebGui product you use is licensed with LGPL license, you may embed VWG open source as you got it, leave Visual WebGui LGPL waiver on your UI, and comply with the rest of the LGPL terms. In this case you do not need to pay.
|
| |
| Q: What about if I use Visual WebGui GPL products to develop and embed with my application?
A: You may not pay, but not only that you need to maintain Visual WebGui library and code open source, the entire application must be open source and licensed to your end-user organization as one.
|
| |
| Q: If I do not want the LGPL or GPL open source restrictions, and I do not want VWG waiver on my application UI?
A: In this case you would need to pay for a Visual WebGui OEM license.
|
| |
| Q: What is a “named application”?
A: This is the unique name given to your application as it appears on the license agreement and according to which is identified.
|
| |
| Q: Where is the LGPL Visual WebGui waiver presented if I use the LGPL license?
A: The LGPL waiver is presented in the browser's window title and any open dialog window title.
|
| |
|