SharePoint 2013 for Developer: Baby Journey (1)

Introduction to SharePoint 2013 for developer (1):

Introduction
a. SandBox is not the way to go for SharePoint 2013 or SharePoint Online 2013
 SharePoint 2013 App Model is the replacement for SandBox but SandBox still exists in SPS2013 for backward compatibility purpose.


SharePoint 2013 Farm\SandBox Solution:
 -CAB File with a .wsp extension -Container of files distributed as a unit (no change from previous version)
-Contains manifest with instruction for installer (no change from previous version)
-Use powershell to deployed
 Good News:
- Nothing changes on Farm\SandBox solution: so 0 relearning
- Bad News:
 - Because nothing change, 0 enhancement to that as well.


  File system in SharePoint 2013
 - same path as SharePoint 2010 or MOSS(2007) -c:\program files\ common files\ microsoft shared\web server extension\

NOTE: it contains 2 folders (14 and 15) - 14 : Is for 2010 and 15 is for 2013

WHY?
* SharePoint 2013 have 2 UI mode
** It is for Migration from 2010 to 2013 so solution can continue to work on sp2013

** Aside from migration, if your UI uses SharePoint 2010 UI Mode, it will use folder 14, -- if you use SharePoint 2013 UI mode it will use folder 15

* Why microsoft want to do that?:Microsoft found out that MOSS doesnt really work well for 2010, so Microsoft make it more robust by adding 14 folder in SP 2013

 Visual Studio 2012 
New Stuff:
- Replace package to Publish(reason MS want to have the same name as SPS 2013)
- You can published to SharePoint or File System: For file system it will built WSP file
- Replace wsp to cab format, u will see manifest.xml and dll files
 * In Manifest.xml, when you built Project for SharePoint 2013, it have SharePointProductVersion=15.
  - you can change to 14 means it will deploy the files into 14 folders and allow to be run if it is in 2010 UI Mode only.

Conclusion
App model is the way to go if you are going to do programming with SharePoint 2013 ONLINE. Even though you have invested heavily on SandBox solution, you can still use SandBox solution in SPS 2013. But because Microsoft invested heavily on APP Solution Model, you should also take note on moving to APP Solution for any future enhancement.

Comments

Unknown said…
Thanks for sharing! i also love developing part
July 9, 2013 at 9:22 PM
Kerl’s blog said…
You are welcome. I am unable to proceed to my next baby steps due to alot of projects but i will do my best to update the post.
September 9, 2013 at 12:04 AM
Post a Comment

Popular posts from this blog

SharePoint 2013: Distributed Cache Services

Image
What is Distributed Cache Services(DCS)? - It is a Platform Service, it runs at the Farm Level.   -- You can decide to run it on all servers in the farm or you can use it to run on a 1 or a couple of servers.   -- Suggest to have dedicate servers for DCS. - It provides in-memory cache for the entire farm. - It is based on Window Server App Fabric Distributed Caching. - It uses to cache Authentication Token(to avoid multiple authentication processes) and MySite Social Feeds. - DCS enable by default and allocate memory based on total memory on your server.   -- You should at least dedicate 50% of RAM or more just to the DCS service for overhead. What is it NOT : - It do not uses Window Azure Cache services and thus it cache on local server (no cloud). - It uses Window Server App Fabric version that comes together with the installer: You are not recommended download any version from Microsoft and upgrade it independently.  - You are not recommended go to the "C
Read more

File Structure (Part 1)

Image
There are few ways for people who arrange their folder structures and which i do not wish to invent it. My approach is to arranging my folder structures based on Features not by types What is Type? Angular have alot of types. for example, we have Controller, Services, Directives which are the commonly used. We do not wish to arrange our file structure like this: This file approach is suitable only for SMALL application, for enterprise application, we have tons of Modules and alot of programmers are working on different modules. So before we jump to multiple modules, we should first arrange our file structures by modules. Let say build an intranet application which consists with Employees modules, eTimelog modules and eLeave modules. I would like also to create main folder to stores all my framework (layout, sidebar, navigationbar, footer-bar etc on my site. here is my simple file structure: - common: putting all my modal, services\repositories\utilities class to be
Read more