Kushan Perera

As for all there are black and white sides of this model as well same as web parts and add-in models. This article will be discuss good and bad of it. Works for IoT (Internet of Things) Modern tend is accessing internet from any device user equipped with such as mobile, tab, laptop, desktop and so on. Even modern SharePoint team sites are responsive there are loopholes. If your requirement is more mobility centric, this would be better option. Users are still active with the legacy interface   If in a requirement users are still active with the legacy application and finds improvement in the application while its up and running. Developing from the scratch or migrating would be more expensive idea such as in this context. So what you could do is develop client side with SharePoint framework which is future proofed and allowing user to work on both. Need of long running operations and impersonation  If you have the requirement to run long running operations, this is not ideal method to

SharePoint framework would give you the experience which you have developed solutions client side such as Angular, Ember, JQuery, Knockout or etc. TypeScript will give you thinner layer between the SharePoint server and client side framework but it also not a mandatory fact. Decoupled Since its loosely coupled with the SharePoint server, it will be easy us to make upgrades easy and do the maintenance on presentation layer. Also it allows us to integrate power of the modern client side frameworks with greater user experience. All about client side scripts  All resides on the clients browser and it will give the same behavior while your felt with client side web development. You may be must to scripts enabled on the browsers to consume this services. It will include the strengths of add-ins and frameworks. Trust  SharePoint framework would take your current browsers authentication to authenticate against the SharePoint server. Other than in web parts and in apps model, you wont equipped

When it comes to develop on SharePoint framework, you are free to use environment as your preference . It may be open source tool or proprietary. In the legacy models of SharePoint development, its highly coupled with the Visual Studio, but when it comes to this model you can use VS Code, Sublime, Brackets, Notepad++, Eclipse or any developer as you love most. Following describes how to develop on SharePoint framework and you still like to develop with Visual Studio which is fully fledged development experience. Step 1: Scaffolded your Office template to your dev folder.  Reference:  SharePoint Framework Scaffolding  Step 2: Install Node.js to to your Visual Studio. Following link for VS 2015 Community and search for your version of VS. https://www.visualstudio.com/en-us/features/node-js-vs.aspx  Step 3: Create new project as below  Step 4: Select where your node JS files are placed. This should be place where you have scaffolded office templates Step 5: Select your startup file.

“SharePoint framework is all about typical web stack tooling” Node.Js Hosting platform Yeoman Generates templates Gulp Task management and automation TypeScript Typed JS VS Code Source editor..or you can select any other AngularJS/ Ember JS/ ReactJs/ Knockout..etc Client side framework You can be selected client side framework as your preference. Angular and Ember is full option frameworks. If you are a less experienced or finding for lightweight frameworks React or Knockout would be better preferences. SharePoint Framework tooling Legacy SharePoint tooling Node.js IIS/ .Net framework NPM NuGet Gulp MS Build Yeoman Visual Studio template selector TypeScript C# You can use any source editor as your preference. If you are mostly coupled with Visual studio you may need to install ‘node.js’ on it. If you free to develop with any development environment; VS code, Sublime, Brackets, Notepad++ ..etc are options.

This will be first step towards developing on SharePoint Framework. You will use npm to manage the packages and Yoeman  for generate SharePoint framework. [code language="powershell"] #check for existence of Node.js; install if following not returns version node -v #install Yeoman npm install -g yo #install generator #Office template https://github.com/officedev/generator-office npm install -g generator-office #move to your working folder or create folders if required cd D:\location mkdir "Folder Name" #Yeoman console..and pick your generator..it should be office generator yo #Or else directly call callout below yo office [/code] After execution of above code your can select default selections and also able to provide customized values if required. You can be used either Powershell or Cmder. But I prefer Cmder since it gives better experience if your are a windows user. But for other OS users, you can pick as you wish. Note: Now, your source template is generated(s

Introduction to SharePoint Framework SharePoint Framework for client-side development, easy integration with the Microsoft Graph and support for open source tooling . It's purely concentrated on integration of modern UX(User Experience) with SharePoint. As for announcements, this available since 3rd quarter of 2016 Allow developers to make use of the latest JavaScript frameworks like React and Angular. This opens doors towards open source development on SharePoint rather than sticking on to Windows and Visual studio. provides dramatically better experiences, performance, mobile support and more while broadening SharePoint developer ecosystem from .NET and beyond Available for existing SharePoint sites and can be include client side web parts into SharePoint pages. This introduces new page experience including page structure. What includes in SharePoint Framework? Capable of including enterprise mobility..responsive and also scale well with any device

  There are many configuration files in SharePoint app development. One point to notice from all is all are simple XML files. From many XML files, AppManifest plays major role with holding most of required metadata. Check "H:\TestSamples\SharePointApp2\SharePointApp2\AppManifest.xml" to continue.

There are mainly two hosting models which are “ SharePoint Hosted ” and “ Cloud Hosted ”. Cloud hosted model is subdivided into two models as “Provider Hosted” and “Auto-hosted.” SharePoint hosted Apps Contains only client side code and resources such as web pages and JavaScript’s etc. Severed up entirely by SharePoint environment Cloud hosted App hosting As mentioned, there are two variations in this those are provider-hosted and auto-hosted Both types has associated “remote web” which host app-start page and required resources Capable of hosting custom database to store app specific data Provider hosted apps Provider hosted apps with multi-tenancy creates complexity This separates app data from tenancy, so that user in an one tenancy cant access data in a separate tenancy (which is good for policies) Comparatively more cost and time to develop apps in provider hosted apps Auto hosted apps No involvement with scalability and data isolation which was

With the rise of cloud platform and cloud model (office 365), app model came into conversation with addressing the some of the drawbacks which was with SharePoint custom solutions. Even though there are many disadvantages with the App model solution designers go to this model with the requirement. Following few points better to know before jump into the model; W3wp.exe – SharePoint worker process which manages solutions which deployed as a farm solution SPUWorkerProcess.exe – worker process which manages solutions which deployed as a sandbox solution Since all the models which were before running inside the SharePoint, there is high couple and dependencies which can be accounted as a disadvantages. There is possibility of custom codes affect the processes and codes of SharePoint – scalability and environment risks Less ability to upgrade the SharePoint with the tightly coupled behavior and its complex behavior – high dependencies When code running with elevated pr

There may be many ways of creating views for SharePoint list, but following method would be most easiest and consistent way of achieving it as I found out. Create a new list or in an existing list,  find the "view" tab. And create new view as your desired. Go to schema.xml of the considered list on the solution. Include your fields as below in the <ViewFields> XML parent. [code language="xml"] <ViewFields> <FieldRef Name="LinkTitle"></FieldRef> <FieldRef Name="Date1" /> <FieldRef Name="Update" /> <FieldRef Name="Details" /> <FieldRef Name="Status" /> <FieldRef Name="Resolved1" /> <FieldRef Name="ResolutionDate" /> <FieldRef Name="ConfidenceLevel" /> <FieldRef Name="PHC" /> </ViewFields> [/code] If there is any filtering in data; you can include those filtering there. [code language="xml"] &