N
Nak
Hi there,
I have come across a rather frustrating bug with the 2002 VB.NET
Standard IDE. I am currently developing an application framework to use my
my new products, all is pretty straight forward except for when using the
assembly in another assembly. Compiling the applcation that is using the
assembly *should* update its references to any new version, but it does
*not* always do this!
For example, I make a change to my framework, compile and then close the
solution, open the application that is consuming the assembly and recompile
that. The referenced version stays on the previous version! Sometimes I
have noticed that the IDE will even not compile a new version, repeat
attempts will result in the same old version being placed in the bin
directory.
As a solution, close the IDE, restart the PC, load the class library
back up, compile (it should now be updated and placed in the bin directory).
Then open the "consumer" remove the reference to the old assembly, add a new
one and compile. Sometimes I need to even replace and usercontrols with the
new ones, which is pretty strange because I am unsure where the IDE is
caching this old assembly.
Is there any work around for this because its making debugging a
complete nightmare because your unsure whether your changes were even
compiled! I've now started including an assemblyVersion property to all
user controls and components just so I can see quickly whether they are upto
date. Anyway, thanks in advance for any advice on this one.
Nick.
I have come across a rather frustrating bug with the 2002 VB.NET
Standard IDE. I am currently developing an application framework to use my
my new products, all is pretty straight forward except for when using the
assembly in another assembly. Compiling the applcation that is using the
assembly *should* update its references to any new version, but it does
*not* always do this!
For example, I make a change to my framework, compile and then close the
solution, open the application that is consuming the assembly and recompile
that. The referenced version stays on the previous version! Sometimes I
have noticed that the IDE will even not compile a new version, repeat
attempts will result in the same old version being placed in the bin
directory.
As a solution, close the IDE, restart the PC, load the class library
back up, compile (it should now be updated and placed in the bin directory).
Then open the "consumer" remove the reference to the old assembly, add a new
one and compile. Sometimes I need to even replace and usercontrols with the
new ones, which is pretty strange because I am unsure where the IDE is
caching this old assembly.
Is there any work around for this because its making debugging a
complete nightmare because your unsure whether your changes were even
compiled! I've now started including an assemblyVersion property to all
user controls and components just so I can see quickly whether they are upto
date. Anyway, thanks in advance for any advice on this one.
Nick.