Issue #41 - Bring method of determining IE version up to date

src/engine/Main.cpp

 #include <AdblockPlus.h>
 #include <functional>
 #include <vector>
 #include <thread>
 #include <Windows.h>
 
 #include "../shared/AutoHandle.h"
 #include "../shared/Communication.h"
 #include "../shared/Dictionary.h"
 #include "../shared/Utils.h"
 #include "../shared/Version.h"
 #include "../shared/CriticalSection.h"
+#include "../shared/IE_version.h"
 #include "AdblockPlus.h"
 #include "Debug.h"
 #include "Updater.h"
 
 namespace
 {
   std::auto_ptr<AdblockPlus::FilterEngine> filterEngine;
   std::auto_ptr<Updater> updater;
   int activeConnections = 0;
   CriticalSection activeConnectionsLock;
@@ skipping 376 matching lines @@
 std::auto_ptr<AdblockPlus::FilterEngine> CreateFilterEngine(const std::wstring& locale)
 {
   AdblockPlus::AppInfo appInfo;
   appInfo.version = ToUtf8String(IEPLUGIN_VERSION);
   appInfo.name = "adblockplusie";
 #ifdef _WIN64
   appInfo.application = "msie64";
 #else
   appInfo.application = "msie32";
 #endif
-  // TODO: Set applicationVersion parameter
+  appInfo.applicationVersion = ToUtf8String(AdblockPlus::IE::installed_version_string());

[sergei, 2014/07/28 11:46:27]

Why do we need it here? The engine should not know about IE anything. If it's
useful for the log, then pass User-Agent in the first message (pipe) while
establishing the connection with the engine.
Even without digging deeper I'm pretty sure `appInfo.applicationVersion` denotes
the version of the current application, thus engine.

[sergei, 2014/07/29 14:45:56]

Still disagree here.
Why do we need the current solution, if it's not good and not what we really
need? It will raise again, let's do it correctly at the first round.
Let's move the discussion to issues.adblockplus.org, I've updated the ticket.

[Eric, 2014/07/29 15:17:22]

OK, but this is a code review, not an architecture review.

As I see it, Wladimir opened ticket #41, and it's to support the JS code in
libadblockplus, so it's beyond my scope to worry about the details of why he
wants it. Personally, even if it's only for error logging it's a good enough
reason for me.

Populating a single string member clearly does not introduce a new defect. The
bulk of the code here is also required for #404, so knocking of an
otherwise-harmless change at the same time is just not a problem.

[sergei, 2014/07/30 13:49:21]

I'm moving the discussion to intraforum.
https://intraforum.adblockplus.org/t/what-is-the-relation-between-code-review...
want to persist in thinking that this is the right place to talk about this
architectural decision, you are welcome to.
Until that ticket changes, I'll consider it valid.

See my comment above, "Let's move the discussion to issues.adblockplus.org, I've
updated the ticket."

   appInfo.locale = ToUtf8String(locale);
 #ifdef ADBLOCK_PLUS_TEST_MODE
   appInfo.developmentBuild = true;
 #else
   appInfo.developmentBuild = false;
 #endif
 
   AdblockPlus::JsEnginePtr jsEngine = AdblockPlus::JsEngine::New(appInfo);
   jsEngine->SetEventCallback("updateAvailable", &OnUpdateAvailable);
 
@@ skipping 48 matching lines @@
     }
     catch (const std::runtime_error& e)
     {
       DebugException(e);
       return 1;
     }
   }
 
   return 0;
 }