ITCamp 2012 - Ovidiu Beches - Developing SharePoint 2010 and Silverlight web parts

itcampro @ itcamp12 # Premium conference on Microsoft technologies

Developing SharePoint 2010 and Silverlight Web Parts –

Tips and Tricks

Ovidiu Becheș-Puia

SharePoint Developer

EBS Romania

[email protected]


Architecture &

Best Practices ITCamp 2012 sponsors


Architecture &

Best Practices

• SharePoint Developer Tools

• ASP.NET and Silverlight Web Parts

• SPG (SharePoint Pattern&Practices Guidance)

• Unit Testing in SharePoint

• DEMOS

Agenda


Architecture &

Best Practices Intro

What means to me developing and working with SharePoint ?


Architecture &

Best Practices Intro


TOOLS

The SharePoint Developer Toolbox


Architecture &

Best Practices

• SPM 2010

TOOLS


Architecture &

Best Practices

• ULS Viewer

TOOLS


Architecture &

Best Practices

• .NET Reflector / JustDecompile

TOOLS


Architecture &

Best Practices

• Fiddler2 / Firebug

TOOLS


Architecture &

Best Practices

• CKS – Community Kit for SharePoint

TOOLS


Architecture &

Best Practices

• SPSF – SharePoint Software Factory

TOOLS


Architecture &

Best Practices

• Linq to SharePoint DSL Extension for VS2010

TOOLS


WEB PARTS

Developing ASP.NET and Silverlight WebParts


Architecture &

Best Practices Web Parts


Architecture &


My GOLDEN RULE (GOAL)

It would be so much easier if we could avoid using

SharePoint server to develop Web Part / anything

The F5 Build/Deploy/Test cycle is slow….


Architecture &


When not to use SharePoint:

-if your WebPart does not use SharePoint calls

-use a simple ASP.NET Web Application – test harness

-statically declare WebParts in aspx – so no need to

handle personalisation

The F5 Build/Deploy/Test cycle is slowww..


SPG

SharePoint 2010 Pattern & Practices Guidance


Architecture &

Best Practices

(Coding) Challenges when creating enterprise

applications:

• Testability

– can you isolate your classes

• Flexibility

– Can you update or replace code without

recompiling

• Configuration

– How do you manage configuration settings?

SPG


Architecture &

Best Practices

(Coding) Challenges when creating enterprise

applications:

• Logging and exception handling

– How do you log ? Consistent across the team

• Maintainability

- How can you maintain code that is always

evolving

• Can your code run in the Cloud (Office 365)

- Without Full trust proxy

SPG


Architecture &

Best Practices

• Main patterns illustrated (with reference

applications in the SPG)

-Service Locator pattern

-MVP pattern (Model-View-Presenter)

-MVVM pattern (Model-View-ViewModel)

-Repository pattern

SPG


Architecture &

Best Practices SPG: Service Locator pattern


Architecture &

Best Practices SPG: Service Locator pattern

Mappings add on Farm level Can be added using only: -farm feature / CA Web App -console app

Mappings add on Site Coll. level

Get Service Locator -Site Collection (if SPContext ) -Farm


Architecture &

Best Practices SPG:MVP (Model-View-Presenter)

-MVP originated in early 1990s

-MVP is a derivative of MVC

-Two types of implementation – Passive View

– Supervising Controller

-Presenter assumes the functionality of the

MVC controller

-View is responsible for handling UI events

-Model becomes strictly a Domain Model


Architecture &

Best Practices SPG:MVP (Model-View-Presenter)


Architecture &

Best Practices SPG:M-V-VM

• Largely based on MVC

• Specialization of the MVP pattern known as

Presentation Model

• Build specifically for the WPF and Silverlight

• ViewModel is a “Model of the View”

-it extends the Model with Behaviours the View

could use

-Data binding between View and Model

-Passes commands between the View and Model


Architecture &



Architecture &


The Model - which provides a view-independent

representation of your business entities

The View - which is the user interface. It displays information

to the user and fires events in response to user interactions

The ViewModel - which is the bridge between the view and the

model.


Architecture &


How about JavaScript / HTML5?


Architecture &

Best Practices SPG: Repository Pattern


Architecture &

Best Practices SPG: Repository Pattern

Choosing a SharePoint Data Access Technology


UNIT TESTS

Unit Testing in SharePoint World


Architecture &

Best Practices UNIT TEST

Only Integration Tests with MSTest

- Visual Studio 2010 SP1

SPListCollection – internal ctors.

Isolation Frameworks:

-Typemock – not free

-Pex and Moles – free


Architecture &


Mocking the ‘Principle of Isolation’


Architecture &


TDD and SharePoint

-reducing the cost of change -in a typical SharePoint project, the portion where TDD is actually applicable is very small which is the writing code part

TDD + SharePoint ? Not worth it IMHO.

Sahil Malik

http://blah.winsmarts.com/2009-6-sharepoint_and_tdd.aspx


Architecture &


TDD and SharePoint a typical SharePoint project: • Customer communication and prototyping • Plenty of attention to the IT Pro side, where you

decide logical and physical layouts of your servers, networks, and your site collections

• A significant effort in branding • Focus on scalability • Writing some code • Establishing roles within your team (overlap with IT

Pro guys) • Training required • large portions of XML

Sahil Malik

http://blah.winsmarts.com/2009-6-sharepoint_and_tdd.aspx


Architecture &


Pex and Moles - Peli de Halleux – Microsoft Research


Q & A

Vă mulțumesc


Architecture &

Best Practices Conclusions