Tuesday, September 8, 2015

Provider hosted app security in SharePoint apps


Check the below link, it was in detail.
https://samlman.wordpress.com/2015/03/02/security-in-sharepoint-apps-part-1/

Thursday, September 3, 2015

New Features in SharePoint 2016


  1. Role based configuration wizard for configuring a server role

  • Front end 
  • Application
  • Search
  • Specialized load
  • Distributed cache
  1. Zero downtime patching
  2. App launcher for on premise has been introduced
  3. Office 365 api's coming to On-premise 
  4. No Standalone machine any more there should be two servers two install SharePoint now one for SharePoint and other for Sql server
  5. No Foundation version any more
  6. Build one and deploy into two environments(for one premise and office 365)

Wednesday, September 2, 2015

BCS in Office 365


We can also call BCS an ORM(object relational map)
Secured store service is used to connect to external sources using different accounts apart from the organizational accounts

The main steps involved in devlopemt using BCS are:

  1. Creating external content types using designer or VS
  2. Importing external content type to BCS
  3. Configure the secured store
  4. Creating external lists
  5. Creating apps
Creation of App level ECT(external content type)

FileBackedMetadatCatalog loads External content type into it to easy access and also for creation of external lists
Specific finder is a method that is used to find one particular item, it is similar to a view on a list but i only returns one item on a list
We are have all the CRUD operational method for ECT to do
Sample code to connect to a list

Tuesday, September 1, 2015

Debugging Remote Event Recievers

  1. We must create a new azure service bus namespace using azure powershell
  2. The command give back a connection sting to connect to Azure environment with EndPoint
  3. Use this in visual studio for connecting to azure
  4. go to project properties
  5. inside that go to SharePoint tab
  6. Check the enable debugging via Azure service bus
  7. copy past the connection string that we got from command prompt
  8. insert a breakpoints and click on F5 for debugging

Remote event receivers in SharePoint 2013


The remote events supports

Site - Create, Move, Delete
List - Create, Delete
List schema - Create, Update, Delete
List Item - Create, Update, Delete, Move, CheckIn, UnCheckIn, CheckOut, AttachmentsAdded, AttachemntsRemoved, FileMoved, FileConverted
App - Install, Update, Uninstall

Some Impotent Points to be noted:
  • Remote event receivers call across the networks
  • After events use WCF(Windows communication foundation) call on remote web so that they do not block the sharepoint host nor delay the response back to the user
  • Remote event recievers will only workf if the concern list is present in App Web
  • SharePoint hosted apps doesnt support remote event receievers, its only provider hosted apps
  • IRemoteEventService an interface thats get inherited in remote event recievers
  • We have only two events called "ProcessEvent" which is a two way event and "ProcessOneWayEvent" for one way
  • Properties argument defines the event that has fired on a list item
  • We will be having only single entry point for all the events
  • Properties.ItemEventProperties is for an item events and Properties.ListEventProperties for list events
  • SPRemoteEventResult which is used to sent status back to SharePoint(used for sending information and also for canceling the events)


Before events example

After events example



  • App Life Cycle events are two way events
  • "ProcessOneWayEvent" never file in App related events
This are just brief points about remote event recievers.