ClearWriter version 3 in the Windows Store

Version 3 of my Windows 8 app ClearWriter is up in the Store now!

It’s a minor update with some bug fixes, but most importantly you can now print from the app.

I expected printing to be something pretty simple to code. Boy was I wrong ūüôā
The existing SDK sample isn’t that clear and a bit too complicated.
I tried to strip it and keep it as simple as possible, but there’s still a lot more work to do to get it as clean as I want.

If I find the time, I’ll write a blog post about the implementation!


MakePri errors in Windows 8 project

While working on my Windows 8 app project called ClearWriter I got the following error:

“MakePri.exe” exited with code -1073740940.

I was working with the resw files, localizing my app, so I expected MakePri to be involved with the resource creation.

After excluding my resw files and including them one by one, I found the incorrect resw file. Apparently I had a Resource name that ended with a dot. Removing this solved the error.

I tried to reproduce the error for this blog post, but now I got the following error when I inserted the dot:

Error 1 Processing Resources with error: The parameter is incorrect. MakePri
Error 2 Unspecified error occurred. MakePRI

My first Windows 8 App: ClearWriter

I am experimenting with the development of Windows 8 Apps. So far it has been an interesting journey and the result is a (for now) very simple app called ClearWriter.

Clearwriter logo

I wanted to create something that doesn’t need a lot of business logic, but allows me to experiment with the different contracts and the global design of a Windows 8 app.

That’s why I created a full screen writing app.

The “content over chrome” logic behind the Windows 8 Apps fits perfectly for ClearWriter. You just focus on your writing, nothing else.

Clearwriter Screenshot

I wanted to push the app to the store as quickly as possible, to get feedback from users, so for now functionalities are limited, but I’m working on that.

Here is a list of the current functionalities:

  • Distraction free writing
  • White or black color scheme
  • Associates with .txt files
  • Sharing from the app

Some functionalities that are on the backlog:

  • Printing
  • Searching
  • Word count
  • Support for Markdown
  • Focus on the current sentence

ClearWriter is translated in English, Dutch, French and German and is free to try for 7 days. It can be downloaded from the store. If you like the app, and want to support its further development, you can buy it for only ‚ā¨ 1,19.

If you have any questions concerning the app (feature requests, improvements, bugs, questions about the development) feel free to ask them here, or mail them to

In future posts i’ll document some interesting parts of the development process of ClearWriter.

ReSharper: my favorite 5 shortcuts

I admit it, I love ReSharper

Honestly, I’m not affiliated with JetBrains in any way, but I think they’ve got a fantastic tool, which makes a developers life a whole lot easier. If you are a C# developer, you should check it out.

I’m still discovering new functionality, even after using it for a few years. In this post I wanted to share my favorite shortcuts. They’ve saved me countless hours, so hopefully you’ll find some new ones, and save yourself some time too!

A remarks before we begin: these are the default ReSharper mappings, but it’s possible that you’ve made some changes to these mappings. If they don’t work, head over to your Visual Studio settings and check your keyboard mappings

Here they are (in no particular order)

  • Alt-PageUp/Alt-PageDown and Alt-Enter¬†–¬†Next/Previous highlight and Quickfix
    It gives you a great feeling of power and control, just cruising over all the warnings in a file with Alt-PageUp/PageDown and fixing them with Alt-Enter. Clean code in no time.
  • Shift-Alt-L¬†– Locate in Solution Explorer
    When you need to quickly locate the file you have open in the Solution Explorer, this handy shortcut does the trick. You’ll be amazed at how many times you can use this!
  • Ctrl-F12¬†– Go to Implementation
    Navigating around my code with F12 (Go to Definition) was common practice, but on ¬†an interface most of the time I wanted to go to its implementation. You can imagine my joy when I discovered this shortcut ūüôā
  • Ctrl-Shift-R – Refactor this
    The mother of all refactoring shortcuts. This gives you a context menu with the possible refactorings in the current context.
  • Alt-Ins – Generate Code
    Quickly add code like constructors, properties or equality members (super handy on structs).

If you need a quick overview of the keymappings, you can download a PDF for your version from the JetBrains website. Or you can try the keymaps for ReSharper Visual Studio plugin.

Have you got any other favorite shortcuts? A favorite feature in Reshaper? Just love the tool and want to spread the love? Leave a comment!

Refactoring keeps it tidy

This is a translation of the dutch post I did for my company’s blog.

Refactoring coverRecently a friend of mine handed me a copy of Martin Fowlers¬†Refactoring: Improving the Design of Existing Code¬†(that’s what friends are for). The book is considered a standard on refactoring en can still be seen as a must-read for every programmer, although it published in 1999.

Refactoring means to rewrite code, in small, safe (backed by unittests) steps. Doing this cautiously ensures that there is no loss of functionality and results in a decrease of error-proneness of the code and an increase in readability and maintainability. As Folwer mentions: the compiler reads your code once, while your and your colleagues will be gazing over it and changing it a lot times during coding. Making sure your code is readable (really readable, like a book) will save you and your coworkers a lot of time!

Fowlers book also helps you maintain the DRY (Don’t Repeat Yourself) principle. If you have to duplicate a piece of business logic in your code, it WILL cause you trouble. When the logic has to be altered, you can be sure that one of these places will be forgotten.

Before Fowler starts working on a piece of code, to fix a bug or add new functionality, he’ll often start with a refactoring to better understand the code. This may sound strange, but it is almost impossible to write perfect code from the start. I don’t mean working code, but code that is open enough to support all the possible questions, extensions or other changes and still is small enough to only do what it needs to do. If you accept the fact that you are going to have to refactor, and that it’s not a failure for you as a programmer, you can write better, cleaner code.

My favorite tool to do this (in .Net) is the fantastic ReSharper. A lot of the refactorings in the book can be done automatically and safely with this tool. It has an¬†enormous list of functionalities, and I’m¬†still discovering new uses every day.

An important note on refactoring is knowing when to stop. Knowing when to start is one thing, but at least as importing is knowing when you’ve refactored enough, or when a refactoring isn’t going as planned and the best thing to do is undo your changes. Huge reworks are done one refactoring at a time. You can always come back¬†tomorrow¬†to do the rest of them. As long as you leave the code in a better state than it was before, your good!

Refactoring fits perfectly in the iterative Agile process and is a corner-stone of¬†Extreme Programming¬†(XP). It’s no coincidence that¬†Martin Fowlers¬†can be found underneath the¬†Agile Manifesto. Clean code will also provide value for the customer.¬†Although¬†it sounds¬†counter intuitive, investing time in refactoring saves time writing code. A win-win!

If you haven’t, read the book and start refactoring.

You’ll love it, it’s a way of life.

All unittests with code coverage failing on branch

Because I practice Test Driven Development, I write alot of unittests. When code gets branched, most of the times these unittests all fail (an yes, they all ran green on the main branch).¬†Most of the tests failed with the exception “Could not load file or assembly”.

Time to do some investigating, my dear Watson.

Nothing could be wrong with the tests themselve, because I was sure they worked and since they all failed, it was a global problem. I checked out the test settings we use (x.testsettings, should be next to your sln file) and went through all the tabs.

On the Data and Diagnostics tab I found we only had Code Coverage enabled, so I took a closer look at that by selecting the line and clicking configure at the top of the grid.

Aha, seems like all of these paths are still pointing to my main branch! I have no idea why these paths are not relative, but after selecting the correct assemblies (the ones from my branch) and deselecting the ones from the main brach, all was well and I could return to my unittesting bliss.

Now this is still a bit of a bummer if I have to do this for every branch I make. I should probably try to change these paths to relative ones, but I have not done that yet.

Has anybody else encountered the same problem? How did you solve it?

3 blogs…

In our line of work it can be vital to keep up with the latest technology. Blog are ideal to keep up with recent news.

My favorite programming related blog is definitely that of Scott Hanselman. The humor he brings to these technical subjects is always entertaining. Also, he is one of my favorite speakers!

Another great blog to keep up with .Net related news is that of Scott Guthrie. Great in depth technical information.

Finally the ideal blog for programmers who don’t have enough time to keep up with all the blogs out there: The morning brew. Having someone wrap up all the interesting other blog posts daily means I don’t have to and can just read this one post!

Good stuff out there!