Assembly Reference

[Bryan Dickerson]

I am working on a .Net Assembly (better known as a DLL, but if my boss heard
me say "DLL", now, he would correct me and 'make sure that he and I were
talking about the same thing' *RollsEyes*) and I am finding that, in my test
client, if I don't delete the reference after I've re-built the DLL, then I
don't get the latest build. Why do I have to keep re-referencing the DLL or
what am I missing? I know that .Net gets rid of DLL-Hell, but this is going
a bit far, isn't it?

 

[Guest]

Each assembly has a version that goes with it. .NET fixes the problem of DLL
hell by versioning assemblies so you cannot possibly use the wrong version.
This is also what is causing you headaches. Each time you rebuild the DLL it
creates a new version automatically. If you want to disable this, just
manually set the AssemblyVersion in the AssemblyInfo.vb file. The default
version for components uses the "*" character that will increment each build.

 

[The Grim Reaper]

I thought the * created a random version number (based on god-knows-what
data) and didn't auto increment as it used to in VB6??
_____________________________________________
The Grim Reaper