cloudscribe commercial libraries are published as nuget packages just like our open source libraries. You can find all of our libraries on nuget.org, the open source libraries have blue icons and the commercial libraries have green icons. The easiest way to get our products is by using our Project Template for Visual Studio, which can create an application configured with our open source and commercial libraries in various configurations based on the options you choose. We also have reference sample applications on github that show how to wire up the nuget packages in case you want to integrate our products with existing web applications. You can find links to the reference applications in the list below and in the product details listed in our store. All of our commercial products are released under our commercial product license, and an Enterprise licence is also available if you would like to obtain the source code to make further modifications for your own projects (please contact us for details).
Some of our commercial libraries can be used with any ASP.NET Core MVC application and do not require cloudscribe Core, but all of our commercial libraries work optimally when used with our open source libraries.
We put a lot of effort into all of our products both open source and commercial, but we depend on sales of our commercial products to support our continued work.
Forms and Surveys
- cloudscribe.Forms.Web - the main library
- cloudscribe.Forms.Bootstrap4 - views for Bootstrap 4
- cloudscribe.Forms.CoreIntegration - integration for cloudscribe Core
- cloudscribe.Forms.ContentTemplate.Bootstrap4 - integration to easily place forms on pages in cloudscribe SimpleContent
TalkAbout Comment System
- cloudscribe.EmailList.Web.Mvc - the main library
- cloudscribe.EmailList.Views.Bootstrap4 - views for Bootstrap 4
- cloudscribe.EmailList.CoreIntegration - integration for cloudscribe Core
- cloudscribe.EmailList.KvpUserProperties.Integration - integration to include newsletter sign up on registration and user profile and management pages in cloudscribe Core
- also depends on cloudscribe Email Templating and cloudscribe Email Queue, see below
- cloudscribe.Membership.Web.Mvc - main library
- cloudscribe.Membership.Views.Bootstrap4 - views for Bootstrap 4
- cloudscribe.Membership.HangfireIntegration - for processing background tasks such as removing users from granted roles when membership expires
- cloudscribe.Membership.StripeIntegration - integration with cloudscribe.StripeIntegration, see below
- also depends on cloudscribe StripeIntegration and cloudscribe Email.Templating, and cloudscribe Email Queue, see below
This is not a standalone product, it is used for email templates in the newsletter solution and for membership renewal reminders in the paywall solution
- cloudscribe.EmailTemplating.Web - main package
This is not a standalone product, it is used in the newsletter solution and in the paywall solution
- cloudscribe.EmailQueue.Services - main library
- cloudscribe.EmailQueue.CoreIntegration - integration with cloudscribe Core
- cloudscribe.EmailQueue.HangfireIntegration - used for processing the email queue on a background task
This is not a standalone product, it is used in the paywall solution and will be used in other ecommerce solutions in the future
- cloudscribe.StripeIntegration.Mvc - main library
- cloudscribe.Core.StripeIntegration - integration for cloudscribe Core
Trial Mode Limitations
Our commercial libraries are free to try, but typically have alert messages shown every few page requests or other limitations that can be removed by installing a license activation file. Activation files are sold per host name, so you need to purchase a separate activation file for each host name where you use the product in order to remove the trial mode limitations.
Clicking the link in the alert will take you to the cloudscribe store passing a token for the product and the current host name so that you can create a license activation and purchase the needed file to remove the alert or other product limitation.
You should get the product working locally, then deploy to your production environment before purchasing the activation file since the activation file is always for a specific host name. You generally should not purchase an activation file for localhost unless you don't mind buying a license just to get rid of the alerts in your development environment.
Installing the activation file
The activation file for each product and host name must be installed to remove the trial mode alerts and limitations. You need to create a folder named LicenseFiles in the root of your web application. You download the activation file and put it in that folder, or if you need to purchase activation files for more than one host name, you can organize them into sub folders corresponding to the host name. For example if you site is running at www.somedomain.com then you would create the folder structure /LicenseFiles/www.somedomain.com/ and put the activation file for that host name in the folder named the same as the host name. This is useful if you want to purchase activation files for different environments that use different host names and also useful if you are using host name based multi-tenancy. It is a good idea to check these files into your source code repository along with your application code.