Correct way to get an updated control or DLL?

[Cristof Falk]

Can someone tell me the right way to get an updated .NET DLL (written
in C#) or control for an ASP.NET application? I have copied the
executable to the <project>/bin on the web server. I then delete the
reference (for the DLL) or reconnect the control, and rebuild the
application. It builds ok, but when I run it, pages say that the
assembly version does not match, and it shows the previous version as
what it is looking for.

I've added the control (Dundas Chart) to the assembly info in the
WebInfo (?) and it sometimes helps for one run before it reverts.

As far as I know, ASP.NET does not have regular manifests.

I have Google-d extensively, and haven't found an answer that meets
this. It's not the 64K limit issue.

This is on VS.NET 2002.

Thanks!

[Cristof Falk]

Any ideas, please? I'm really struggling with this.

On Sat, 01 May 2004 14:01:37 -0700, Cristof Falk
<cf**@critterdesign.net> wrote:

Can someone tell me the right way to get an updated .NET DLL (written
in C#) or control for an ASP.NET application? I have copied the
executable to the <project>/bin on the web server. I then delete the
reference (for the DLL) or reconnect the control, and rebuild the
application. It builds ok, but when I run it, pages say that the
assembly version does not match, and it shows the previous version as
what it is looking for.

I've added the control (Dundas Chart) to the assembly info in the
WebInfo (?) and it sometimes helps for one run before it reverts.

As far as I know, ASP.NET does not have regular manifests.

I have Google-d extensively, and haven't found an answer that meets
this. It's not the 64K limit issue.

This is on VS.NET 2002.

Thanks!

[Cristof Falk]

Any ideas, please? I'm really struggling with this.

On Sat, 01 May 2004 14:01:37 -0700, Cristof Falk
<cf**@critterdesign.net> wrote:

Can someone tell me the right way to get an updated .NET DLL (written
in C#) or control for an ASP.NET application? I have copied the
executable to the <project>/bin on the web server. I then delete the
reference (for the DLL) or reconnect the control, and rebuild the
application. It builds ok, but when I run it, pages say that the
assembly version does not match, and it shows the previous version as
what it is looking for.

I've added the control (Dundas Chart) to the assembly info in the
WebInfo (?) and it sometimes helps for one run before it reverts.

As far as I know, ASP.NET does not have regular manifests.

I have Google-d extensively, and haven't found an answer that meets
this. It's not the 64K limit issue.

This is on VS.NET 2002.

Thanks!