2012 | Thomas' Work Space

How to work around broken links and visible “Machine generated alternative text”issues with images from MS-OneNote in Windows Live Writer

2014/07/08 plagwitz Leave a comment

Problem: Sometimes when you use Windows Live Writer (2012) to post images copied from MS-OneNote (2010, 2013), the result (on WordPress) can get messed up, like so (post has since been fixed as described below):
1. The image is missing (“src=” link broken).
2. The “alt=” text is visible instead (and you did not want to post this “alt=”text anyway. (MS-OneNote OCRs images to make the text therein searchable; this text is put into the “alt”when pasting from MS-OneNote).
Root cause:
1. Windows Live Writer converts the pasted content by
  1. removing the “alt=”Machine generated alternative text: [deleted for brevity]”
  2. creating from the pasted content thumbnail images
  3. which it links in the “src=” tag, and links the thumbnail image to the full-size original image.
2. If something – unclear what – prevents this conversion, Unfortunately, this is not obvious from the “edit” tab view or elsewhere within Windows Live Writer. But when posted, will result in “Machine generated alternative text” from MS-OneNote in place, but even break the image src link: .
3. What exactly triggers (and would allow you to force) a successful conversion within Windows Live Writer I do not know. However, there is a simple:
Workaround:

After pasting your images, be patient : The trick seems to be to give Windows Live Writer enough time (more apparently if you have pasted multiple images) to finish
Things you can look for in Windows Live Writer to make sure the conversion is finished:

2012/11/17 plagwitz 3 comments

When right-clicking on my App.config to access the Enterprise Library configuration tool, I kept getting this error:
after installing
1. VS.net 2012;
2. Enterprise library 5.0.414 through nuget (why does nuget install only this older version?);
3. the unofficial Enterprise Library Extension vsix updated for VS.net 2012 published by the Enterprise Library team here.
What fixed this error for me was (YMMV, November 2012):

installing Enterprise Library 5.0 optional update 1 (=5.0.515) using this approach:

– Adding to the vs.net 2012 SLN file, at the end of "Global" (immediately before "EndGlobal")

GlobalSection(ExtensibilityGlobals) = postSolution
EnterpriseLibraryConfigurationToolBinariesPath = C:\Program Files (x86)\Microsoft Enterprise Library 5.0\Bin
EndGlobalSection