Version to 1.8.2.

Author: realvizu

CHANGELOG.md

@@ -1,5 +1,10 @@
 # NsDepCop Change Log
 
+## v1.8.2
+(01/2019)
+
+- [x] Fix: #43 (for real this time) - RemotingException when path contains space.
+
 ## v1.8.1
 (12/2018)
 

README.md

@@ -35,7 +35,7 @@ See the [**Help**](doc/Help.md) for details.
 
 ## Feedback
 * Please use the [**Issue Tracker**](https://github.com/realvizu/NsDepCop/issues) to record bugs and feature requests.
-* Or tweet me [![Follow on Titter](https://img.shields.io/twitter/url/http/realvizu.svg?style=social&label=@realvizu)](https://twitter.com/realvizu)
+* Or find me on twitter [![Follow on Titter](https://img.shields.io/twitter/url/http/realvizu.svg?style=social&label=@realvizu)](https://twitter.com/realvizu)
 
 ## More Info
 * [Diagnostics Reference](doc/Diagnostics.md)

appveyor.yml

@@ -2,7 +2,7 @@ image: Visual Studio 2017
 
 environment:
   shortversion: '1.8.2'
-  informationalversion: '1.8.2-beta1'
+  informationalversion: '1.8.2'
 
 version: '$(shortversion).{build}'
 

doc/Troubleshooting.md

@@ -10,9 +10,9 @@
 ## Exception: Unable to communicate with NsDepCop service
 > Applies to version v1.7.1 or later.
 
-This problem is either caused by a bug that was fixed in v1.8.1 or by the analyzer client not waiting enough time for the analyzer server started in a separate process to spin up.
+This problem is either caused by a bug that was fixed in v1.8.2 or by the analyzer client not waiting enough time for the analyzer server started in a separate process to spin up.
 To fix it:
-* Update to v1.8.1 or later. 
+* Update to v1.8.2 or later. 
 * Try to set longer and/or more wait intervals in your config.nsdepcop file(s) by adding the AnalyzerServiceCallRetryTimeSpans attribute to the root element and fiddling with its value. The value should be a comma separated list of wait times between retries (in milliseconds).
   * E.g. this config waits 100ms, then 1sec, then 10sec: