Install Visual Studio 2013 Update 2

Install Visual Studio 2013 Update 2

  • Comments 12

TechEd 2014 is going on this week in Houston, Texas and there have been many exciting announcements from all over Microsoft. You can read about all the exciting developer-focused announcements on Soma’s blog:

Mobile-first, Cloud-first Development – Visual Studio 2013 Update 2 released, Visual Studio Apache Cordova Tooling preview and the future of .NET for Cloud and Server

We, on the LightSwitch team are particularly excited about the release of Visual Studio 2013 Update 2. Update 2 includes bug fixes to the upgrade experience, designer experience, as well as customer reported issues so we encourage you to install the latest update. Visual Studio 2013 Update 2 also includes improvements in bookmarking pages within your LightSwitch applications. Look for a blog post about this in the near future.

Thank you everyone who submitted feedback via the forums, user voice, connect or send-a-smile!

Download Visual Studio 2013 Update 2

Have fun creating those awesome LightSwitch apps!

-Elizabeth Maher, Senior SDET, LightSwitch Team

Leave a Comment
  • Please add 3 and 8 and type the answer here:
  • Post
  • Hi Elizabeth, it would be helpful to know how existing projects should take advantage of the fixed issues as there does not appear to be an upgrade option. The HTML table sorting issue (for example) seems to have been fixed in the new msls-2.5.0.js file, but it was only discovered through experimentation that one needs to copy the new version of that file - which for some reason has the same version as the previous release - over to the existing project.

    What other files should we copy across or is there a better way?

    Many thanks

  • Xander,

    Copying the new version manually is your best bet right now.  The LightSwitch team is aware of this issue and I will add a comment to this post when I have further news.

    The changes made to msls js file were all on the bug fix level.  The HTML sorting issue was fixed, as you mentioned.  

    Best regards,


  • Hello Elizabeth,

    I'm hoping you can answer some Lightswitch questions or point me to a roadmap doc or such that would help shed some light on some questions.  I'm starting to look at investing some time into LightSwitch.  We used to be full blown Xaml, Silverlight & WPF but MS has made it clear in the technology guide Silverlight is going away.  So we've resorted back to WPF.  However, that's temporary until we can figure out exactly where Microsoft is heading and may stick with for more than 5 years.  I've started looking into Lightswitch because of a request to build a sharepoint app for a customer and stumbled on the Cloud Based template.  It's html but when I go into the pure LightSwitch templates it states its for mobile apps, and then there is a Desktop template.  However, to my amazement the desktop template states it utilizes Silverlight.  I like the base screen templates which get created, however, how can I in good conscience sell a client on a LightSwitch application that's built off Silverlight?  Is there some type of migration plan if we start Silverlight based desktop apps today, they are going to migrate to say a Windows Anywhere platform or even WPF down the road.  I don't see how WPF could be an option since your template creates a web app.

    The HTML template for now seems limited and we don't want a SPA interface for rich applications built specifically for desktops.  To recap, the questions are:

    1) If we build mainly desktop applications, from Microsoft perspective what should we be considering if we're trying to use LightSwitch for departmental applications to increase productivity.  If you say the Desktop template, what's the migration path away from Silverlight down the road?

    2) Is the HTML option only designated for the mobile environment and will only have the option of building an SPA app?  The Lightswitch template would seem to imply that, but then again if you look into SharePoint, a Cloud based Business application in fact looks to use LightSwitch and the interface seems to be a SPA, mobile based.

    I like the concepts of Lightswitch but without a Roadmap or very detailed guidance document for building enterprise/departmental apps, we remain hesitant to go too far down any one path and continue to stick with a WPF or Asp.Net option for fear of running our customers down a dead in path or at the very best a path that boxes them in eventually because of limitations requiring us to at some point start their projects over from scratch.


  • Hi Elizabeth,

    I totally concur with Kris. Many shops that I deal with feel burned by Microsoft over Silverlight. LightSwitch is great, and I am a proponent of it, but the lack of a roadmap is troubling, even though this issue is repeatedly raised. Is this supposed to be a secret for some reason? (if so, why?) Or do you simply not know where you are going yet?

    The desktop (Silverlight-based) version is so feature-filled compared to the HTML client, but the HTML client has so many advantages of its own (e.g. touch enabled, no plug-in required).  When I am helping my clients make decisions for a major project, it sets the course for them for (hopefully) a long time. We need a glimpse of what is expected to going to be there at the end of the march, not just what is over the next hill.

    And by the way, are there going to be improvements (or guidance) to performance when developing very large projects (hundreds of tables, for example)?

    Please throw us a bone. We have to plan as well.


  • Hi Elizabeth,

    I totally agree with the two comments above. A roadmap is absolutely necessary to make Lightswitch a bigger success!

  • Having installed Update 2, we're now experiencing the issue covered in the following Microsoft connect submission on multiple machines: -

    Prior to installing Update 2 everything was fine using Update 1 and the Office Tools for VS2013 Update 1.

    Any help would be appreciated as this is proving a pain.

    Kind regards,


  • The real news with this update is that Dynamic Conn Strings are now supported.  Looking forward to a team blog in this...very soon we hope.  Words simply cannot express...Thank you! Thank you! Thank you!  LS Team Rocks!

  • Is there a post defining what is included within this update for Lightswitch?

    Thanks, Steve

  • Steve,

    The difference from Office Developer Tools for Visual Studio 2013 – March 2014 Update to Visual Studio 2013 Update 2 are some bug fixes.  Most notable changes include fixes to the table sorting and the bookmarking feature.  I believe there was also a fix around the search textbox and scrolling.

    Hope that helps,


  • For those asking for a roadmap, the LightSwitch town hall hosted by Joe Binder is a good place to start.   It is available at Joe also responded on a forum thread with a written road map.  That thread is available at

    A few important points from both these communications are:

    -The Silverlight client for LightSwitch will continue to be supported per the Silverlight support policy.  

    -We will continue to improve the HTML Client, focusing on mobile devices.

    -Office 365 is our sweet spot.  You can see that with the Cloud Business App.

    Hope that helps,


  • Change log please - I am in the middle of an LS HTML project and need to know which bugs the upgrade fixes to decide whether to risk the upgrade now.  

  • Not the right one. Does not redirect to any update 2 for VS2013. Wrong link.

Page 1 of 1 (12 items)