This article will provide several tips to adopt LightSwitch programming model using Application Lifecycle Management (ALM) approach.
This article will combine the ALM with Rapid development model using data driven development in LightSwitch. In general, ALM approach has three major steps which are Define, Develop, and Operate. We will discuss each step and relate it with the LightSwitch Development.
Step 1 - Define The Data
LightSwitch using data driven model so the first step is to define the data. LightSwitch using Data Driven model so what we need is to design several data structure which are
- Designing and Creating Table. This action is the most vital in this step. The selection of datatype, naming convention, and the data length is three main aspects that need to be handled in this step. Table normalization will help cut development time.
- Creating the computed property for each table. Computed property variables will be valuable for any computing purposes.
- Creating the screen. Screen is composed logically in LightSwitch. Defining the screen discuss how the data will be shown. Be sure to format the data using forrmatting properties, change the display name properties, and hide the unused data.
Fig 1. Defining data is not only about selecting a data type but also displaying the correct data to the user
Step 2 - Develop The Application
Creating a screen from a Wizard on Visual Studio is not a silver bullet. In many real application, sometime we need to build the screen from the beginning. However, the development consists four main activities which are:
- Composing and editing the screen to suit your application need. We should learn a lot about layouting. For example, column layout can be combined with row layout to provide list (master) and detail records. Tab layout will be great to be used when we want to show the relation or dependency between table, Each layout has a purpose, so be sure to learn each layout for better user experience.
- Developing the codes. In LightSwitch, we can do a code in Computed Property or write a code in screen. Computed property can reach our data entity while write code will help us to access the screen data. Combining both codes will help to access anything in the application.
- Runtime query. In LightSwitch we can edit directly the entity query by using edit mode. In this case, we can access and edit the query on the fly without go back to add query on the table. I suggest to use runtime query when you need a direct interaction with the screen data such as filtering using a control, or creating custom search through parameter.
- Building RIA Services. Lightswitch is a combination between Silverlight and RIA Services. Therefore, you can customize LightSwitch further using RIA services. The good news you can host the RIA services within your LightSwitch application. RIA Services can be used for advanced application scenario such as create a custom report, consuming third party services, or even building powerfull business logic.
Fig 2. LightSwitch is a combination between Silverlight and RIA Services
Fortunately, LightSwitch provide you a bulletproof when you do code changes, table changes, and others. You have to worry when you changes a table will break the data binding. The screen still work as usual and adopt the changes that you made. You can learn more the development techniques in LightSwitch Blog.
Step 3 - Operate the Application
When building a LightSwitch, you can integrate the versioning system and engineering process with the ALM package in TFS and Visual Studio Ultimate. If you already done with it, your agenda is delivering the application to the customer. Several consideration when you distribute your application are:
- Visiting your client and see how you will deploy your LightSwitch application. You can develop your Lightswitch in 2 tier deployment, three tier, and Microsoft Azure deployment. Two-tire is a good choice if you want your customer feel a LightSwitch app just like desktop application so that it can interact directly with Microsoft Office Application and others local resources. Three tier is great way to deploy your application in self hosted Web application. Azure choice is great when we need high performance and elastic LightSwitch application.
- reparing the dependency. Your Lightswitch need at least a SQL Server 2008 R2 and Silverlight 5 (for Lightswitch 2012). Be sure to bring that to your client so that they can get better installation experience. Publishing option provide you once click installation, but please be aware that the dependency component should be downloaded and sometimes is not good to see your 20 MB LightSwitch application has 600 MB dependency. Therefore, this article encourage you to have master installation for SQL Server 2008/2012 and Silverlight 5.
- Database deployment choice. When you publish your Lightswitch application you have two choices in database deployment which are using SQL script or direct to the database. If you already know or believe that your user doesn't have a SQL Server, the backup-restore can work great. Just choose direct to the database and backup the deployment database and restore in your client database.
Fig 3. Publishing Option in LightSwitch
Community Solutions Content DisclaimerMICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.
Id. de artículo: 2770725 - Última revisión: 20 jun. 2014 - Revisión: 1