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:
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.
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:
After some short nights we finally managed to stabilize the resharper plugin for Machine.Specifications. The latest stable release is 0.8.2. What has changed?
Thanks for the patience! Happy coding
You have already heard me talking or at least read a blog post about NServiceBus from me The next big release from particular software is just around the corner! This time it is not just another version of NServiceBus. No, it is a whole platform or toolset you can use to build up complex distributed systems based on NServiceBus. I give you a brief overview over the platform and then dive into ServiceMatrix. Let’s get started! Continue reading
My article about Onion Architecture has just been released in the Method and Tools Magazine. The article contains even more insights into the Onion Architecture and how it compares to traditional Layered Architecture by analyzing code samples with Structure Studio. I highly recommend you read it.
Methods & Tools is a free software development magazine on Project Management, Software Testing, Agile, Scrum, Lean, Kanban
Open Source Tools, Software Process Improvement (CMMI, SPICE), Software Architecture, Software Development Jobs
Subscribe to Methods & Tools if you are not afraid to read more than one page to get smarter!
The newest spring edition contains the following interesting articles (including mine):
Download the article directly and for free on their website! I suggest you also click the subscribe button to get notified when the next magazine is published. I would like to thank Franco Martinig for giving me the possibility to publish my article in his magazine!
Remember: Chop onions instead of layers and turn your tears of sorrow into tears of delight.
I just released the newest stable release of Machine.Specifications. The newest stable release contains the version number 0.7.0. What has changed in this release? There is one big change and in fact this is the only relevant change for the users of the library:
Machine.Specifications used to ship directly with its own ShouldExtensions. This was a bit of a pain for people using other assertion libraries like FluentAssertions. I personally prefer also FluentAssertions over other assertion libraries and even over the Machine.Specifications ShouldExtensions. In the past the internally shipped ShouldExtensions would “pollute” IntelliSense for example if you use FluentAssertions. This is now resolved!
The following nuget packages are now available:
Read the following instruction carefully!
If you are a user of the Machine.Specifications ShouldExtensions then upgrade by installing the Machine.Specifications.Should or -Signed package. This has a dependency to Machine.Specifications. I’ve seen issues with nuget that installs a pretty old version especially with the signed package. This seems to be a nuget bug. If this happens just upgrade the Machine.Specifications package in Visual Studio manually afterwards.
If you are a user of for example FluentAssertions then just upgrade the Machine.Specifications or -Signed package and you’ll never see the extension in IntelliSense again (unless you install the package ).
If you have any issues please use the official github issue tracker.
While we are constantly pushing forward the development of Machine.Specifications it can happen that regression occurs especially in the area of the resharper provider and runner. Unfortunately we don’t have integration tests in that area. Apart from the 0.6.0 build we broke the capability of having internal specs or private nested specs. This issue is now addressed and a new release under 0.6.2 is available on nuget. Check it out and provide feedback. So the this release contains the two changes
I’m planning advance more and more to version 1.0.0. Along the way I will be dropping support for old legacy stuff (old versions of dotCover, Resharper…) in order to clean the internals up. Feedback and comments are welcome here. Download the latest release with nuget here.