- Markdown: added an options page with properties to:
  - Hide/show the preview window.
  - Enable save to disk.
  - Specify a custom save location.
  - Added some default values for the settings dialog (MarkdownOptions), but they seem to be ignored.
  - Exposed MarkdownSharp options in the settings dialog:
    - AutoHyperlink
    - LinkEmails
    - AutoNewLines
    - EmptyElementSuffix
    - EncodeProblemUrlCharacters
    - StrictBoldItalic
- CoffeeScript
  - Added property to enable/disable the compiler.
  - Added property for custom save location.
- LESS
  - Added property to enable/disable the compiler.
  - Updated property for custom save location (hopefully won't conflict with existing settings now).
  - Added missing LessSourceMaps property to ProjectSettingsStore; I'm assuming it should be there with the others.
- Greatly cleaned up the MarginBase.GetCompiledFileName() code by using the ProjectHelpers.GetRootFolder() method. Thanks to @SLaks.
- Got the compilers (LESS, CoffeeScript, and Markdown) working when there isn't a project loaded and you're just editing one of the files.
- Upped the version to 1.3.13; I don't know if you want that incremented or not. (Sure makes it easier than un-installing everytime.)
- TODO Need to figure out how to set defaults, because right now the LESS and CoffeeScript compilers are defaulting to disabled..
Better capturing of region name in JavaScript regions

This is a fix to a small issue where the region name wouldn't be picked up when the region starts with // #region Name

When there is a space between // and #region, the region collapses (since startHide = "// #region"), however the regex that extracts the name does not allow the space, so when collapsed the region would show "#region" instead of the name. This new regex works with both //#region and // #region.
Setting to skip relative paths fix on css minify

Sharepoint has virtual "/Layout" folder, so it makes sense to keep there
resources, which are directly "deployed" to the server.
Outside this folder can be development going on, e.g. css-files, which
eventually need to be compiled, minified and so on.
Having enabled css relative paths overwriting on minifying by default
without a setting to turn it off interfere with this folder structure.

Say we have
/Layout/Project1/Styles/fonts/font-awesome.woff
/Layout/Project1/Styles/css/plugins.css.bundle

now, bundle, references file:
/Styles/css/font-awesome.css

now replacing the "../font.woff" to "../../../../font.woff".

The commit is rather simple and merely adds a Misc option to css  bundle
compile check inside
WriteBundleFile,
controlling thus
CssUrlNormalizer.NormalizeUrls

Feel free to commit, or point out why that's unwise, how could we make
this better.
Merge pull request #239 from kodybrown/master

More updates.. Yeah, maybe went a little crazy with this one.. What do you think about setting the defaults? Where would you like those set?
Merge pull request #241 from am11/master

Fixed #240
Merge pull request #243 from xps/patch-1

Better capturing of region name in JavaScript regions
Merge pull request #245 from gr9zev/master

Setting to skip relative paths fix on css minify
Fixed null reference exception
Truncate SourceMapURL from result
Log result when exception is thrown