none
LightSwitch in Visual Studio 2013 Preview and RC and LightSwitch in Visual Studio 2012 Update 3 Release Notes

    General discussion

  • LightSwitch in Visual Studio 2013 RC - Known Issues

    Upgrading Existing Lightswitch Projects to Visual Studio 2013 RC
    If you have upgraded your project that contains a HTML client to Visual Studio 2013 RC, there’s a manual change needed to the .JSPROJ file in your solution.  Here are the steps to follow:
    1)      Locate the .JSPROJ file in your solution and open it in notepad (or your text editor of choice).  It is typically located in the solution directory under “<solution folder>\<application name>\<application name>.HTMLClient\<application name>.HTMLClient.JSPROJ
    2)      Find and replace all instances of “$(LightSwitchVersion)” with “v4.0” throughout this file and save it

    3)      Close and reopen the solution in Visual Studio

    LightSwitch in Visual Studio 2012 Update 3

    Update 3 for Visual Studio 2012 is now available for download here: Visual Studio 2012 Update 3

    Important: After installing Visual Studio Update 3, any new or upgraded LightSwitch project will no longer be able to display any built-in localized strings. If you have or need to create localized applications, the Release Candidate for Visual Studio Update 4 fixes the localization issue. You can download Update 4 RC here: VS 2012 Update 4 RC 1
    Download Center

    The update doesn’t include any new LightSwitch features, but it does incorporate several bug fixes, most notably the JavaScript Intellisense issues.

     LightSwitch in Visual Studio 2013 Preview - Known Issues

     Upgrade

    Visual Studio 2013 supports upgrading projects created with Visual Studio 2012 (including Update 1 and Update 2). If you have a project created with LightSwitch HTML Client Preview 2, you must first upgrade it to Visual Studio 2012 Update 2 and follow the manual steps in the Migration Report at the end of the upgrade. Upgrading directly from Visual Studio LightSwitch 2011 isn’t supported. You must first upgrade the project to Visual Studio 2012.

     Known Issues

      •          In some cases, the StartUp project in the solution is not set correctly after upgrade. You need to ensure LightSwitch root project is the StartUp project. Right click on the root project and select “Set as StartUp Project”.

      Publishing

      Known Issues

      •          In some cases, the Publish wizard freezes the IDE the second time it is opened.

      General Development

      Known Issues

      •   You can't rename an HTML screen once the underlying screen code file is generated (for example, by writing screen code).
      •   Copying and pasting or dragging and dropping HTML client files in Solution Explorer and the Code Editor is not supported. Solution Explorer currently does not prevent such operations, however doing so will cause your project to become unstable and possibly unusable. 
      • If you update an external data source, Silverlight screens that contain data from related tables will lose all controls that are bound to the related tables. There is no workaround other than to recreate the screens each time you update the external data source.

      Team Development

      Known Issues

      • Get Changes from Server with Designers Open:

      Doing a Get operation (latest or specific change set) when the project is open in Solution Explorer and when designers for entities or screens are also open may cause Visual Studio to crash. To avoid this, close all the windows for designers and also the Start page before doing a Get operation. Alternatively, you can close and then reopen the solution before doing the Get operation.

      • Reload the Project After Getting Changes:

      When model changes are obtained from server using a Get operation, the model is in a pending reload state. At this time, debugging or building will fail.

      Before doing any subsequent operations on the model (Eg Build, F5 or adding/deleting/editing entity, screen etc.), it is advised to reload the project manually.

      This reload can be done by double-clicking the Properties node of root project. This prompts for reload. Select yes for the model to be reloaded. Again, make sure that all designers are closed at this time. Alternatively, the solution can be closed and reopened.

      Note: For changes that involve resolving manual merge conflicts, always close the solution before resolving the conflicts and then reopen the solution.

      • HTML client-specific files aren’t tracked for pending changes initially

      In a couple of instances, we have observed that HTML Client files are not included under pending changes (untracked in Git terminology). So before checking in the project under Source Code control for the very first time, verify that all the files are included.

      In the event that they aren’t included, manually include them by right-clicking Excluded files (Untracked) and select the appropriate files. This should be a one-time operation.

      • Build failure with TFS Online

      First time builds of projects that use the intrinsic database may report a build failure. In most cases executing the Retry Build command (on the context menu) should result in a successful build.


    Steve Hoag Microsoft aka the Lights Witch (IEnumerable of Newt)










    Thursday, June 27, 2013 6:10 PM
    Owner