SharePoint Workflow Vs Microsoft Flow

Workflow	Microsoft Flow
Enterprise focused solutions	Focused on individual
Automation of business processes	Automate workflows connects with SaaS (Software As A Service)
Works within SharePoint framework	Integrate with business APPs
Can integrate with Visual Studio	Automated ACTIONS based on EVENTS
Permission based on list	Actions are intended to automate the personal processes of end users (Permission)
Workflows starts with an event within SharePoint	Flows are triggered by web hooks into external systems
Possible to debug / attach with processes	Flow can take data from External systems to SharePoint
	Automate digital life while accessing data from social feed
	Can use defined templates, expect new templates in future
Editable using SharePoint Designer	Browser based
	Development / Administration knowledge is not necessary

Hide DELVE / VIDEO icons in Office 365 SharePoint portal

There are a lot of icons in the RIBBON in SharePoint portals.

If we do not want to use those, we can disable using Settings.

We have to Go to 

Admin Center --> SharePoint Section

After we get SharePoint manage page,

Then we have to go to SETTINGS section.

To hide DELVE we have to DISABLE "Office Graph" option.

To Hide VIDEO we have to DISABLE "Streaming Video Service" option.

After SAVE and refresh the page. We wont be able to see DELVE icon and VIDEO icon.

Change SharePoint Title

When we need to change the SharePoint Title from the Site collection,
We can use PowerShell Command.

PS C:\Users\Administrator> $app = Get-SPWebApplication -Identity http://spsvr:1111

PS C:\Users\Administrator> $app.SuiteBarBrandingElementHtml = "<div class='ms-core-brandingText'></div>"
PS C:\Users\Administrator> $app.Update()
PS C:\Users\Administrator>

Now can see the Chaned TEXT. If we don't want anything we can set "EMPTY".

Alternative Access Mapping for a SharePoint Farm

We have to add Alternative Access Mapping for all application severs.

Then we have add Alternative Access Mapping for Intranet zone.

Other wise users getting FILE NOT FOUND ERROR.

Save SharePoint List as a Template giving an error

When we are going to save a SharePoint List with huge data, it gives an error.

Simply because of Data size.

So we have to increase template size using STSADM

It is easy.

SharePoint Credential Popup disabling

It was a so much trouble to me when working SharePoint to give "Credentials" always. Even we are not thinking about it, it takes considerable amount of time. So i have decided to avoid from it. 

Internet Explorer --> Internet Options --> Security --> Trusted Sites --> User authentication

Localization in SharePoint

It was a horrible week for me, because of a too critical task, i.e.LOCALIZATION

Finally i was able to do it :) :) :)

*** Added "ChanaApp.resx" to App_GlobalResources folder in [Port] folder
*** Added "ChanaApp.nl.resx" to same folder
*** Added a label to .ASPX page
*** Set the Expression of the label, set the TEXT property using "Resources"

*** If only one page we can use
 protected override void InitializeCulture()
        {
            string[] languages = HttpContext.Current.Request.UserLanguages;
            string language = languages[0].ToLowerInvariant().Trim();

            string selectedLanguage = language;
            Thread.CurrentThread.CurrentCulture =
                CultureInfo.CreateSpecificCulture(selectedLanguage);
            Thread.CurrentThread.CurrentUICulture = new
                CultureInfo(selectedLanguage);
            base.InitializeCulture();
        }

*** If for total web application then we have to use
protected void Application_BeginRequest(object sender, EventArgs e)
        {
            string[] languages = HttpContext.Current.Request.UserLanguages;
            string language = languages[0].ToLowerInvariant().Trim();
            string selectedLanguage = language;
            Thread.CurrentThread.CurrentCulture =
                CultureInfo.CreateSpecificCulture(selectedLanguage);
            Thread.CurrentThread.CurrentUICulture = new
                CultureInfo(selectedLanguage);
        }
in GLOBAL.ASAX file.
*** Change the Culture of browser will change the TEXT in the label

Best Practices in SharePoint Development

1. When user creates a Webpart the UserControl should be placed in ~/ControlTeamplates folder
   
2. To identify SharePoint content within VS 2010
   
   1. Server Explorer à SharePoint Data Connections à Lists, Tasks, Calendar        
      
3. To add a workflow feature
   
   1. Template/1033/Workflows (can do using VS 2010 navigation)
      
4. After create a feature
   
   1. Rename chanaka.wsp as chanaka.wsp.cab
      
   2. Open as zip file
      
   3. Check about automatically created,
      
      1. Public key
         
      2. Solution id
         
      3. Feature id
         
5. When want to add Images to SharePoint portal
   
   1. Right click on solution VS 2010 server explorer
      
   2. Add à Sharepoint "Images" Mapped Folder
      
   3. It will be placed in (14 hive) SharePoint root à TemplateàImages
      
6. When we add a SPI (SharePoint Project Item) it will creates (Eg:- A Webpart name as chanaka)
   
   1. Element.xml (List ID, URL, Property Name, Webpart group)
      
   2. Chanaka.webpart (Name / Description)
      
   3. Chanaka.feature (Better to set Scope = "Site" )
      
      1. New UI in VS 2010 to work with
         
         1. Manifest.xml
            
         2. Dependencies
            
         3. SPI View
            
      2. Connect as a Event Receiver
         
         1. Right click on feature name in VS
            
         2. Add a Event Receiver
            
         3. Write the logic in one of event (Eg:- Feature Activated)

Recover Sharepoint Documents from backedup DB

We have lost our sharepoint portal + all other data bases.
Then we had to get data from our backup DB.
To get this data i have written a application.
It gets all files other than images (sharepoint) & unwanted files.
This also create folder structure according to portal.

Simple application :) :) :) :)

Download Direct Application

Download App through megashare

Why TFS portal webparts throwing an error - [Solution]

When we have configured sharepoint webportal for TFS, sometimes is throws an error when displaying "Project Dashboard" & "My Dashboard", all webparts displaying as missing components.


This is because, we have lost all webparts (basically dll's that renders webparts).
What we have to do is,
(1) Central administration --> Operations --> Solution management --> tswawebpartcollection.wsp --> DEPLOY




(2) Central administration --> Application Management --> Manage Web Application Features --> Visual Studio Team Foundation Server Configuration --> ACTIVATE



Now refresh your page :)

What we can do using TFS

We can do all in ALM (Application LifeCycle Management)

1. Source Control
2. Build automation
3. sharepoint integration
4. Process integation (Agile/CMMI)
5. Bug tracking
6. Reporting
7. Testing

TFS include management of
1. Task
2. Bug
3. Issue
4. Change Request
5. Requirement gathering
6. Review
7. Risk
8. Test case

Deploy 40 templates (.wsp solution) to sharepoint

first go to
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\BIN

then type
stsadm –o addsolution –filename ApplicationTemplateCore.wsp

stsadm –o deploysolution –name ApplicationTemplateCore.wsp -allowgacdeployment -local

stsadm -o copyappbincontent

then go to central administration --> Operations --> Solution management

You can see your solution there(ApplicationTemplateCore).

Now you have to add your necessary templates...
Same as early
stsadm –o addsolution –filename ApplicationTemplateCore.wsp
stsadm –o deploysolution –name ApplicationTemplateCore.wsp -allowgacdeployment -local

Now go to central administration with a hope !
Create new site collection -->
Under application templates --> you will have your template(s)

:)

How to install Sharepoint on Windows 7

This is a good article.

http://community.bamboosolutions.com/blogs/bambooteamblog/archive/2009/05/07/installing-wss-3-0-moss-sp2-on-windows-7-rc.aspx

Sharepoint in Sinhala

Many developers had difficulties to implement Sharepoint in their own language.
In srilanka we had same issue.
So we worked hard & finally we got the results.

Sharepoint Webpart Concepts

In order to create WSS-style Web Parts, you must have a dependency on the Microsoft.SharePoint.dll and you must inherit from the WebPart base class in the Microsoft.SharePoint.WebPartPages namespace.

In order to create ASP.NET-style Web Parts, you have a dependency on System.Web.dll and inherit from a base class named WebPart in the System.Web.UI.WebControls.WebParts namespace.

When creating WSS 3.0 Web Part pages, you should use the WebPartZone control defined in the Microsoft.SharePoint.WebPartPages namespace. You do not want to use the WebPartZone control contained within ASP.NET 2.0.

Different controls contained in a WSS-style Web Part page

The preferred way to create Web Parts for WSS 3.0 sites is to create the ASP.NET style WebParts. As discussed before, this means inheriting from the WebPart base class in the System.Web.UI.WebControls.WebParts namespace and overriding the RenderContents method.

Sharepoint Standard Versus Enterprise Edition

MOSS 2007 comes in both Standard and Enterprise Editions. Based on the needs we can choose to implement Standard Edition and upgrade to Enterprise Edition at a later time, or
immediately implement Enterprise Edition with all of its additional features.
Although there are many small differences between the two editions, the following are
the significant features included in Enterprise Edition but not in Standard Edition:

Excel Services
This feature provides access to Excel spreadsheets through a web browser and
offloads the calculations to the server. It makes only specific areas of the spreadsheet
visible to users, and ensures that there is “one version of the truth,” since
only specified users can modify the underlying data.

Report Center
This is a site provided out of the box that has been designed to simplify the management
of reports and data connections.

Business Data Catalog
This feature is a simplified way to bring data from external sources into Share-
Point without costly custom development. With it, users do not need to access
multiple systems to view the data they need—it is all available from one common
interface provided by MOSS.

Business Data Search
This feature allows users to search data that has been stored in separate systems
exposed through MOSS (such as those connected via the Business Data Catalog).

Forms Services
You can create forms within Microsoft Office InfoPath 2007 and publish them to
SharePoint using Forms Services, allowing users without the InfoPath client to
complete forms entirely through their web browsers.

Add an item to dropdown in sharepoint ListItem

Finally we will get

Sharepoint 2010 Overview

It's time to have a look new features that we want in sharepoint !!!

1. Look & Feel (Ribbon Control)
   
2. Multi document Checkout + avoid from post backs
   
3. Nice pop-up windows than response.redirects J
   
4. Direct uploading & showing images from your computer to sharepoint
   
5. SilverLight webpart
   
6. Nice themes like "PowePoint Theme"
   
7. Visio services running with sharepoint services (Visio is not necessary)
   
8. Fully rich Sharepoint Designer
   
9. Entities to connect SQL,LOB with Edit/Delete functions (OOB)
   
10. Direct connect to the office tools like Office 2010 with a click J
    

Infopath data retrieve with Sharepoint

SPSite objSite = new SPSite("http://sharepointsvr:123/");
SPWeb objWeb = objSite.RootWeb;
SPList objList = objWeb.Lists["Participant"];
SPQuery objQuery = new SPQuery ();
SPListItemCollection objCollection = objList.GetItems(objQuery);
SPListItem objItem = objCollection[0];
SPFile objFile = objItem.File;
byte[] xmlFormData = objFile.OpenBinary();
XPathDocument ipForm = null;
using (MemoryStream ms = new MemoryStream(xmlFormData))
{
ipForm = new XPathDocument(ms);
ms.Close();
}
XPathNavigator ipFormNav = ipForm.CreateNavigator();
XPathNavigator nodeNav = ipFormNav.SelectSingleNode("/my:myFields/my:fldFamilyName", GetFormNSM(ipForm));
string strValue = nodeNav.InnerXml;
Response.Write(strValue);


//XML Namespace Creator

private XmlNamespaceManager GetFormNSM(XPathDocument ipForm)
{
const string strMYNamespacePrefix = "my";
const string strMYNamespaceURI = "http://schemas.microsoft.com/office/infopath/2003/myXSD/2009-06-25T10:50:10";

const string strDIRNamespacePrefix = "d";
const string strDICNamespaceURI = "http://schemas.microsoft.com/sharepoint/soap/directory/";


XPathNavigator formAccess = ipForm.CreateNavigator();
XmlNamespaceManager namespaceMngr = new XmlNamespaceManager(formAccess.NameTable);
namespaceMngr.AddNamespace(strMYNamespacePrefix, strMYNamespaceURI);
namespaceMngr.AddNamespace(strDIRNamespacePrefix, strDICNamespaceURI);

return namespaceMngr;
}

RunWithElevatedPrivileges in sharepoint

When we try to get data from a document library that is not assigned for current user, we are getting this error.

Solution is:::::

SPSecurity.RunWithElevatedPrivileges(delegate()

{

…

//any code that we have to use

});


Sometimes even we add this delegate still it's not working.
That's because the object we are using made without elevated privileges.
(Ex:- We are creating SPWeb under the delegate, but the SPSite(parent object) object is outside the delegate, then we won't get chance to access data)