A few days ago I posted about my first useful Azure application, which is hosted on here http://storageexplorer.cloudapp.net http://azurestorage.azurewebsites.net. Today I just wanted to announce I just uploaded the code to a Google Code project called windowsazurewebstorageexplorer :)
It is a good (I think is good) example of both programming for the Windows Azure platform and programming against the Windows Azure Storage client API.
So feel free to download it and let me know what you think. (Make sure you download the Windows Azure tools for Visual Studio 2008 first)
As usual, this code is certified to apply every “works on my machine” standard :)
Note: Too bad the December 2009 Windows Azure-Related Developer Challenges are for US only :(
Read Full Post
Summary only...
I recently read on stackoverflow a ton of great programmers quotes I thought it’d be good to share.
Here are some of my favorites.
“Walking on water and developing software from a specification are easy if both are frozen.”
“Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.”
“Linux is only free if your time has no value”
“Debuggers don't remove bugs. They only show them in slow motion.”
Read the full list here.
Read Full Post
Summary only...
Why would you want to do that in the first place? Let’s say you have a complex (long) test you want to run in your application, so you decided to start it before going home so it’ll be ready tomorrow morning with the results. What would happen if when get to you computer the next morning you find an assert dialog waiting for you to “Abort”, “Retry” or “Ignore”? Believe me, it is frustrating and irritable!
I had a few “alternative ways” to ignore those asserts (http://twitpic.com/qvecx) but Willy told me the correct way to do it.
All you have to do is adding the following to your .exe.config file:
<system.diagnostics>
<assert assertuienabled="false"/>
</system.diagnostics>
That code tells the framework that you don’t want to show a message box when a “
Debug.Assert” is called, which is exactly what I wanted.
So, since my test is a msbuild script all I had to do is adding the above “code” in the msbuild.exe.config and now my tests runs smooth and the results are ready, waiting for me :)
More info on the assert tag
here.
Read Full Post
Summary only...
Posts
