Showing posts with label Sharepoint Online. Show all posts
Showing posts with label Sharepoint Online. Show all posts

Monday, November 4, 2013

o365 Sharepoint Online Branding

For the Sharepoint Saturday Chicago on Nov 2nd 2013 @the Hard Rock Hotel, downtown Chicago, I spoke on one of my favorite topics : o365 SP2013 Online Branding - How to make your SP online site not look like Sharepoint.

I had worked on gathering some good demos and the audience found it valuable. The public site that I showcased in my presentation is https://sponlinedemo-public.sharepoint.com/ , it is a carousel based site with static images as of now but can be easily changed to getting the images from the library. Well this site does not look like this was built on Sharepoint.. and guess what.. IT IS!









Here is the session details and deck from my presenation.






 
                         


 

Monday, February 25, 2013

Custom Site Provisioning - SP2013 way....

Before I move on to the  content for my blog today .. here's some importnant information..SP2013 preview is ending soon to give way to the live version of SP2013 on the cloud ( o365)
 
O365 launch event info below. Please Sign up to see the new stuff.

Virtual Launch Event on February 27th 2013 as Microsoft celebrates the availability of a major new release coming to Office 365 for businesses.  Demo of new features in enterprise social and show how this has transformed the full Office experience you know into an always up-to-date service. Some real-world stories from customers about their move to the cloud. 
 
Now coming back to code....
 
Recently I had a requirement to do some feasibility study for SP2013 for sandboxed solutions. Well as we all know Microsoft has deprecated sandboxed solutions in o365 2013
This means that the functionality will still be available for use in SharePoint 2013, but primarily for backwards compatibility with existing solutions built using the sandbox solution approach.
 
Microsoft's guidance is that if you are building new applications that in the past you would have deployed as sandbox solutions, you should use the new App model for those solutions instead of using sandbox solutions.
 
More info on an article here...
 
Some SharePoint components are used in end-user scenarios but do not have any equivalents in the SharePoint app model. For these you must use farm solutions.

Well the requirement in this case is to "Create a custom user interface to provision a sub site based off a custom template, add some details to the site and add users"

Well - I plan to try this as an app too.. but from the looks of it if I want to create a custom web Template this is not supported. Hence, my first reaction is to create a Sandbox solution.

Upload a custom SP 2013 Site template in the solutions gallery!

 
 
 
 
 


CODE :
 using System;  
 using System.ComponentModel;  
 using System.Web.UI;  
 using System.Web.UI.WebControls;  
 using System.Web.UI.WebControls.WebParts;  
 using Microsoft.SharePoint;  
 using Microsoft.SharePoint.WebControls;  
 using Microsoft.SharePoint.Client;  
 using System.Collections.Generic;  
 using Microsoft.SharePoint.Navigation;  
 namespace SharePointProject1.CreateSubSite  
 {  
   [ToolboxItem(false)]  
   public partial class CreateSubSite : System.Web.UI.WebControls.WebParts.WebPart  
   {  
     string AccountGroup = "";  
     protected override void OnInit(EventArgs e)  
     {  
       base.OnInit(e);  
       InitializeControl();  
     }  
     protected void Page_Load(object sender, EventArgs e)  
     {  
       AccountGroup = txturl.Text + " Account Group - Contributor";  
       // Create more gropups based on requirements  
     }  
     protected string GetCustomTemplate(SPWeb web)  
     {  
       SPWebTemplate SiteTemplate = null;  
       // Find correct template  
       foreach (SPWebTemplate wt in web.GetAvailableWebTemplates((uint)1033)) // for EN-US use LCID 1033, http://msdn.microsoft.com/en-us/goglobal/bb964664  
       {  
         if (wt.Title == "AccountSiteTemplate")  
         {  
           SiteTemplate = wt;  
           break;  
         }  
       }  
       return SiteTemplate.Title;  
     }  
     protected SPWebTemplate GetCustomSiteTemplate(SPWeb web)  
     {  
       SPWebTemplate SiteTemplate = null;  
       // Find correct template  
       foreach (SPWebTemplate wt in web.GetAvailableWebTemplates((uint)1033))  
       {  
         if (wt.Title == "AccountSiteTemplate")  
         {  
           SiteTemplate = wt;  
           break;  
         }  
       }  
       return SiteTemplate;  
     }  
     private void CreateSPGroup(SPWeb newWeb)  
     {  
      //  AccountGroup = txturl.Text + " Account Group - Contributor";  
       SPGroup groupContributor = newWeb.SiteGroups[AccountGroup];  
       SPRoleDefinition roleDefinitionContributor = newWeb.RoleDefinitions.GetByType(SPRoleType.Contributor);  
       SPRoleAssignment roleAssigmentContributor = new SPRoleAssignment(groupContributor);  
       roleAssigmentContributor.RoleDefinitionBindings.Add(roleDefinitionContributor);  
       newWeb.RoleAssignments.Add(roleAssigmentContributor);  
       lblStatus.Text += "</br>Subsite Groups successfully created!!</br> ";  
     }  
     private void AddUsersToGroups(SPWeb newWeb)  
     {  
      //  AccountGroup = txturl.Text + " Account Group - Contributor";  
       SPUser spUser = newWeb.EnsureUser(txtContributor.Text);  
       if (spUser != null)  
       {  
         SPGroup spGroup = newWeb.Groups[AccountGroup];  
         if (spGroup != null)  
           spGroup.AddUser(spUser);  
       }  
       txtSiteDesc.Text = "";  
       txtSiteName.Text = "";  
       txturl.Text = "";  
       lblStatus.Text += "</br>User Successfully added to the group! ";  
       lblStatus.ForeColor = System.Drawing.Color.Green;  
     }  
     protected void Button1_Click(object sender, EventArgs e)  
     {  
       using (SPSite site = new SPSite(SPContext.Current.Web.Url))  
       {  
         using (SPWeb web = site.OpenWeb())  
         {  
           if (string.IsNullOrEmpty(txturl.Text))  
             txturl.Text = "Demo";  
            if (string.IsNullOrEmpty(txtSiteName.Text))  
             txtSiteName.Text = "Demo";  
            try  
            {  
              web.AllowUnsafeUpdates = true;  
              web.SiteGroups.Add(AccountGroup, web.CurrentUser, web.CurrentUser, string.Empty);  
              SPWeb newWeb = site.AllWebs.Add(txturl.Text, txtSiteName.Text, txtSiteDesc.Text, 1033, GetCustomSiteTemplate(web), true, false);  
              newWeb.Description = " New Account site created!!";  
              lblStatus.Text = "Subsite successfully created!! " + "<a href ='" + newWeb.Url.ToString() + "'> New Subsite Link </a> ";  
              CreateSPGroup(newWeb);  
              AddUsersToGroups(newWeb);  
              newWeb.Dispose();  
              web.Dispose();  
            }  
            catch (Exception ex)  
            {  
              lblStatus.Text = "Exception Occured! Error message : " + ex.Message.ToString();  
              lblStatus.ForeColor = System.Drawing.Color.Red;  
            }  
           finally  
           {  
             web.AllowUnsafeUpdates = false;  
           }  
         }  
       }  
     }  
     protected void txtTemplate_Click(object sender, EventArgs e)  
     {  
       using (SPSite site = new SPSite(SPContext.Current.Web.Url))  
       {  
         using (SPWeb web = site.OpenWeb())  
         {  
           txtSubsiteTemplate.Text = GetCustomTemplate(web);  
         }  
       }  
     }  
   }  
 }  


Upload the sandbox soultion to the solutions gallery

 
 


 



Add the web part top a page and start provisioning sites your way in SP2013...!!

Note:
In case you are thinking about the cool User Interface... This is because I have chosen a Theme - Orbit.. This is super simple and easy...
Please go through my blog to see how this can be done!



 
 

Thursday, February 7, 2013

My First NAPA App - o365 SP2013 Preview

What is NAPA ???

 
NAPA is the easiest way to start building apps for the new Cloud App Model introduced in SP2013. You can think of it as a super simple development environment with no installations on the local machines & an online companion to Visual Studio. This is a free app for SharePoint to facilitate rapid application development.

App Model - what is it?

Within the last decade the Internet has evolved tremendously from simple pages to robust social sites that support loosely coupled yet highly integrated third party apps. From the beginning of SharePoint to today, SharePoint has also made significant changes from being a portal site to our newest release. SharePoint 2013.
 
For the developer and ultimately benefiting the user, SharePoint 2013 has made a significant investments to provide a new way to bring custom solutions to users with the new web standards based cloud app model that are easily discoverable and yet will give IT and developers peace of mind knowing that they can scale, are safely isolated from SharePoint yet can leverage the full capabilities of SharePoint.
 
 
One of the new features of SharePoint 2013 development model is the App model. Using this new App model, developers can easily extend SharePoint 2013 and build great apps that integrate with the numerous services. Today web is filled with many services i.e.
Financial data, WikiPedia, Bing Search and Maps etc.  Even SharePoint, Dynamics CRM can provide data for us. This model make it easy for developers to integrate these services into SharePoint for consumption and build solutions that solves specific user needs.

Apps enable SharePoint 2013 users to extend the capabilities of SharePoint 2013 to address specific business needs by allowing users to connect to data and services both from within an organization as well as in the public cloud.

How is it different that what was offered before in SP2010?

The new cloud app model gives the developer the freedom of choice in how they implement apps for SharePoint. No longer are you tied to writing on top of the SharePoint platform, now you can write along-side it with the tools and web hosting platforms of your choice… Whether it is on premise or in the cloud… Whether the platform is IIS/ASP.NET, a part of the Windows Azure family of hosting options or a non-Microsoft web hosting platform.  The final choice is up to you.
 
 
Now we have had WebParts and the like for SharePoint for some time and we can provide similar experiences creating full-trust and sandbox solutions.  The issue is that these apps are tightly integrated with the platform and require some amount of touch to insure as technology advances that our customizations can advance with it.  This is were apps differ, apps are loosely coupled and not dependent on the SharePoint as a platform, but dependent on SharePoint as a service. Apps execute “off-server”, hence they don’t actually run on the SharePoint box but instead are hosted in their own hosting environment which could be the browser, a Window Azure service, ASP.NET or even a non-Microsoft web hosting platform such as Linux or Amazon Web Services.

 
 Life cycle for app for SharePoint development :

 

Developement - Let's build our very first Napa App on the cloud:

Create a new SP2013 preview account by following the instructions here
 
The Team site that is provisioned by default, Let's try to add NAPA app.
 
 
 
 
 
 
 
 
 
You will see that it does not get added. Don't panic yet,  Go to see the details of the error.
 
So we need a site with a developer template / developer features turned on. Hence I go ahead and create a new developer Site. 
 
 
 
 
 
And YAY it gets added !!
 
 
 
 
 
Now, Let's create a new Project:
 
 
 
 
 
 
 
 
 
 
Some changes that we need to do in the Default.aspx
 

 


And Now changes to App.js file

To Change the look and feel of the site changes can be done to our App.css

The O/P looks as below:



I added the code for an embedded Bing map


 <p>A simple embedded map.</p>  
    <iframe width="400" height="300" frameborder="0" scrolling="no" marginheight="0" marginwidth="0"  
      src="http://dev.virtualearth.net/embeddedMap/v1/silverlight/aerial?zoomLevel=10&center=47.5_-122.5&pushpins=47.5_-122.5"/>  

 
The app is ready for testing and starts appearing in your gallery

 
 

A couple of items that I tried to add to my NAPA app are below for reference using JavaScript Client Object Model

1. Add a People picker to your page:

 Changes to the App.js file

 
Changes to the default.aspx file  

2. Add a Embedded Bing Search to your page:

Add the below to Deafult.aspx


Important links for reference

MSDN  

Wednesday, July 18, 2012

Best Practices.. Sharepoint

A collection of all best practices for SharePoint is collated below logically grouped :


General:





Code :










Customizations:





Usage :






Design and Architecture:






Migration:





Security:




Monday, July 9, 2012

Sharepoint Online (o365 ) - Architectural Considerations


Sharepoint Online :   It is available at all times, It is constantly upgraded and it saves you loads on hardware and operational costs - isn't this what the cloud is all about? Then why is there a hesitation when we talk about the cloud to the clients and our trusted partners? Security of data, limited feature set, cost of migration of the existing environment, adoption, governance..?

Perhaps the greatest threat to adoption of Office 365 is not competitors, but rather reluctance of organizations to move data and applications from on-premise servers and clients to Microsoft’s cloud. Well... with all the tension free life of no-maintenance of the hardware and software comes a tradeoff of the rich feature set which is slightly compromised in the online version and the security of your hosted data concerns.

I spend a lot of time over the net searching for a central location to get the feature set comparison and was lost in the results. Finally, I decided to have all the information collated at one glance to help me in my understanding. The primary ones which shape the architecture of your o365 SharePoint online portal are mentioned here with details on the others tabled below. Hope this helps you as well.

Microsoft decided to exclude certain functionality from SharePoint Online at the time of launch in June 2011. In short, the most important capabilities missing in SharePoint Online are listed below which is very imnportant for architects like me to design a new portal or migrate the existing :


S. No. Features Not Supported
1 FAST Search 
2 Advanced Search Configuration 
3 Record Center - Last I heard this was being offered in the Dedicated online version.
4 Word Automation Services 
5 Business Intelligence Center 
6 Secure Store Service 
7 Web Analytics 
8 Mail Enabled Document Libraries are not supported, impacting Scanners & Scanner software
9 Locally installing custom software - Any third party agent cannot be run on the server.
10 Advanced public facing web sites 
11 Vanity URLs are not supported for intranet zone sites. They can only be applied to your SharePoint Online Public Website.
12 BCS within SharePoint Online does not support a direct connection to SQL Azure. A WCF endpoint is required.
13 Access reporting is not supported by SharePoint Online Access Services because SQL Server Reporting Services (SSRS) is not currently enabled for SharePoint Online. Access reporting requires SSRS.
14 SharePoint Online does not support auditing capabilities to log the opening and downloading of files in a document library.
15 SharePoint Online does not support PerformancePoint Services.
16 Editing the Public Website with SharePoint Designer is not supported.

Feature SharePoint 2010 Server SharePoint Online 
Developer Dashboard Yes No
SharePoint Timer Jobs Yes No
Business Data Integration with the Office Client Yes No
Business Connectivity Services Profile Page Yes No
Audit Opening and Downloading Yes No
Records Center Yes No
Word Automation Services Yes No
Business Intelligence Center Yes No
Chart Web Parts Yes No
Data Connection Library Yes No
PerformancePoint™ Services Yes No
Dashboards Yes No
Decomposition Tree Yes No
Excel Services and PowerPivot for SharePoint Yes No
Advanced Content Processing Yes No
Tunable Relevance with Multiple Rank Profiles Yes No
Business Intelligence Indexing Connector Yes No
SharePoint 2010 Search Connector Framework Yes No
Contextual Search Yes No
Deep Refinement Yes No
Federated Search Yes No
Query Suggestions, "Did You Mean?” and Related Queries Yes No
Relevancy Tuning Yes No
Rich Web Indexing Yes No
Enterprise Scale Search Yes No
Windows 7 Search Yes No
Similar Results Yes No
Thumbnails and Previews Yes No
Visual Best Bets Yes No
Advanced Sorting Yes No
Web Analytics Yes No


Feature SharePoint 2010 Server SharePoint Online 
Office Web Apps integration Yes – separate installation Yes – comes preconfigured


Feature SharePoint 2010 Server SharePoint Online 
Secure Store Service Yes Yes – Tenant Level
Public Website No Yes (one per tenant)

Feature SharePoint 2010 Server SharePoint Online 
Ask Me About Yes Yes
Blogs Yes Yes
Colleague Suggestions Yes Yes
Colleagues Network Yes Yes
Discussions Yes Yes
Enterprise Wikis Yes Yes
Keyword Suggestions Yes Yes
Memberships Yes Yes
My Site: My Content Yes Yes
My Site: My Newsfeed Yes Yes
My Site: My Profile Yes Yes
Note Board Yes Yes
Organization Browser Yes Yes
Photos and Presence Yes Yes
Ratings Yes Yes
Recent Activities Yes Yes
Status Updates Yes Yes
Tag Clouds Yes Yes
Tag Profiles Yes Yes
Tags Yes Yes
Tags and Notes Tool Yes Yes
Wikis Yes Yes
Client Object Model (OM) Yes Yes
Event Receivers Yes Yes
Language Integrated Query (LINQ) for SharePoint Yes Yes
Solution Packages Yes Yes
REST and ATOM Data Feeds Yes Yes
Ribbon and Dialog Framework Yes Yes
Silverlight Web Part Yes Yes
Workflow Models Yes Yes
Access Services Yes Yes
Browser-Based Customizations Yes Yes
Business Data Connectivity Service Yes Yes
External Data Column Yes Yes
Business Data Web Parts Yes Yes
External Lists Yes Yes
SharePoint Designer 2010 Yes Yes
Forms: Out-of-Box workflows and customization through SharePoint Designer 2010 Yes Yes
InfoPath Forms Services Yes Yes
Sandboxed Solutions Yes Yes
Workflow Yes Yes
Microsoft Visual Studio® 2010 SharePoint Developer Tools Yes Yes
Windows 7 Support Yes Yes
Workflow Templates Yes Yes
SharePoint Service Architecture Yes Yes
In-Place Legal Holds Yes Yes
Document Sets Yes Yes
Metadata-driven Navigation Yes Yes
Multi-Stage Disposition Yes Yes
Rich Media Management Yes Yes
Shared Content Types Yes Yes
Support for Accessibility Standards Yes Yes
Content Organizer Yes Yes
Unique Document IDs Yes Yes
Managed Metadata Service Yes Yes
Excel Services Yes Yes
Visio Services Yes Yes
Calculated KPIs Yes Yes
Best Bets Yes Yes
Extensible Search Scale Yes Yes
Duplicate Detection Yes Yes
Metadata-Driven Refinement Yes Yes
Mobile Search Experience Yes Yes
People and Expertise Search Yes Yes
Phonetics and Nickname Search Yes Yes
Recently Authored Content Yes Yes
Search Scopes Yes Yes
Single Site Collection Search No Yes
Site Search Yes Yes
Click-Through Relevancy Yes Yes
View in Browser Yes Yes
Basic Sorting Yes Yes
SharePoint Lists Yes Yes
Web Parts Yes Yes
Improved Governance Yes Yes
Large List Scalability and Management Yes Yes
Multi-Lingual User Interface (MUI) Yes Yes
Permissions Management Yes Yes
Quota Templates Yes Yes
Connections to Microsoft Office Clients Yes Yes
Audience Targeting Yes Yes
Cross-Browser Support Yes Yes
External sharing No Yes
SharePoint Ribbon Yes Yes
Mobile Connectivity Yes Yes
SharePoint Workspace 2010 Yes Yes
Out-of-the-Box Web Parts Yes Yes
Scalability Yes Yes
Templates Yes Yes
Accessibility Yes Yes
Configuration Wizards Yes Yes


An exact list of all capabilities missing from the SharePoint online offering is listed in the current Service Description. Over the upcoming service releases, scheduled every 90 days, Microsoft will begin introduce some of the aforementioned features and I am hopeful that the rich feature set is completely available in the online version as well.



Security of Data : Some countries and organizations have legal limitations on where their data can be hosted, this primarily is applicable for some sensitive data which is of a specific category. Microsoft’s Data Centers are located throughout the world and this might be a legal issue if you chose to go this route.  If your organization’s data cannot leave your region or continent, then Office 365 is not the solution for you currently.

Reference :
MSFT site
SharePoint Online Architectural Considerations