I listen to a few podcasts. Mainly technical ones. I recently got a hint from Mike Minutillo about a podcast called “Stuff I learned yesterday”. I was blown away when I started listening to this podcast. It makes you think more about stuff that you learned. Furthermore, this podcast is full of stories from the podcasters themselves but also from the community. You’ll find the podcast here
One of the recent inspiring and very emotional episodes are
If you have lost someone in your life like I did, you know why I like this one.
Are they even listening?
If you are a parent, like I am, you know why I like this one.
Subscribe! It is emotional, inspiring, makes you laugh, cry, think…
Post picture by http://www.gotcredit.com/
I recently announced Machine.Specifications.Resharper 1.1.0 release. This is the last release I did for Machine.Specifications. I’m taking a step back from the project. Let me give you a bit of background how I ended up maintaining Machine.Specifications and why it’s time to move on. Continue reading
I’m hereby announcening the Machine.Specifications.Runner.Resharper 1.1. It provides support for Resharper 9.1. Install it over the gallery. You should also be notified about the new version being available.
For a little more than seven years bbv Software Services AG has been my first employer after my studies at the University of Applied Sciences in Horw, Lucerne. Today it’s time to say goodbye. But before I talk about my new future allow me to take a step back and reflect on my bbv Software Services experience. Continue reading
Thanks to Matt Ellis and some bug hunting of me I can proudly say that we have released Resharper 9 integration for Machine.Specifications. You can now install the plugin by using the provided extension manager in Resharper 9.
For those who are using Resharper versions older than 9 I pushed an update for the plugin for Resharper 8.2. It resolves an issues when you switch from Debug to Release mode or vice versa while having a unit test session open. If you did, you actually had to restart Visual Studio so that the Resharper plugin picked up the correct output path location of the specs assembly. Older Resharper versions are no longer supported as well as the installation via batch files. If you find anyting feel free to open issues on the github repository.
I’ll be speaking about Agile Architecture – is it possible? at the BASTA! in Darmstadt next February (The presentation will be in German).
Link to conference.
Link to my session.
This is a really quick announcement. I recently released Machine.Specifications 0.9.0. With that release I introduced a breaking change: I disabled the console output capturing by accident. If you are using console outputs in your specs and need to see them then I strongly advise you to upgrade to Machine.Specifications 0.9.1. You only need to upgrade the Machine.Specifications nuget package in your solution. None of the other components are affected. This is the beauty of the new architecture 😉
Have fun and sorry for the inconvenience!
Today we released the next version of Machine.Specifications. This release implements an important feature to move on in the future. We implemented a complete runner dependency abstraction. What does that mean? Let me take a step back.
The picture above shows the state of Machine.Specifications previous to V0.9.0. The console runner, the resharper runner, the TDnet runner and more were directly dependent upon the same Machine.Specifications version. This means when we release a new version of MSpec you actually had to use also the new version of the ReSharper, Console runner and more. This was not only for you as a user cumbersome it was also for us as the maintainers of the library. We had a massive repository with everything in it and released all as a “big chunk”. That made working, forking and all other git operations heavyweight because the repository was quite large. Continue reading
I attended TechEd Barcelona with a coworker. The venue was just amazing. TechEd was hosted in the Fira Barcelona. The floor space in the fira is 400000 m2. You really have to walk from session to session. But I think that has very positive influence on the conference experience. Because usually when you are always at the same location you are getting more and more tired (mentally) after each session. With the “long” distance walks between the sessions you grab a coffee or tea on the way and head to the next hall (up to 10 minutes depending on your walking speed). This gives you time to think about what you’ve heard in the sessions and also time to “exercise” your body. Good contrast to the sitting only experience of the sessions.
This is an overview of the sessions I visited:
- Day 1
- The Keynote (Link)
- Optimizing Your Datacenter with Windows Server, System Center, and Microsoft Azure (Link)
- Microsoft IoT Platform: Architecture Overview (Link)
- Introducing Microsoft Azure Machine Learning (Link)
- Architecting Predictive Algorithms for Machine Learning (Link)
- Day 2
- The Next Generation of Microsoft .NET (Link)
- TWC | A Game of Clouds: Black Belt Security for the Microsoft Cloud (Link)
- Entity Framework Now and Later (Link)
- Windows PowerShell Unplugged with Jeffrey Snover (Link)
- Introduction to NoSQL in Azure (Link)
- Architecting Secure Microsoft .NET Applications (Link)
- Country Drinks Party 😉
- Day 3
- The Future of Microsoft .NET on the Server (Link)
- Debugging Tips and Tricks in Visual Studio 2013 (Link)
- Automating Microsoft Azure with the Management Libraries (Link)
- Lessons from Scale with Mark Russinovich (Link)
- Day 4
- Building Real-Time Applications with ASP.NET SignalR (Link)
- Entity Framework Model Partitioning in Domain-Driven Design Bounded Contexts (Link)
- Telemetry and Data Flow at Hyper-Scale: Azure Event Hub (Link)
This might seem like a minor release but I personally think is a very good and worthwhile update! The first cool thing in this release is that we have now full AppVeyor support in the console runner. By default the console runner uses auto detection to determine whether it is running under AppVeyor and automatically prints out the necessary outputs for AppVeyor to report the progress, the passed and failed specs and more on the user interface. The auto detection feature uses the APPVEYOR_API_URL environment variable. The auto detection can be disabled by providing the –no-appveyor-autodetect flag to the console runner. This behavior is congruent to the TeamCity integration.
The next very cool and anticipated feature is the resharper gallery integration for the plugin. The Machine.Specification plugin can now be installed by using the Resharper Extension Manager for Resharper 8.0/8.1/8.2 and dotCover 2.6/2.7. The old installation way with batch files is still supported. But I strongly recommend to use the Extension Gallery! You’ll see why at the end of this post.
Before you install the plugin you need to make sure all previously installed MSpec plugins are removed.
By default the batch files installed the plugin files into %APPDATA%\JetBrains\ReSharper\v8.2\Plugins\mspec.
- Make sure you close all instances of VisualStudio and delete the mspec plugin folder.
- After that restart VisualStudio, goto the Resharper > ExtensionManager menu and search for Machine.Specifications.Runner.Resharper.
- Install the latest stable version and you are ready to go!
In the future all plugin updates will be delivered automatically via the Extension Gallery and the old installation procedure with batch files will be deprecated. The final picture says more than thousand words 😉
Last but not least I want to give a shout out to the following contributors who provided the AppVeyor support:
Happy mspecing 😉