views:

2758

answers:

3

I am currently working on a server control for other applications in our company to interface with a WCF service. Every time I make a change code change and recompile the control, I increment the the AssemblyVerison and AssemblyFileVersion class in the AsseemblyInfo.cs by one. For example, my latest build went from 1.0.07.0 to 1.0.08.0.

When the consuming application updates the file by copying the latest file in the bin directory and tries to compile, they receive the following error:

The type or namespace name 'MyControl' does not exist in the namespace 'MyNamespace' (are you missing an assembly reference?)

In order to resolve this error, they have to delete the current reference and re-add the reference.

Is there any way to update the server control without having to delete and re-add the reference?

UPDATE:
I am not strong naming the server control.
@JPunyon - Do you mean have the consuming application add the server control project to their solution?

A: 

Can you add the User Control project to the solution and add it as a reference?

Jason Punyon
A: 

Are you strong-naming your assemblies? In that case it is not a good idea to auto-increment your build number because with every new build number you will also have to update all your references.

0xA3
+1  A: 

Right-click the assembly reference in the solution explorer, properties, disable the "Specific Version" option.

Wim Coenen