Interface Design Question

[Guest]

Hello,

I have an application that allows the user to customize one function
(literally only one function) by specifying a path to an assembly that
contains one class implementing an interface.

public interface ICorrelation
{
public double CalculateHTC(HTCInputs inputs);
}


At runtime, the program loads the assembly and gets a delegate to this
interface.

When the user installs the app, he/she creates a class by referencing one of
the application DLL's for the above interface.


My problem :

The above type i.e. the Interface and the class HTCInputs is not going to
change at all. But the version of the assembly containing the above types
changes every 3 month (development/release).
How can I ensure that the users dont have to recompile their code again and
again to that the new version of application can load the user assembly ?

thank you in advance.

 

[David Browne]

Hello,

I have an application that allows the user to customize one function
(literally only one function) by specifying a path to an assembly that
contains one class implementing an interface.

public interface ICorrelation
{
public double CalculateHTC(HTCInputs inputs);
}


At runtime, the program loads the assembly and gets a delegate to this
interface.

When the user installs the app, he/she creates a class by referencing one
of
the application DLL's for the above interface.


My problem :

The above type i.e. the Interface and the class HTCInputs is not going to
change at all. But the version of the assembly containing the above types
changes every 3 month (development/release).
How can I ensure that the users dont have to recompile their code again
and
again to that the new version of application can load the user assembly ?

Don't change the AssemblyVersion. Just change the AssembllyFileVersion.


David