Abstract: Changes in display area automatically lead to changes in the format used to display graphical content of a list of items such as thumbnails or application icons, for example. A list display controller transitions between scrollable format and fixed format, and transitions between fixed formats with different numbers of display slots. Transitions may be triggered by window resizing, by moving a graphical user interface from one device to another while the application runs, or by switching between landscape and portrait mode, for example. Even when the format is not changed in response to a display area change, graphical content is automatically resized to match changes in the size of the display area containing the graphical content. Format transitions and content resizing help provide a pleasant user experience by maintaining content density with expected usage patterns for a given device, and reduce proliferation of code versions.

Abstract: Changes in display area automatically lead to changes in the format used to display graphical content of a list of items such as thumbnails or application icons, for example. A list display controller transitions between scrollable format and fixed format, and transitions between fixed formats with different numbers of display slots. Transitions may be triggered by window resizing, by moving a graphical user interface from one device to another while the application runs, or by switching between landscape and portrait mode, for example. Even when the format is not changed in response to a display area change, graphical content is automatically resized to match changes in the size of the display area containing the graphical content. Format transitions and content resizing help provide a pleasant user experience by maintaining content density with expected usage patterns for a given device, and reduce proliferation of code versions.

Abstract: Concepts and technologies are described herein for using virtual machines to manage software builds. A deployment controller manages deployment of a new software build. The deployment controller installs the new software build on test device and tests the new software build. If the new software build functions without errors, the new software build is deployed to hosts of a data center and monitored for errors. If errors are detected, the errors are reported to a developer associated with the new software build. In some embodiments, the deployment controller creates a differencing disk storing differences between the updated software build and an existing software build and uses the differencing disk for installing the new software build for testing and/or for deploying the new software build.

Abstract: Concepts and technologies are described herein for continuously deploying applications. In accordance with the concepts and technologies disclosed herein, a first host environment executes an application. An upgrade for the application is released by creating a backup of the application and content used by the application and restoring the backup at a second host environment. The application hosted by the second host environment is upgraded, traffic is routed to the second host environment, and performance of the upgraded application is monitored. If errors are detected in the upgraded application, the upgrade can be rolled back, and traffic can be rerouted back to the first host environment. If the errors are not detected, traffic can be increasingly routed to the second host environment and the first host environment can be deactivated.

Abstract: Concepts and technologies are described herein for managing continuous software deployment. A deployment controller can manage deployment of code to a data center. The deployment controller can execute workflows for checking in, verifying, deploying the code, or other processes. The code can be deployed using a differencing disk that includes data indicating changes between software hosted by the data center and a version of software resulting from deployment of the code. The differencing disk can be linked to the disk or virtual resource hosting the software and executed collectively to provide an updated version of the software. Traffic to one or more virtual machines of the data center can be controlled by the deployment controller. If errors are detecting during deployment or after updating, the update can be rolled back.

Abstract: Concepts and technologies are described herein for managing continuous software deployment. A deployment controller can manage deployment of code to a data center. The deployment controller can execute workflows for checking in, verifying, deploying the code, or other processes. The code can be deployed using a differencing disk that includes data indicating changes between software hosted by the data center and a version of software resulting from deployment of the code. The differencing disk can be linked to the disk or virtual resource hosting the software and executed collectively to provide an updated version of the software. Traffic to one or more virtual machines of the data center can be controlled by the deployment controller. If errors are detecting during deployment or after updating, the update can be rolled back.

Abstract: Concepts and technologies are described herein for using virtual machines to manage software builds. A deployment controller manages deployment of a new software build. The deployment controller installs the new software build on test device and tests the new software build. If the new software build functions without errors, the new software build is deployed to hosts of a data center and monitored for errors. If errors are detected, the errors are reported to a developer associated with the new software build. In some embodiments, the deployment controller creates a differencing disk storing differences between the updated software build and an existing software build and uses the differencing disk for installing the new software build for testing and/or for deploying the new software build.

Abstract: Concepts and technologies are described herein for continuously deploying applications. In accordance with the concepts and technologies disclosed herein, a first host environment executes an application. An upgrade for the application is released by creating a backup of the application and content used by the application and restoring the backup at a second host environment. The application hosted by the second host environment is upgraded, traffic is routed to the second host environment, and performance of the upgraded application is monitored. If errors are detected in the upgraded application, the upgrade can be rolled back, and traffic can be rerouted back to the first host environment. If the errors are not detected, traffic can be increasingly routed to the second host environment and the first host environment can be deactivated.