Microsoft Webinars on .Net sessions for March month

.Net sessions webinars

Take this opportunity and join us for exclusive webcasts with experts in the technology. Register now for the webinars listed below.

Session	Date
Windows Phone App to App Communication	March 5, 2014; 3:00 pm - 4:00 pm
Testing for Continuous Delivery with Visual Studio 2013	March 12, 2014; 3:00 pm - 4:00 pm
Agile project management using TFS	March 19, 2014; 3:00 pm - 4:00 pm
Scaffolding in ONE ASP.NET using Visual Studio 2013	March 26, 2014; 3:00 pm - 4:00 pm

Microsoft Dev Camps in Hyderabad

JOIN DEV CAMPS IN HYDERABAD TO BEGIN APP DEV

Microsoft Dev Camps are no-cost, fun, no-fluff events wherein developers get a chance to learn how to build great apps on Microsoft platforms from experienced developers.  Date: September 20, 2013 Time: 9:00 am to 6:00 pm Venue: Regenta One, 115/1, ISB Road, Financial District, Nanakramguda, Gachibowli, Hyderabad - 500 032.

http://www.microsoft.com/en-in/events/devcamps/all_events_hyderabad.aspx

SharePoint Code Analysis Framework (SPCAF)

Microsoft has recently coming up with new tool for SharePoint code review and analysis.This tool is in beta stage and is available for free and it is integrated with Visual Studio 2012. It can be download in the following link  Tool Download


What it can do? why it is better than FxCop and SPDisposeCheck?
SPCAF can analyze aseesmblies and also it take one more step in analyze all the XML code in SharePoint packages like ContentTypes, ListTemplates ,Features and all the other files like controls (.ascx), pages (.aspx) and master pages (.master), stylsheets (.css), JavaScript (.js).

Is this directly integrated?

SPCAF is directly integrated with  Visual Studio 2010/2012 to analyse SharePoint projects. 

It also provides a client application to analyze existing WSP packages.This can also be used in MS Build task.

Sharepoint 2013 databases

SharePoint 2013 has lot of improvements over SharePoint 2010.SharePoint 2013 has the following database.

The table illustrate the databases used in SharePoint 2013

Database	Description	Application Classification or Apps used By
App License	Stores the App licenses and permissions downloaded from the global marketplace.	App Management
Configuration Database	Contains data about all SharePoint databases, all Internet Information Services (IIS) websites or Web applications, trusted solutions, Web Part Packages, site templates, and Web application and farm settings specifi c to SharePoint 2013 Preview, such as default quota and blocked fi le types.	Core Databases
Central Administration Content	Content database for the Central Administration site.	Central Administration Content
Content Databases	Stores all site content, including site documents or fi les in document libraries, list data, web part properties, audit logs, sandboxed solutions, and usernames and rights. All the data for a specific site resides in one content database. Content databases can contain more than one site collection. Also stores data for Office Web Applications, if in use.
Machine Translation Services	Stores information about pending and completed batch document translations with file extensions that are enabled.	Machine Translation Services
Managed Metadata Service	Stores managed meta data and syndicated content types.	Managed Metadata Service
PerformancePoint	Stores temporary objects and persisted user comments and settings.
PowerPivot	Stores data refresh schedules and PowerPivot usage data copied from the central usage data collection database. PowerPivot for SharePoint 2013 requires SQL Server 2012 Analysis Services, Business Intelligence, or Enterprise Edition.
Project Server	Stores all the data for a single Project Web App (PWA), along with the following: All Project and Portfolio Management (PPM) data Time tracking and Timesheet data Aggregated SharePoint project site data
Search	Hosts the Search application confi guration and access control list (ACL) for the crawl component.	Search Administration
Secure Store	Stores and maps credentials such as account names and passwords.	Secure Store
Subscription Settings Service	Stores features and settings information for hosted customers. This database is not created by default but must be created by using Windows PowerShell or SQL Server.
State Service	Stores temporary state information for InfoPath Forms Services, Exchange, the chart web part, and Visio Services.
Usage and Health	Stores health monitoring and usage data temporarily, and also used for reporting and diagnostics. The Usage database is the only SharePoint database that can be queried directly and have schema modifi ed by either Microsoft or third-party applications.	Usage and Health Database
User Profi les		Stores and manages users and their social information.
Word Conversion	Stores information about pending and completed document conversions.
Word Automation	Stores information about pending and completed document conversions.

MySite.Master

MySite.Master in Sharepoint 2013

In Sharepoint 2013 new feature Mysite.master

Difference between Server,Ecma and Managed Client object model

Server objects , client objects  and Managed .Net client objects

S.No.	Ecma Script	Server Object Model	.Net Managed
1	SP.ClientContext	Microsoft.SharePoint.SPContext	Microsoft.SharePoint.Client.ClientContext
2	SP.Site	Microsoft.SharePoint.SPSite	Microsoft.SharePoint.Client.Site
3	SP.Web	Microsoft.SharePoint.SPWeb	Microsoft.SharePoint.Client.Web
4	SP.List	Microsoft.SharePoint.SPList	Microsoft.SharePoint.Client.List
5	SP.ListItem	Microsoft.SharePoint.SPListItem	Microsoft.SharePoint.Client.ListItem
6	SP.Field	Microsoft.SharePoint.SPField	Microsoft.SharePoint.Client.Field

SharePoint 2013 Development Models

Microsoft has provided 3 types SharePoint model solutions

1. Farm solution model
2. Sandboxed solution model
3. SharePoint app model

Farm solution model :

This model is basically known as the Fully Trusted Solution

(FTS) Model, which allows the developer to deploy customizations directly to global assembly cache (GAC) and web front end 15 hive or SharePoint Root folders. This option provides the greatest

power and flexibility in developing solutions for your SharePoint 2013 environment. 

This model was actually introduced in SharePoint 2007.

Sandboxed solution model

This model is known as Partially Trusted Solution (PTS) Model, this enables the developer to deploy customizations directly to an individual site collection. Partially trusted assemblies are executed in a separate isolated process, called the user code service. 

This model was introduced in SharePoint 2010 version.Microsoft has indicated that the sandboxed solution model is available in SharePoint 2013,but has been deprecated. This means you can still develop and use sandboxed solutions,but that they may not be upgradeable to SharePoint Next. Microsoft recommends moving away from the sandboxed solution model wherever possible and using the new app model in

conjunction with client object models and out-of-the-box web services

SharePoint app model

This is the new model introduced by microsoft in the latest version of SharePoint 2013 which is known as SharePoint app model. This model enables the developer to develop solutions that can be hosted in a corporate catalog and on the Microsoft Office Store Catalog.