Print

Flipping on LightSwitch



Alexandra Weber Morales
Email
April 23, 2012 —  (Page 1 of 4)
Everyone’s aiming for the “citizen developer,” but lately that elusive customer has led Microsoft on a snipe hunt. With LightSwitch, the company has a rapid application development (RAD) tool, that no one—not even Redmond or its partners—seems to know quite what to do with.

When Microsoft announced the Visual Studio LightSwitch beta in August 2010, the target audience was Access users. The developer community response was predictably negative, envisioning monstrosities similar to what corporate users often created with Microsoft Access, which grew until they “became self-aware and literally devoured the entire office,” blogged Kevin Hoffman, “The .NET Addict,” in July 2010.

“Finally, as this story always ends the same way, someone from IT was tasked with converting this Access DB/Excel sheet/pile of sticky notes into a legitimate, supportable, maintainable application.”

One year later, with the first release of Visual Studio LightSwitch, Microsoft had refined its target: both end-user developers and professional developers. But several Microsoft partners who offer Silverlight controls have only cautiously tinkered with LightSwitch extensions. Developers continue to disdain the IDE despite its proclaimed utility for prototyping and productivity. And fear abounds over Microsoft’s Silverlight strategy as the market shifts away from that cross-platform plug-in toward HTML5 plus JavaScript.

In February, Microsoft announced exciting changes for LightSwitch in the Visual Studio 11 beta, which comes with a Go Live license, meaning projects built with the beta can be deployed to production. With major enhancements such as OData support, the IDE is poised for greatness, according to its small but vocal fan club. Amid all the obfuscation, will LightSwitch finally shine?

Doing the right thing
“There’s a lot of misinformation around LightSwitch,” said Beth Massi, Microsoft’s senior program manager for the Visual Studio community. “This is definitely a developer tool. It is in Visual Studio. We’re targeting an end-user developer. It is RAD, not a code generator. You are describing an app, and it is making technology choices for you under the hood. Basically, the only code you write is the only code you could write, which is the business logic.”

Like dBase, Visual FoxPro and Visual Basic before it, LightSwitch is designed for quickly building data-centric apps. Unlike these earlier dev tools, however, it abstracts today’s .NET stack for three-tier applications with:
• Presentation in Silverlight
• Logic in C# or VB .NET, and data via OData and the Entity Framework, both hosted in ASP.NET
• Data storage in SQL Server Express (included in LightSwitch), SQL Server or, in the cloud, SQL Azure

“It’s designed to launch users down a path of success,” praised Rich Dudley, developer evangelist for ComponentOne, a maker of Windows and .NET controls. “If you start your app in LightSwitch, later you can deploy it to a Web server where the department can consume it, and you can scale and maintain it,” he said.

Unlike Access, he said, “Here’s a tool that will get you 80 to 90% of what you need and lighten the load off your developers. Microsoft always likes to highlight that it’s forcing the Model View ViewModel pattern...plus the Entity Framework, OData services for the communication layer, and Silverlight for the UI.” His colleague, product manager Dan Beall, concurred: “It’s actually forcing you to do something right.”

Productive, portable and scalable
The promise of LightSwitch, then, is for quickly building line-of-business applications that manipulate structured data, such as customers and orders, while being portable and scalable.

From a UI standpoint, LightSwitch screen design is hierarchical and declarative, replacing the typical WYSIWYG form designer with a process whereby the detail in the data model itself allows a UI to be interpreted and generated (not to mention easily re-skinned or updated without altering a line of code).

From a data standpoint, the ADO.NET Entity Framework lets you program against a conceptual application model instead of a specific relational storage schema, which avoids hard-coded dependencies. LightSwitch is designed to sidestep the typical context shifting that slows citizen developers down when they must switch from specifying application behavior to defining regular expressions. Business Types, such as Email or PhoneNumber, come with appropriate input masks and UI behavior.

Authentication, permissions and security are also built into LightSwitch’s underlying technologies, including IIS and ASP.NET, and developers have the opportunity to make important access control decisions at each application layer.

Finally, when it comes to deployment, LightSwitch applications, which are generated in Silverlight, can run on desktops, inside the browser, or in the cloud. A SQL Server Express database is included in LightSwitch. Scalability is built-in, unlike those Access or shared Excel files business users are so fond of. And the MVVM pattern at the heart of the LightSwitch application is contained in an ApplicationDefinition.lsml (XML-compliant LightSwitch Markup Language) file, detaching it somewhat from platform specifics.


Related Search Term(s): LightSwitch, Microsoft, Visual Studio

Pages 1 2 3 4 


Share this link: http://sdt.bz/36550
 


Comments


04/23/2012 08:06:13 PM EST

I appreciate that you took the time to talk with so many people to accurately cover LightSwitch.

United StatesMichael Washington


04/24/2012 02:34:03 PM EST

Great article Alexa, thank you. This is a great objective roll-up of LightSwitch perspectives. I speak to this "Citizen Developer" topic in a few of the articles on my blog @ paulspatterson.com. Do you have any other insight into the adoption rate of LightSwitch? For example, is there any indication from Microsoft suggesting that LightSwitch sales are meeting expectations? Probably too early to tell at this point in time, but would be interesting to know. Cheers, Paul PaulSPatterson.com

CanadaPaul


05/22/2012 08:40:28 AM EST

Lightswitch will not be sold as a separate product but only included in Visual Studio 11. This is not encouraging if the end-user developer is one of the targeted primary users of Lightswitch. The idea of Lightswitch capturing Access developers seems to be waning. Initially, it was rumoured that the Access data file was going to be a data source for Lightswitch. This is no longer appears to be in the works. And now that the product will only be available through Visual Studio seems to further put this product firmly in the full-fledge developers court. Steve

United StatesSteven


close
NEXT ARTICLE
Microsoft releases Visual Studio 2013 Update 1
Targeted update rolls out technology improvements and bug fixes for Visual Studio 2013 Read More...
 
 
 




News on Monday  more>>
Android Developer News  more>>
SharePoint Tech Report  more>>
Big Data TechReport  more>>

   
 
 

 


Download Current Issue
APRIL 2014 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?