Application Development in Sharepoint hardly requires any coding. Why? See the following list:
• Entities - these get created as "Content Types" in WSS and require no coding.
• Metadata - these get created as "Site Columns" in WSS and get bound together as "Content Types". No coding.
• Database - WSS automatically stores all metadata in its own database without the need to create additional structures. No coding
• Connections - connections to the database handled by the WSS provisioning engine. No coding.
• Security - this is handled by WSS through NTLM, Kerberos, SSO or "Forms Based" authentication. No coding
• Authentication - this is done by IIS and WSS. No coding
• Optimising - WSS has built in caching components that can be configured using the browser.
• Scalability - the topology of WSS allows it to scale out into a farm configuration. All web pages are stored in the database as metadata and can therefore be rendered from any amount of WFE's.
• Auditing - WSS has built in audit trails.
• Web page builds - the provisioning engine of WSS creates web page on the fly without the need of coding them. The layouts can be controlled using the browser or SPD.
Vinay Chavadi's Blog on Application Development in SharePoint 2010/2013/2016 & SharePoint Online
Subscribe to:
Post Comments (Atom)
-
There are 3 SPJobLockType available: 1. SPJobLockType.None -- if you set it none, the instance will run in all the available s...
-
Overview: We define disaster recovery as the ability to recover from a situation in which a data center that hosts SharePoint Server beco...
No comments:
Post a Comment