Skip to main content

Moving to the cloud - part 4

When e-mail, files and blog are already in the cloud the Cornball is the only application left on my hosting provider. It is now getting really exciting because there is no doubt that the Corball should move to the Microsoft cloud, Windows Azure.

The Cornball is a Silverlight application which communicates through a WCF service with a MySQL database, all on the same hosting provider. This is about to be converted into a Silverlight application which communicates through a WCF service on Windows Azure that in turn communicates with an SQL Azure database.

Microsoft have published a lot of information to get started with Windows Azure, but basically it is quite simple. After downloading the tools and SDK it is just to get on with the development. Through my MSDN subscription I have got some free Azure capacity so just by logging on to the Windows Azure portal I am ready to configure my cloud.


The Windows Azure Management Portal is a Silverlight based user interface which is very easy to use an intuitive. There is a wide variety of settings and possibilities, but the things I needed for my application was to create a Data Store, a database and also a Hosted Service. Once these components were created I could easily set up a connection in Visual Studion which enabled me to Deploy my application directly to the cloud.


SQL Azure has a Silverlight based user interface as well, and it works perfectly for my simple needs. I have only got two tables and a couple of stored procedures. There are some limitations in SQL Azure compared to SQL Server but since I was moving from a MySQL server that was nothing I really thought about.

So, now I have moved e-mail, files, web sites and databases to the cloud and I could not be more happy! Everything has been running as clockwork and I have saved some money each year as well. I have also gained a lot of experience and set myself free from some worries.

Comments

Popular posts from this blog

Programming AD with C#.NET – part 4

Our transition to the  System.DirectoryServices.Protocols  has in the whole gone very smooth, but there have been some issues with one environment that contains subdomains. Most things are working fine, but writing to a subdomain does not work in the same way as it did before. What is generally bad with the  System.DirectoryServices.Protocols is the documentation, which is practically non-existent. But most things can  be figured out anyway since most classes just are wrappers for the wldap32.dll, which in turn is way better documented. I would like to have as little bindings to a specific server as possible but still be able to access the domain. In the  LdapConnection  it is possible to set the identifier to null and use the executing computer as a starting point to find a domain controller. But sometimes I must know that I am using a Global Catalog, and with more and more RODC in the environment I sometimes must know that I am working against a writeable domain controller.

jQuery file upload with Bootstrap progress bar

Performing an asynchronous file upload from the browser is a common problem with almost as many solutions as there are developers. The following solution is the best fit for my needs, and also works well with most popular browsers. Backwards compatibility is not an issue in this case which is great, because I can use the new technologies as they are supposed to be used. Everything is put together in JSFiddle for a working example . I will continue to explain the parts below... First, the input field needs to be styled as a button. The form tag is only present for us to be able to reset the file input field later on. <form>     <span class="fileUpload btn btn-default">         <span class="glyphicon glyphicon-upload"></span> Upload file         <input type="file" id="uploadFile" />     </span> </form> .fileUpload { position: relative; overflow: hidden; } .fileUpload input { position: a

Google+ finally for everyone!

There have been a lot of whining on Google from their Apps-users since the launch of  Google+  for everyone with a regular Google-account. The Apps-users have not been able to use  Google+ , until now! (actually  october 27 ) As usual I am impressed with most of the things Google accomplishes, but now when all of their services have gotten a visual and functional touchup I am getting really impressed. As someone at an early stage pointed out it is really sweet of Google to play naive and let me fill in my profile information when I create my profile (as if Google did not already know), but after a few clicks I am on the go. My albums from Picasa is automatically integrated and even the pictures I have uploaded to this blog is shown in  Google+ . But what happens next? Practically no one of my friends are on  Google+  so what do I use it for? I guess we will see. Hopefully there will be even more integration between the social networks in the future. I am anyhow very satified with