With the upcoming of the new Virtual Machines service on Microsoft Windows Azure, many server applications are going under testing and porting to cloud located machines. Today i tried to install a VisualSVN Server on Windows Server machines (both 2008 R2 and 2012) located in Windows Azure. The porting is quite simple and smooth and can be completed in less than half an hour. Since Azure VMs are persistent, all the installation and configuration can be performed directly on the remote machine simply using Remote Desktop Connection, without the need for any additional virtualization software. The only point that requires some attention is the correct setting of the Server URL inside VisualSVN Server, otherwise your SVN client will come to an abrupt halt immediately after setting up the connection due to a response containing misleading server information. The VisualSVN Server in fact sets by default its Server Name in the form https://[yourAzureVMName]:8443/svn/, missing part of the complete DNS name of the Azure VM. The correct URL that needs to be set is https://[yourAzureVMName].cloudapp.net:8443/svn/.
All the details can be found in this short QuickStartGuide. Hope it helps!
YETI snow solution, the entertainment and tracking system designed and prototyped by Michał Wojtysiak and Maciej Piotrowski with the support of MIC Torino, has been proclamed the winner of the Bavaria Region Price on 19 October at the European Satellite Navigation Competition in the Allerheiligen Hofkirche of the Munich Residenz.
The European Satellite Navigation Competition (ESNC) values especially innovative ideas involving satellite navigation. It gives the opportunity to present and promote innovative ideas, and eventually, to put them into practice. The ESNC is a challenge for companies, scientists and students. Apart from the overall prize, the competition awards several Regional Special Prizes financed by local sponsors, in order to help the winners to begin exploit their ideas. The Bavaria Region Prize, a prize incubation package (valued at EUR 35,000) at the Anwendungszentrum GmbH Oberpfaffenhofen (AZO), is sponsored by the Bavarian Ministry of Economic Affairs.
Imagine you go skiing in the mountains. Suddenly, you feel queasy or pass out and get injured. You need help, but help is not at hand … What if your smartphone could call for help – all by itself?
YETI snow solution is a system which can alert rescue teams or other skiers in multiple ways. Thanks to widespread access to GNSS services and many communication channels, there will be someone to provide instant assistance for you. Even if you are out of GSM range!
Furthermore, to enhance YETI snow attractiveness (especially for younger generation), it offers variety of entertainment services, such as workout tracking, single and multiplayer gaming. High interaction levels between users strengthen the sense of community. In a unique way, YETI combines virtual gaming and search&rescue services. All the user needs, is a smartphone with the YETI application installed.
YETI snow solution is the idea of two polish students, Michał Wojtysiak and Maciej Piotrowski, who spent an Erasmus period at Politecnico di Torino. During their internship here at Microsoft Innovation Center Torino they developed the first YETI prototype.
The system is composed of a Windows Phone 7 application, the core of the project, and a Windows Azure backend, which provides storage capabilities and additional in-browser functionalities. This project is one of the examples of convergences between embedded/phone system and the cloud platform proposed here at MIC Torino.
YETI has been submitted to the European Satellite Navigation Competition and is currently under evaluation.
When developing a business application for Windows Azure, almost surely you end up creating custom build configurations to manage multiple deployment settings for the different stages of the development process. To do this VS2010 and Windows Azure SDK (from 1.4) offer some straightforward interfaces for the configurations management with an automatic update of the project files.
Unfortunately, in Windows Azure projects with web roles this process can cause some packaging and publishing problems on x86 machines. In fact after the set up of a new custom configuration, you may receive this build warning when creating the Azure deploy package:
“warning WAT160: The project ‘YourProject’ contains the following assembly: C:\Windows\assembly\GAC_32\msshrtmi\188.8.131.52__31bf3856ad364e35\msshrtmi.dll. This assembly is not compatible with the 64-bit processor architecture used by IIS on Windows Azure. To make sure that the role starts, you must replace this assembly with one that is compatible with this architecture.”
The reason for this warning is that the automatic project files updater creates the new configuration property group in the web project file (.csproj) from a template which includes a PlatformTarget element. The presence of this element forces the inclusion of the msshrtmi.dll, that on x86 machines is only 32-bit processors compatible.
Example configuration tag:
<PropertyGroup Condition=”‘$(Configuration)|$(Platform)’ == ‘Production|AnyCPU'”>
When deploying the packaged solution to Windows Azure the Web Roles containing the msshrtmi.dll library will not start properly.
Fortunately, the solution is quite simple: you should manually remove the PlatformTarget element from all the custom configurations properties in the web project file.
To solve this problem you have to:
- In Solution Explorer, right-click on your web project and select Unload Project
- Right click again and select Edit
- Delete all PlatformTarget elements
- Close the file and Reload Project by right clicking on the web project