Reference conflict

[blar58]

Hello

I have a problem with references conflict.
I am using Xceed dll in my indicators to get a nice property grid.
Now one of my customer is using another indicator that uses the same Xceed reference but not the same version.

Obviously that creates a conflict and causes compiling problems so both indicators cannot work at the same time.

What can I do on my side that could fix this problem ?

Thank you

[NinjaTrader_Kate]

Hello blar58,

Thank you for your post.

It sounds like this DLL isn't one you created. The developer of the DLL would need to change the class names in the version of the DLL you're using and change the file name in order for this to work. If it is one you created, you could make those changes yourself since you'd have access to the source code.

Alternately, you could modify your script to use the same version of the DLL that the other assembly is using - this would likely be the simplest route.

Please let us know if we may be of further assistance to you.

[blar58]

Thanks Kate

No I am not the one who created the DLL file.

Now I would be really interested in modifying my script to use the same version of the DLL.
Could you guide me in how to do this ?

Thanks again !

[NinjaTrader_Kate]

Hello blar58,

Thank you for your reply.

I don't have a step by step guide for you, but essentially what you would need to do is to remove the DLL assembly you're currently using, import the assembly they are using, modify your code, and then consult the developer of the DLL for any issues with using that version.

Please let us know if we may be of further assistance to you.

[blar58]

Kate
Thank you for your reply.
I just got an idea and would like to know what you think about it.

If from the Editor I right click ( references window ) and change the Xceed directory to get the other version ( which I put in another directory ) would that work ?

That would imply that my customer would have to copy his version to the same directory I have created.

Or even better what if I ask my customer to put my version in another directory other than custom directory and change the reference directory from the Editor ?

[NinjaTrader_Kate]

Hello blar58,

Thank you for your reply.

The reference that you make to the other assembly would need to have the same path as where it is placed by the other installation since you don't have control over where that programmer placed their reference. The conflicting assembly would need to be removed and could not be in a different directory as you'd still get errors when trying to compile that.

Please let us know if we may be of further assistance to you.