Friday, March 13, 2015

TFS - Source Control

Advanced TFS

- Get latest / Check in / Undo changes
- CheckIn policy (Work Item, Code Analysis etc) we can write our own by extending it or buy third party
- Tasks templates (Agile, Scrum templates etc)
- Associate and Resolve Task Id while checkin
- ChangeSet (for relelase note, associate work item with changeset)
- Lable (Book mark of milestones eg. IPhone UX Implemented etc)
- Branching
- Merge code between branches
- Shelve / Unshelve - Move the new code in a safe location (Shelve) and it will not be compiled in builds and you can use the old code. First shelve and undo the undo pending changes.
During unshelve, we may have a conflict with the present code.
- Use the local/Server version/Auto Merge/Merge tool

Friday, February 20, 2015

PowerShell SharePoint Administration - Script samples

I always love and keep an eye on the SharePoint Administration. I have watched the MVA video training conducted by Christopher and his samples are in GitHub

If you are a developer, please have a look at it and understand and need to know some administration.
Download the SharePoint Administration scripts

Wednesday, January 28, 2015

Knockout Introduction

Today I conducted a session on KnockOut, which is a client-side MVVM JS library. Have a look at the below slide and can download for your reference. Its free for you :)

The audience are impressed about the two way communication and the page rewrite without refreshing the entire page.

You can develop a awesome Web page, SPA or Apps using knockout. I am sure you will love it.


Wednesday, October 1, 2014

SharePoint 2013 REST API calls using Fiddler

SharePoint 2013 REST API is the best choice to access server objects from client site. The easiest and more convenient way to test this is using Fiddler tool

The below are the two samples to demonstrate how to use Fiddler and pass header and body content to send request

Example 1: Add a list item (task) to a List (Tasks list)

Header 

ACCEPT: application/json;odata=verbose
Content-Type: application/json;odata=verbose
X-RequestDigest: 0xE2872916105EF8654E29E7295F06D7A0CA96847415B5AC010F00FE871BADC181D85783853ECA1C9002C402B675F2CC00C9312293668F261888E7B3694F138567,01 Oct 2014 18:39:40 -0000
Host: yourhost.com
Content-Length: 91

Body

{'__metadata': {'type':'SP.Data.TasksListItem'},
'Title': 'Let me in via Fiddler REST'
};



Example 2: Add a list to a Web

Header

ACCEPT: application/json;odata=verbose
Content-Type: application/json;odata=verbose
X-RequestDigest: 0x16F60B1D8E5FD4DEC53E3609823866DA3DD8BC187A2C4F8070B4761183FC2C60B974ECA083B2E5613A1019C79277B18B4EDDEB41E3452F2D43CCD01ACDAF3957,01 Oct 2014 19:41:49 -0000
Host: rmitscvpspqa02:2000
Content-Length: 191

Body

{ '__metadata': { 'type': 'SP.List' }, 'AllowContentTypes': true, 'BaseTemplate': 100,
    'ContentTypesEnabled': true, 'Description': 'My list description', 'Title': 'Test List from fiddler' }


To test it, go to SharePoint site and verify. Its cool :) 

Note : Where do I get the form digest value to include in my request?

As described on this page on MSDN, you can retrieve this value by making a POST request with an empty body to http://site/_api/contextinfo and extracting the value of the “d:FormDigestValue” node in the XML that the contextinfo endpoint returns.

Thursday, September 25, 2014

Solution deployment stuck on deploying

I got the deployment issue in visual studio and powershell scripts in farm solutions. Most of the solutions in the google are suggesting to do the following steps and I did and restarted the all the servers. But the issue continues. Fortunately I got the real reason after reviewing the sharepoint log file. So the lesson learned is "The reason may be anything and review your log file carefully"

The actions which I tried (not got the solution)

1.   Make sure SharePoint timer service should be started on all the servers (web front ends as well as app server)
2.   Try restarting the SharePoint Administration service on all the servers.
3.   Restart all the SharePoint servers
4.   Make sure that all the servers in farm are on the same time zone.
5.   Execute stsadm -o execadmsvcjobs on all the servers of the farm
6.   Cancel the deployment job by means of central administration, remove the solution and try to add the solution again & check the results.
7.   Check the status of the jobs by means of CA-timer job status or use te following command - stsadm -o enumdeployments   - This will give you the list of all the pending & active deployments.

Still had the error while cancel the deployment job using CA. The error thrown by CS is "Object reference not set to an instance of an object". This confuses me more and I started reviewing the sharepoint log file using ULS Viewer, and I got the real reason for this strange behaviour.

SharePoint Log Critical Error

Database full error on SQL Server instance 'XXX' in database 'SharePoint_Config'. Additional error information from SQL Server is included below.  Could not allocate space for object 'dbo.Tombstones'.'PK_Tombstones' in database 'SharePoint_Config' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.



Solution


Increased the DB size and the issue is resolved

USE master;
GO
ALTER DATABASE SharePoint_Config
MODIFY FILE
    (NAME = test1dat3,
    SIZE = 10240MB);
GO


or Use "SQL Management Studio" as shown below.