Saturday, November 30, 2013
Wednesday, October 16, 2013
Presentation: Take the advantage of Windows Azure to market your application in SaaS, with real-life testimonials and feedback
With a testimonial based on real case application that is used to predict sales' stocks deployed as a SaaS application into Windows Azure.
Quality enforced though FxCop / StyleCop / Resharper and NDepend v5 !
(An English version is planned to be written...).
Saturday, July 27, 2013
I am a real fan of StyleCop and FxCop for the last 4 years or so (see how many rules FxCop+StyleCop).
Up until now, I have been only build up my knowledge from my own experience and reading blogs.
The small size of this book allows a broader vision rapidly, and covers things that I never had the time to implement on real projects (such as VS Templates, or files headers).
I also finally understood why my Resharper did not work with my StyleCop, which was an easy thing to fix.
It is worth reading !
Friday, July 26, 2013
And the most warriors of us stayed up until 1 in the morning where we were talking about TDD!
Free drinks and special hotdogs to accompany our discussions.
Wednesday, July 3, 2013
Finally, after years of struggling with AssemblyInfo.cs files to be updated to track assembly versioning, here IS an EASY WAY to do this thing, which should have been made easy in the first place in TFS. In the past, I used a more sophisticated way of doing it.
The credit to this method goes to Steve Fenton, who explained his method called "Automatically Updating Your AssemblyInfo The Wrong Way".
To me it is less elegent than doing a full workflow foundation solution, but it solves my problem quick ! So that a good solution. Secondly, maintenability is also great, as it is based on a plain text Batch file. No need to recompile deploy, …
The secret lies the following steps :
- the only mini-change that one could barely notice the link icon on the AssemblyInfo.cs file. Here is a representation in both Visual Studio 2013 Ultimate preview and Visual Studio 2012 Ultimate
ZOOM ! on AssemblyInfo.cs
The result is instantaneous … on every single step of my software factory, it is highly traceable with the unique ID of the TFS Team Build of 370, as illustrated below.
(1) Displays on an “About Page” the exact version of the application, based on the assembly version of the AssemblyInfo.cs,
(2) This version number is dynamically generated by TFS Team Build during the Continuous Deployment process (called _CD).
This guaranties the uniqueness of this number. In this example, it is Build# 370, which gives a version 188.8.131.520.
As a result, we could go up to 1.0.0. 65534,
where 65534 = UInt16.MaxValue – 1= 65535-1
Then you can open the TFS Drop Folder to verify that ALL your assemblies have the correct assembly version.
(3) From TFS Cloud, you’ll get a Zip file that has got the unique suffix “CD_370”, and in the App.publish, you could unzip the Windows Azure package *.cspkg
(4) Once unzipped into the folder “???CD_370”, you’ll see the DLLs
(5) Check the first DLL; we could see the magic happened: The assembly is tagged as 184.108.40.2060
(6) Check another Assembly: still 220.127.116.110 !!
DONE ! and Enjoy !!
And the most time consuming part to was to find the proper solution, since many great alternatives are present in CodePlex. I’m sharing that with you hoping it’ll save you plenty of time… and another hope is that this simple feature will appear one day in TFS at last after years of wait !!
Sunday, June 30, 2013
|Since my previous post, after a fast reformat and the installation of Windows 8.1, the installation of Visual Studio 2013 Preview (with ALL options), was smooth and relatively fast. |
To avoid this pain, you could also mount a Windows Azure VM that is ready for you to try: http://visualstudio2013galleryimage.azurewebsites.net/
Because VS2013 supports the development of Windows Phone 8.0, the installation has activated and configured Hyper-V (image 1).
|A fast reboot allows us to start rapidly with VS2013 (Image 2). |
We can see how the new version handles an optional sign in into VS2013 (image 3).
Then, another Windows Account is needed to log into you Team Foundation Service in the Cloud Azure.
Once VS2013 is started I ran into TFS to open my Windows Azure project… and a now common error is this one:
|The Azure SDK currently available is not compatible with VS2013. Although, I tried to cheat and used a “Microsoft Web Platform Installer 4.5”. |
This is confirmed by this MS documentation: https://www.windowsazure.com/en-us/develop/visual-studio-2013/#not-supported :
“Features that are not yet supported in Visual Studio 2013
The Windows Azure SDK for .NET is not compatible with the Visual Studio 2013 Ultimate Preview. This means that Visual Studio 2013 can not yet be used to author, debug, or publish cloud service projects. In addition, no Server Explorer support is available for features other than Mobile Services, and streaming logging is not available for web sites. An SDK release that is compatible with Visual Studio 2013 will be available later in the summer.”
And this one: http://msdn.microsoft.com/en-us/vstudio/dn250998.aspx
It doesn’t fully matter, because even without a Windows Azure Project, I could use the old fashion “Web Publish” to deploy into Azure on my existing Could Service.
The first thing I wanted to try was the handy “Peek Definition” which is a variant of “Go To Definition”, except that you stay on the same page, and the definition is displayed inline.
For the other new features available in VS2013, it is quite pleasing to see that it is getting better and better. However, the drawback of that is that one have to always keep up to date on what’s available to produce be best possible application !