Code changes ignored

[Waldy]

Hi there,
a customer has an .ASP .Net application that I have written
for them. They recently requested a minor change to a SQL statement that
loads a drop down. I made the change and supplied them with the updated .VB
file. However, the changes are ignored by the application. I have even
dialled in to their system and completely changed the SQL statement to
return rubbish but the changes are not recognised by the application. I
rebuilt the application when I made the code change here, and it did not
update the .DLL so I only sent the .VB file to the customer. The change
works fine on my machine but not the customers. There must be something
blindingly obvious that I have missed. Can anyone please shed some light on
this.

[Rob Amos]

If you're using code behind then giving them the .vb file will have no
effect, the code is compiled into the .dll. (unless you explictly tell the
page you are fixing to use late binding). When you rebuilt the app it should
have updated the dll, that seems to be the issue. Are you sure there were no
build errors? can you check the properties of the project to verify the path
to the dll?

Rob

"Waldy" <wa***@notmail.com> wrote in message
news:u2**************@TK2MSFTNGP15.phx.gbl...

Hi there,
a customer has an .ASP .Net application that I have written
for them. They recently requested a minor change to a SQL statement that
loads a drop down. I made the change and supplied them with the updated
.VB file. However, the changes are ignored by the application. I have
even dialled in to their system and completely changed the SQL statement
to return rubbish but the changes are not recognised by the application.
I rebuilt the application when I made the code change here, and it did not
update the .DLL so I only sent the .VB file to the customer. The change
works fine on my machine but not the customers. There must be something
blindingly obvious that I have missed. Can anyone please shed some light
on this.

[Mark Rae]

"Waldy" <wa***@notmail.com> wrote in message
news:u2**************@TK2MSFTNGP15.phx.gbl...

a customer has an .ASP .Net application that I have written for them.
They recently requested a minor change to a SQL statement that loads a
drop down. I made the change and supplied them with the updated .VB file.
However, the changes are ignored by the application. I have even dialled
in to their system and completely changed the SQL statement to return
rubbish but the changes are not recognised by the application. I rebuilt
the application when I made the code change here, and it did not update
the .DLL so I only sent the .VB file to the customer. The change works
fine on my machine but not the customers. There must be something
blindingly obvious that I have missed. Can anyone please shed some light
on this.

There's no point sending the .vb file to the customer - those files are used
only to store your VB.NET code-behind.

You need to rebuild your ASP.NET application in Release mode and then
redeploy the DLLs from your \bin folder into the equivalent \bin folder on
the client's web server.

[Waldy]

Sorry,
I was looking at the wrong .DLL! I opened the .DLL in notepad and
you can clearly see that the SQL statements are held within.

Thanks.