home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Plugins
Popular Plugins
Fanart Handler
Latest Media Handler v2.4.X.000
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="styrsven" data-source="post: 1182440" data-attributes="member: 135607"><p>After some struggling with this issue, making my hair (what remains of it) even more grey than before, these are my findings:</p><p></p><ul> <li data-xf-list-type="ul">Whatever I do in the code, the log problem is still there if I don't use argus.</li> <li data-xf-list-type="ul">There is a build script that merges the dll with a specific version of NLog.</li> <li data-xf-list-type="ul">If i use the version of the dll that is not merged to NLog, the logs work in all cases.</li> <li data-xf-list-type="ul">I don't know the history, so I dont know the reason why LMH must bring its own private NLog.dll.</li> <li data-xf-list-type="ul">I don't think that NLog is causing this, I think it is ilmerge that finds something in argus that it links to and this makes the logs only work when the argus dlls are found.</li> <li data-xf-list-type="ul">The only way that I could see (at least according to the documentation) for ilmerge to ignore resolving the argus references was to use the /internalize switch with an exclusion list that names all dlls except the NLog.dll. I don't think that is a good solution.</li> </ul></blockquote><p></p>
[QUOTE="styrsven, post: 1182440, member: 135607"] After some struggling with this issue, making my hair (what remains of it) even more grey than before, these are my findings: [LIST] [*]Whatever I do in the code, the log problem is still there if I don't use argus. [*]There is a build script that merges the dll with a specific version of NLog. [*]If i use the version of the dll that is not merged to NLog, the logs work in all cases. [*]I don't know the history, so I dont know the reason why LMH must bring its own private NLog.dll. [*]I don't think that NLog is causing this, I think it is ilmerge that finds something in argus that it links to and this makes the logs only work when the argus dlls are found. [*]The only way that I could see (at least according to the documentation) for ilmerge to ignore resolving the argus references was to use the /internalize switch with an exclusion list that names all dlls except the NLog.dll. I don't think that is a good solution. [/LIST] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Popular Plugins
Fanart Handler
Latest Media Handler v2.4.X.000
Contact us
RSS
Top
Bottom