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

Developing SharePoint 2010
and Silverlight Web Parts –
Tips and Tricks
Ovidiu Becheș-Puia
SharePoint Developer
EBS Romania
ovidiu.beches@ebs.ro

@ itcampro # itcamp12 Premium conference on Microsoft technologies

ITCamp 2012 sponsors Architecture &
Best Practices


Agenda Architecture &
Best Practices

• SharePoint Developer Tools
• ASP.NET and Silverlight Web Parts
• SPG (SharePoint Pattern&Practices Guidance)
• Unit Testing in SharePoint
• DEMOS


Intro Architecture &
Best Practices

What means to me developing and working with SharePoint ?


Intro Architecture &
Best Practices


The SharePoint Developer Toolbox

TOOLS


TOOLS Architecture &
Best Practices

• SPM 2010


Best Practices

• ULS Viewer


Best Practices

• .NET Reflector / JustDecompile


Best Practices

• Fiddler2 / Firebug


Best Practices

• CKS – Community Kit for SharePoint


Best Practices

• SPSF – SharePoint Software Factory


Best Practices

• Linq to SharePoint DSL Extension for VS2010


Developing ASP.NET and Silverlight WebParts

WEB PARTS


Web Parts Architecture &
Best Practices


Best Practices

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….


Best Practices

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..


SharePoint 2010 Pattern & Practices Guidance

SPG


SPG 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: Service Locator pattern Architecture &
Best Practices


SPG: Service Locator pattern Architecture &
Best Practices

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


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

-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


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


SPG:M-V-VM Architecture &
Best Practices

• 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


Best Practices


Best Practices

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.


Best Practices

How about JavaScript / HTML5?


SPG: Repository Pattern Architecture &
Best Practices


SPG: Repository Pattern Architecture &
Best Practices

Choosing a SharePoint Data Access Technology


Unit Testing in SharePoint World

UNIT TESTS


UNIT TEST Architecture &
Best Practices

Only Integration Tests with MSTest
- Visual Studio 2010 SP1

SPListCollection – internal ctors.

Isolation Frameworks:
-Typemock – not free
-Pex and Moles – free


Best Practices

Mocking the ‘Principle of Isolation’


Best Practices

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 Sahil Malik

TDD + SharePoint ? Not worth it IMHO.


Best Practices

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 Sahil Malik

• Focus on scalability
• Writing some code
• Establishing roles within your team (overlap with IT
Pro guys)
• Training required
• large portions of XML


Best Practices

Pex and Moles - Peli de Halleux – Microsoft Research


Vă mulțumesc

Q&A


Conclusions Architecture &
Best Practices


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

Recommended

Recommended

More Related Content

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

Similar to ITCamp 2012 - Ovidiu Beches - Developing SharePoint 2010 and Silverlight web parts (20)

More from ITCamp

More from ITCamp (20)

Recently uploaded

Recently uploaded (20)

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