Tag Archives: HTMLClient

LightSwitch – Common Core Teacher Evaluations

lsWires-1.0.6-Tiles

Here we’ll show you, via video, an application we’ve written to support the Common Core Standards for Education.  Its an evaluation system that in its current form is about teachers.  But we’ve made it so that with just a bit of terminology change, it can morph into an evaluation system for most anything.  Living or not!

  • Based on TNTP.org simplified rubric
  • Multi-tenant
  • Drag and Drop sorting
  • Tile based menus
  • Role based
  • Analytics with pretty graphs
  • Supports desktops down to smart phones!

Check it out on our tutorial site… TES

You can also see the video and more up on our YouTube Channel.

Tagged , ,

lsWireCore Project Updated v1.0.6

lsWireCore

Updated to lsWires.js v1.0.6

Added Database Project to pre-seed the tiles
Just need to edit the tiles in the browser to add the icons

Added lsWiresExtras folder with the security tile icons
Highly recommend Syncfusions Metro Studio for additional icons.

Updated the CopySolution.ps1 script

Fixed Visual Studio from changing IIS ports on rebuilds

This should be the project that you use our CopySolution on

We’ve moved the repo to https://bitbucket.org/interbay/lsWireCore

Don’t hesitate to holler if something breaks!

Well it broke… Arrrgggg!!  Hopefully easy work around… just do a full rebuild after you download. 
(thanks Michael Washington)

Dale

Tagged , , ,

lsWires.js Updated – 1.0.6

Good day folks,

lsWires.js has been updated, 1.0.6
lsWires.js now embeds its dependencies
lsWires.js repository has moved:  http://bitbucket.org/interbay/lswires
lsWires.js 1.0.6 will most likely break things
lsWires.js documentation will be updated shortly
lsWires.js samples will be converted and moved over to Bitbucket

We’ve also added a new database project that will pre-seed the tiles for managing security.
Have added a folder lsWiresExtras that includes a few icons for the tiles
Updated the CopySolution script, but the better solution to copy is the lsWireCore project due to a naming issue.

We’ve done some pretty significant changes under the covers and we appreciate the patience.  One of the big ones is incorporating “signals” for hooking into the jQuery Mobile Page events.  We’re also providing a much simpler, yet more powerful, tile based menu system.  I think you’ll appreciate its simplicity.  For example:

lsWires-1.0.6-Tiles

We’ll also be posting a new “real application” video that will showcase what you can do with the new 1.0.6.  Which is what the image above is from.  I think you’ll be pleased with what you see and how you can bring excitement to your LOB apps!

Stay tuned!

Tagged , , ,

LightSwitch Tutorial – Create a Multi-Select Pick List

We’ll show you how you can easily create a pick list that allows selecting multiple items, work those items, show what’s selected when you go back into the pick list.  It’ll quickly become part of all your projects!

In this tutorial we show how to take our core project, and change the pick list for adding/removing permissions from Security Roles.  Allowing the Admin to remove/add permissions in one swoop vs. having to keep popping up a pick list for each.

So check it out at our tutorial site:  LightSwitch.CodeWriting.Tips

Here are the screen shots of what you’ll get, open the picker.

RunningPicker1

Select some items, click the save button.

RunningPicker2

Now open the picker back up, notice it preselects.  Go ahead and remove a couple and add others.

RunningPicker3

 

Tagged , ,

LightSwitch – Single Production Database, Multiple Applications?

Yes you can!

We’ll show you how you can actually use the same production database for multiple LightSwitch applications.  We’ll also show you how you can share common tables. And we’re not talking by OData endpoints here.

Great for situations where you are limited to the number of databases, not to mention simplifying maintenance.

Check it out on our tutorial site… lightswitch.codewriting.tips  – with videos!

Tagged , ,

LightSwitch HTML Client – The lsWire Core Project

Our new lsWire Core project will be the basis for all of our tutorials going forward.

Its based on the lsWires framework and is our first tutorial being hosted on our new site, http://lightswitch.codewriting.tips

This is also our first tutorial that we’re providing a “Starter Kit” so that you can not only quickly get going, but that you can create as many new solutions from this core project as needed.

This little item alone will, hopefully, dramatically change the landscape of the LightSwitch ecosystem. By allowing developers to provide their own starter kits from their own amazing solutions.  Especially since Visual Studio has not provided a means for creating templates from LightSwitch Applications.

Click here for a direct link to the tutorial.

Tagged , ,

How To Create An Expanded LightSwitch 2013 Project!

This process requires the March 2014 Update

I’m happy to report that the March 2014 Update brought back SCAFFOLDING!! Yay!

How to add Web API and MVC to a LightSwitch 2013 project

Visual Studio LightSwitch is a great product. But it’s not the end all and most professional development projects require a mix of technologies to be considered successful. By following these steps, you’ll end up with a LightSwitch project that has the HTML Client, Silverlight Client, MVC, Web API and Web Forms with the naming conventions of your choosing. Giving you a solution without restrictions!

First time thru the tutorial it may still take you 15 minutes. So give it a try and see what you think… Oh… btw you can clone/download the updated sample project from github… you’ll need this, but really only for the WebApiConfig.cs.

  1. Start Visual Studio 2013
  2. Create a new project: File, New Project…
  3. Select LightSwitch HTML Application
  4. Name the project: myTest
  5. Name the solution: myTest
  6. Create new table
  7. Name it TestItem, 1 property, Name
  8. Add your browse/add/edit screens for the TestItems table
  9. Double click on the properties file for the myTest project
  10. Enable forms authentication, and allow Security Admin for debug
  11. Save the solution, do a full build, run the app
  12. Add some test data into the table
  13. Back into Visual Studio
  14. Right click on your server project
  15. From the Add Scaffold window, click on MVC 5 Dependencies
  16. Press the Add button
  17. On the Add MVC Dependencies popup
  18. Select the Full Dependencies option, press the Add button
  19. Close the web.config that gets automatically loaded
  20. In the App_Start folder, open RouteConfig.cs
  21. Add the following line under the other IgnoreRoutes
    routes.IgnoreRoute("{*allsvc}", new { allsvc = @".*\.svc(/.*)?" });
    
  22. Right click on the App_Start folder, add a new Class file
  23. Name it WebApiConfig.cs
  24. Replace the contents with the contents from the WebApiConfig.cs file from our zip file
  25. Add two folders under the Controllers folder
    1. api
    2. mvc
  26. Right click on the api folder, select add, select New Scaffold Item
  27. Select Web Api 2 Controller with Read/Write actions
  28. Name it TestController
  29. Follow the instructions of the readme.txt file that automatically opens in the editor
  30. Make sure the GlobalConfiguration.Configure gets added to the beginning of Application_Start
  31. In the Controllers folder again, right click on the mvc folder, select add, select New Scaffold Item
  32. Select MVC 5 Controller with read/write actions
  33. Name it HomeController
  34. In the HomeController.cs file that gets automatically loaded
  35. Right click on the ActionResult Index()
  36. Select add view
  37. In the Add View dialog, leave all defaults, just click on add
  38. Go edit your default.aspx page in the root of the solution
  39. Comment out the first line… add some test text to the body
  40. Do a full save, then rebuild, run your app

Your LightSwitch html app will run first with your custom URL path
http://localhost:{port}/App

Moving on, let’s test access to the ApplicationData.svc file
http://localhost:{port}/ApplicationData.svc

So far so good eh? How about our MVC?
http://localhost:{port}/Home

Yay! Looking good… now our default.aspx file in the root…
http://localhost:{port}/default.aspx

Yep that works too… final test… the Web.Api side…
http://localhost:{port}/api/Test

You can now go in and clean up the project, delete the test screen, test table, etc.
Save the solution again.

This would be the point when you would add your project into source control.

One of the great features out of this is we can use Visual Studio LightSwitch to do all of our data management without having to go down into the Entity Framework.

Happy coding!

Tagged , , ,

Rename LightSwitch 2013 HTMLClient

When creating a new Visual Studio LightSwitch HTML Client, the “powers” have hard coded the naming of what the project names shall be.  For the publicly visible HTML Client project the name will be {mySolution}.HTMLClient and your deployed URL will also have the name of {url}/HTMLClient.  Obviously not the best scenario for most applications.

If you follow these steps you’ll be successful at not only changing the name of your project in Visual Studio, but also changing the public URL.  Replace {mySolution} with the name of your own solution name.

Obligatory Disclaimer… please backup your project/solution before attempting this procedure!

  1. Open your solution in Visual Studio 2013
  2. Rename {mySolution}.HTMLClient to your new name {mySolution}.App
  3. Close the solution
  4. Important… Close Visual Studio
  5. Open a Windows Explorer, navigate to your solution folder
  6. In your favorite text editor, open the {mySolution}.sln file
  7. Replace all instances of the name HTMLClient with your new name, App
  8. Save
  9. Next level down, open the {mySolution}.lsxproj file
  10. Replace all instances of the name HTMLClient with your new name, App
  11. Save
  12. Rename the HTMLClient folder to your new name, App
  13. Save
  14. Next level down, in your App folder (old HTMLClient folder)
  15. Open the App.jsproj file, this should already reflect the new name
  16. Replace all instances of the name HTMLClient with your new name, App
  17. Save
  18. Open the ModelManifest.xml file
  19. Replace all \{mySolution}.HTMLClient\ with your new name, App
  20. Save
  21. Start Visual Studio 2013 again, open your solution
  22. Once fully loaded, select Build, Clean Solution
  23. Then select Build, Build Solution
  24. Double click on a screen to validate the editor is still working
  25. Double click on a table also to validate the editor is still working
  26. Run your app (F5)

Your solution and browser should now be using the new name.  Yay!!

Does this now open up the possibility of more than 1 HTMLClient?  Absolutely!!  Especially if you already had the original HTMLClient in source control.  Perhaps for another post 🙂

Tagged , ,