Hi there,

I have come across a bit of an annoying bug, all of a suddent VB.NET is
packaging old versions of my assemblys into the into my deployment package.
I can confirm that it is doing this by deleting the assemblys from the
projects Bin folder as well as the output of the deployment projects build
and then recompile. The files are replaced but for some strange reason they
do not match!

This is very irritating a quite similar to the licensing issuses that I
face regularly in VB.NET when the IDE *forgets* to embed the licenses file
as a resource into the assembly. Simply restarting the computer and
rebuilding can fix this issue!

Any ideas? This is doing my nut in!

Nick.

Hi there,

I found the fix, I needed to visit the small green fairy in the land of
make believe and request 3 wishes, firstly that I could be blessed with an
IDE that functions correctly, secondly that I would not encounter any more
mysterious issues and lastly that if I restart my computer yet again that
all problems would be resolved. Thus and so I am functional once more, damn
and blast for the law of the sod, and the VB.NET 2002 IDE, gawd bless it's
"soul".

Nick.

"Nak" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi there,
>
> I have come across a bit of an annoying bug, all of a suddent VB.NET
> is packaging old versions of my assemblys into the into my deployment
> package. I can confirm that it is doing this by deleting the assemblys
> from the projects Bin folder as well as the output of the deployment
> projects build and then recompile. The files are replaced but for some
> strange reason they do not match!
>
> This is very irritating a quite similar to the licensing issuses that I
> face regularly in VB.NET when the IDE *forgets* to embed the licenses file
> as a resource into the assembly. Simply restarting the computer and
> rebuilding can fix this issue!
>
> Any ideas? This is doing my nut in!
>
> Nick.
>