MP LatestMediaHandler, different APIs
Posted: Sun Mar 06, 2016 5:08 pm
In an attempt to expand my experience, I decided to do my first ever .NET and VS project.
I decided to try to adopt the MP LatestMediaHandler to Argus2.3.
After some fumbling I managed to make something that works on my machine, but for checking in it is necessary to solve two issues:
1. ArgusTV.DataContracts.dll is incompatible between Argus 2.3 and older versions. Backwards compatibility is absolutely necessary.
At least with my limited C#/VS/Windows knowledge it seems impossible to solve.
Even if I somehow manage to fool the compiler, I still don't see how I could add two incompatible dlls with the same name in the same assembly.
Renaming dll's don't help as other argus dll's refer to the datacontracts dll, each expecting a different version and if I rename then it is not found.
2. Compared to the first issue, the second is minor. The API have no method of accessing the logo path, just the logo itself. Older version of this plugin solved it by copying a dll to the project, but that dll is no longer available in ,NET 4.0.
I would appreciate if anyone have any hints that could help me solve these issues.
I decided to try to adopt the MP LatestMediaHandler to Argus2.3.
After some fumbling I managed to make something that works on my machine, but for checking in it is necessary to solve two issues:
1. ArgusTV.DataContracts.dll is incompatible between Argus 2.3 and older versions. Backwards compatibility is absolutely necessary.
At least with my limited C#/VS/Windows knowledge it seems impossible to solve.
Even if I somehow manage to fool the compiler, I still don't see how I could add two incompatible dlls with the same name in the same assembly.
Renaming dll's don't help as other argus dll's refer to the datacontracts dll, each expecting a different version and if I rename then it is not found.
2. Compared to the first issue, the second is minor. The API have no method of accessing the logo path, just the logo itself. Older version of this plugin solved it by copying a dll to the project, but that dll is no longer available in ,NET 4.0.
I would appreciate if anyone have any hints that could help me solve these issues.