You are here:   Blog
Register   |  Login

Latest Microsoft LightSwitch Blogs

Note: This article applies to LightSwitch in Visual Studio 11 (LightSwitch V2) It’s common for developers to add static images and text to their screens to help guide their users through the application.  Although you can easily add images that come a database to your screens, up
Read more...

Matt Sampson has posted part 3 of a multi-part blog post this week that completes the walkthrough of creating an application around the popular public transit CommuterApi OData Service. This post focuses on creating a RIA Data Service
Read more...

Eric Erhardt has posted part 2 in his series on using stored procedures in LightSwitch. In the second part, he describes how you can use Visual Studio LightSwitch to update database records using stored procedures.  A lot of database administrators only allow modifications to data through
Read more...

The first release of Visual Studio LightSwitch (LightSwitch V1) allows users to define relationships between tables within the intrinsic/built-in data source (ApplicationData).  When attaching to existing data sources, LightSwitch will import the relationships defined within the data
Read more...

Eric Erhardt has posted part 1 of a series on using stored procedures in LightSwitch.  In the first part, he describes how you can execute a stored procedure when a user clicks a button on your LightSwitch screen. The blog post is here – Read more...

Oct 16

Written by: kchristo
Sunday, October 16, 2011  RssIcon

I had initially discarded LightSwitch from my deck of choices. At first glance (early Beta 1) I had misjudged it as poor relative of application builders that I hate altogether.   

It was after watching Beth Massi’ s presentation in Tech-Ed USA 2011 regarding extensibility that made me take a second good look at it. And then…then it was love at second sight.    

Although extensibility was what made me love LS, it took me quite some time to decide to write my own extension. I had custom controls I was using (the Color business type and editors is an example) and referenced libraries for a long time as I was really intimidated by the idea of creating an extension of my own. And it was only after the official release of Visual Studio LightSwitch that I even thought of doing it, as the Cookbook  and blank template approach was, to say the least, discouraging, at least for me. I knew I wasn’t the intended audience.    

When I started the development of the first application, I knew I had to write the extensions. Using the custom controls required so much duplication of logic –mostly- and code, and was so restricting (as to how to name the members of the screens etc.) that made it unattainable to use them.    

Just reading the How to articles on extensibility it was obvious the path to follow was there but many things were to be discovered and solve down that path, the hard way. I mean, it’s not the most complete and well structured documentation, but a wealth of information is provided.    

“Be a man” I said to myself and created my first extensibility project. Took me a lot of effort to even have this, preliminary in terms of quality and completeness, version released. But, as I said in the previous post, as soon as I replaced the first custom control with the respective extension control I knew it was all worth it…
In upcoming posts I will share implementation details that i believe are worth sharing.

Tags:
Categories:

1 comment(s) so far...


Gravatar

Re: CLASS Extensions. Making of (the origins)

I am looking forward to the series :)

By Michael Washington on   Monday, October 17, 2011

Your name:
Gravatar Preview
Your email:
(Optional) Email used only to show Gravatar.
Your website:
Title:
Comment:
Security Code
CAPTCHA image
Enter the code shown above in the box below
Add Comment   Cancel 

Microsoft Visual Studio is a registered trademark of Microsoft Corporation / LightSwitch is a registered trademark of Microsoft Corporation