Notable changes from Beta 2 to RTM

    General discussion

  • The following is a list of notable changes that we made for RTM after Beta 2. If you were an early adopter and built applications on Beta 2 you may be impacted by these changes. This is in no way an exhaustive list. If you reported a bug through Connect and it’s not listed here, check to see the status of the bug by going to http://connect.microsoft.com/VisualStudio and either click on “My Dashboard” at the top to see your submitted bugs or perform a search on “LightSwitch” to see all of them.

    If you built applications with the Beta 2 release of Visual Studio LightSwitch your projects will open and build fine in the final RTM release. Beta 1 projects are not supported. 
    This following list represents the more notable behavior changes we made for RTM.

    Changes to the Collection Refresh
    In Beta2, the built-in Refresh command on Lists and Grids and the corresponding API would only refresh the screen by adding new data from the server. Existing data shown on the screen would not be refreshed. This also applied to any queries executed within the data workspace. If entities had been previously retrieved, they were not updated when re-queried. This behavior has now been changed so that any refresh or re-query of entities on the client cause new data to be added and existing unchanged entities to be updated with new values from the server. Any modified entities remain unaffected. The behavior when issuing queries on the server remains the same as Beta2. This new refresh behavior will allow users to view the latest updates from the server without having to lose any of the unsaved changes they might have made on the screen. If you are using the collection refresh button or API or have code that issues queries from the client then this updated behavior will be enabled once your application is published with the final release of LightSwitch. If you have designed your application screens and workflow for the Beta2 behavior you may need to account for the new behavior in your design.

    Additional settings persisted
    The window size for out of browser applications is persisted across application launches. If an end user resizes the application window to a specific size then that size will be remembered the next time the application launches. Similarly the minimized or maximized state of the Navigation Menu and Ribbon will be persisted. If the navigation menu or ribbon were minimized when the application is closed then they will remain minimized the next time the application is launched. This functionality will be automatically available to applications that are published with the final release of LightSwitch.

    Multi-column sorts
    Sorting on multiple columns has changed. Previously if your query was designed to sort on multiple columns the actual data being displayed on the screen would only be sorted by the first column specified. This has changed so when you publish your applications with the final release the screens will automatically begin sorting based on the multiple column sort orders as specified in the query.

    Various Changes to Screens & Controls
    We have made various changes to the screen and control layouts including better defaults and fixed behaviors on various properties. You will benefit from the new default properties when creating new items and any new behaviors will be automatically available when you publish your application with the final release.
    Some examples include -
    • Default layouts for screens created from parameterized queries – When creating new screens for parameterized queries the collection controls like grid and list will take up the entire screen width instead of being indented under the parameters control. Only new screens created with the final release will default to this behavior, you will have to modify existing screens manually if you want the new layout.
    • Labels can autosize height to fit text – In Beta2 setting the labels Height property to Auto would not increase the labels height to fit the contents; instead the content would be clipped. With the final release a label with Height set to auto will resize its height to fit its content.
    • Resize row and column layouts – New properties were added which when enabled will allow end users to resize the rows and columns for those screen layouts.
    • You will be able to specify a screen data item be of type GUID. You will be able to choose GUID as a type in the “Add Data Item” dialog.
    • In Beta2, there is a hard-coded minimum height in the tab control. We have fixed this issue, it now respects the layout settings in the properties.
    • In Beta2, the data grid does not respect the regional settings for decimals in display mode. We have fixed this issue.
    • When trying to use FindControl.ControlAvailable the ControlAvailable event was never raised in Beta 2 for a modal window. We have fixed this issue, this event is now raised whenever the modal window is opened.

    Senior Program Manager, Visual Studio Community http://msdn.com/lightswitch http://msdn.com/vbasic http://msdn.com/vsto http://www.bethmassi.com
    Tuesday, July 26, 2011 7:52 PM