Monthly Archives: December 2015

Using cloud storage for Open Live Writer draft posts

Blog, Open Live Writer, Technical stuff
No Comments

You might not have heard one of the best news ever for bloggers: Windows Live Writer was open sourced, thanks to the relentless effort of a few ‘Softies. It is awesome news because Windows Live Writer is awesome but needs some love, and Microsoft hadn’t really touched it in years (literally, the last version available was released in 2012).

More information about Open Live Writer is available on Scott’s blog and http://openlivewriter.org. Open Live Writer is a part of the .NET Foundation (like MVVM Light too ;) and is giving us bloggers a lot of hope and happiness for awesome development! I am of course using it right now to write this post, and already noticed a couople of improvements. You can fork the code here and submit pull requests, however

One thing that is super important to me is saving my draft posts on OneDrive so that they are backed up safely (sometimes I just start a new post to draft some ideas and don’t finish writing the article immediately) and also for synchronization amongst devices. In WLW I was following Scott’s advice and editing the Registry to set the “PostsDirectory” key to save into my OneDrive.

Of course with the new applications comes a new Registry location and you can find it at HKEY_CURRENT_USER\SOFTWARE\OpenLiveWriter. Once there, create a new String value and set the folder path where OLW should save and find the Drafts. For me I created a folder within my OneDrive, but of course it also works with Dropbox etc.

2015-12-14_10-36-49
(Click for larger image)

Hopefully this will help with the adoption of the new Open Live Writer and it will quickly become the standard in blogging editor!

Happy blogging ;)
Laurent

GalaSoft Laurent Bugnion
Laurent Bugnion (GalaSoft)
Share on Facebook
 

Solving the issue where unexpected languages appear when you submit to the Windows 10 Store (#mvvmlight)

MVVM, Technical stuff, Universal Windows Platform UWP, Windows 10, Work
No Comments

Ah the joy of developing for new platforms :)

Over the past few weeks, I received a few bug reports where an application that was supporting only one, non en-US language was receiving some errors when being submitted to the store. In short, the store thought that the application was bi-lingual (original language + en-US) and asked for all the assets (description etc) in en-US as well. Needless to say it is no fun for the developer who has to prepare all the assets in en-US at the last minute.

This issue was described here in the CommonServiceLocator library. And unfortunately, because MVVM Light has a dependency on this library, it can also occur in MVVM Light applications too.

It’s a bug!

After reporting the issue to Microsoft, and having one member of the team spend some time on it (thanks!), it so happens that it is due to a bug in Visual Studio 2015. This is a regression in the handling of portable class libraries. And what’s great is that (while waiting for the bug to be fixed), there is a workaround:

  • Open your application’s CSPROJ file in a text editor.
  • In the first PropertyGroup of the project, add the following line:
<SkipIntermediatePriGenerationForResourceFiles>false</SkipIntermediatePriGenerationForResourceFiles>

This line will prevent the bug from happening, and you should be able to submit your app to the store as usual.

Happy coding!
Laurent

GalaSoft Laurent Bugnion
Laurent Bugnion (GalaSoft)

Share on Facebook