Applies to: Calendar E-Mail Extension for SharePoint on premise (SP2010, SP2013, SP2016, SP2019)
The following article describes what’s included in the Source Code Edition.In this article:
- The Source Code Edition is designed for developers, system integrators, ISVs
- What you get with the Source Code Edition
- Source Code fingerprint
The Source Code Edition is designed for developers, system integrators, ISVs
The Source Code Edition is part of the Enterprise license and is designed to be a foundation on which you can build your calendar based and e-mail enabled apps for SharePoint. It enables you to start with a proven, stable product that you can modify or enhance to add value and integrate with your SharePoint solutions and apps to suit your needs. We want to encourage partners and customers to use our stable, proven SharePoint Apps to add value to their SharePoint deployments and solutions.
The Source Code Edition is the foundation on which you can base your customized solutions. If you can’t find a suitable partner to create your customized solutions, please contact us. We will do our best to find a partner for you.
NOTE: In order to receive the Application Source Code you must accept our License Agreement in advance. We will not ship any source code prior to receiving the accepted agreement.
What you get with the Source Code Edition
The Source Code Edition contains the complete application code. The underlying framework source code containing base classes, interfaces, base types and their properties is not available, as it contains the license validation code and will therefore not be published. All relevant base classes, base types and their properties can be overridden with your own implementations. Additions to the framework itself can only be done by us.
The Calendar E-Mail Extension Source Code Edition contains the Visual Studio 2010, Visual Studio 2012 and Visual Studio 2015 solutions for SharePoint 2010, SharePoint 2013 and SharePoint 2016.
The solution contains the following components:
The solution contains a content type definition for the calendar content type and custom field definitions. Use this component to add additional fields or change fields’ properties.
The solution contains the list definition for the e-mail extended calendar list. You can develop the list schema to add or change fields and views.
The solution contains two delegate controls registered in the page header. One checks if the calendar list is configured correctly, the other renders status bars to indicate the event’s status.
Control templates – settings pages
The solution contains 2 settings pages to configure the application. One is accessible through the calendar’s list settings, the other through the “Calendar with E-Mail Extension” content type settings. You can develop these pages to add additional settings.
Control templates – EventForm.ascx
The solution contains the form template for the e-mail extended calendar event content type.
Entities in the Sapiens.at.SharePoint Framework are explicit implementations of content types providing not only type-safe access to their data but also a separation of business processes. The solution contains one event entity and implements additional properties (fields). If you develop the event content type you can also develop this entity to provide type-safe access to the item’s data.
Feature event receiver
The solution contains one feature receiver used to register the settings pages and to make sure all receivers are removed if the feature is deactivated.
Item event receivers
The solution contains item event receivers containing most of the business logic like e-mail dispatch, workspace creation and synchronization and much more.
The solution contains one e-mail receiver used to handle attendees’ responses, event creation and more.
The solution contains English and German language resources. You can edit them or create your own language files.
Source Code fingerprint
Each copy of the application’s source code is individually fingerprinted. The underlying framework compares computed checksums with those provided by the productInfo interface. Don’t change it. If you need to change assembly properties that are used for computing those checksums, or want to integrate parts of the source code into your own assemblies, we will serve your requests and provide you with new checksums.