Search

This article is Part 0 of the series “XNA for Silverlight developers”:

• XNA for Silverlight developers: Part 0 - Why should I care?
• XNA for Silverlight developers: Part 1 - Fundamentals
• XNA for Silverlight developers: Part 2 - Text rendering
• XNA for Silverlight developers: Part 3 - Animation (transforms)

Introduction

Around the time the first Windows Phone 7 devices were released to the market, one popular sentence you heard was "every Silverlight developer is a Windows Phone 7 developer" – and that's true. Silverlight is Microsoft's main platform to do Windows Phone 7 development, and every desktop Silverlight programmer will feel comfortable in the new mobile programming environment instantly. Sure there are differences and libraries specific to the devices, but you won't have to learn a new programming language or new ways to define your UI, and you can use the same development environment you've been using for normal Silverlight development all the time.

This article is Part 1 of the series “Beginners Guide to Visual Studio LightSwitch”:

1. Beginners Guide to Visual Studio LightSwitch (Part – 1) – Working with New Data Entry Screen
2. Beginners Guide to Visual Studio LightSwitch (Part – 2) – Working with Search Screen
3. Beginners Guide to Visual Studio LightSwitch (Part – 3) – Working with Editable DataGrid Screen
4. Beginners Guide to Visual Studio LightSwitch (Part – 4) – Working with List and Details Screen 
5. Beginners Guide to Visual Studio LightSwitch (Part – 5) – Working with Custom Validation 

In my previous post “Introduction to Shapes in Silverlight 4” I introduced you with various types of Shapes available in Silverlight 4 and informed you that, I will post an article describing each one of them and here it is.

In this article, I am going to describe you about each shapes and the process to add them in our application (whenever you need). This article is for the Beginners, who don’t know much about the shape controls. If you have any suggestions/concerns please use the feedback section to let me know.

This article is Part 2 of the series Sketchflow from a developer point of view:

1. SketchFlow from a developer point of view - Part I - Basics 
2. SketchFlow from a developer point of view - Part II - Dev Stuff

Introduction

Sketchflow is a great tool for prototyping, that’s great for designers, but… for developers? of course !!!

In this article we are going to step through Sketchflow functionality from the point of view of a developer.

To check how Sketchflow works we will:

• Simulate the startup of simple project: a  local community web site, that will hold news / events / members plus and admin area.
• Insert video snippets in between the article to show how to perform certain operations using Sketchflow.

I’ve gotten the Windows Phone App fever. The past few days I’ve been creating my first Silverlight applications for Windows Phone and I have to say I’m impressed with the development environment and the emulator.  I’ve done a lot a work with Windows CE and Windows Mobile in the past, so I've seen my fair share of device emulators, and the Windows Phone emulator is very nice and easy to use.  

1. Introduction

In this short series of articles I’ll show you how to integrate Telerik OpenAccess ORM in Silverlight applications, how to solve issues when applying this pattern and how to take advantage from this great product. What will be covered?

• WCF RIA Applications with Telerik OpenAccess ORM Part I: The Basics
• WCF RIA Applications with Telerik OpenAccess ORM Part II: Create, Update, Delete and Validation 
• Creating Silverlight Applications with Telerik OpenAccess Data Service Wizard
• WCF Data Services with Telerik OpenAccess ORM
• WCF End Points Services with Telerik OpenAccess ORM
• Silverlight Applications for Windows Azure with Telerik OpenAccess ORM Part I: Connection to SQL Azure
• Silverlight Applications for Windows Azure with Telerik OpenAccess ORM Part II: Developing the Silverlight Client and Deploying the Application

To MEF or not to MEF?

Did you ever wanted to build a modular application? You know when you program against interfaces rather than actual implementation, and the implementation is likely to change anytime? The implementation resides in building blocks and you can just replace these building blocks whenever you want. Or maybe you wanted to build an extensible application that can work nicely with plug-ins. I could go on and on with examples but in general, we can say that we have an application and a couple of modules, extensions, building blocks, whatever, and we just want to ”plug” them into our application, without writing any more plumbing code or applying any modification.