ASP.NET and IIS totally ignoring vb codebehind changes

I have a page MyPage.aspx

I have a codebehind MyPage.aspx.vb

I deployed to IIS box, it ran okay, I saw something I wanted to change, so I modified the vb file.  IIS is ignoring the change, same content is displayed WITH THE EXCEPTION of a time label I put on the form to ensure that the page content wasn't cached locally.

Every time I refresh, the time changes, but new code changes are ignored.  I even renamed the vb codebehind file and the app still runs.

It appears to me that IIS is not sensing the code change and is running a compiled version of my code.  I am deploying just by copying local aspx, vb, etc files to the server.

Stopping IIS no effect.  Recycling app pool no effect.

This is VS 2008 3.5 framework IIS 6 VB.NET

Regards, all.


Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

try deleting the server cache, for 2.0+, on the web server, it's located at:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files

Everything in there can be deleted...if you find a file is locked....try stopping IIS before you delete...
JXCovertAuthor Commented:
Thanks Sam..

Tried it, but No Dice.  I have recreated the Virtual Dir.  Stopped IIS,  Deleted temp files.  Stopped the web site.  Renamed files.  Nothing works.  

I even rebooted my web server, then renamed the code behind file to comething other than what is referred to in the aspx.  IIS insists on running some phantom piece of code somewhere.
Use publish feature in Visual Studio or Copy ALL files and directories again, not only your modified file.
JXCovertAuthor Commented:
This remains a mystery, at least to some extent.  The project was a Web Application, when we "converted" to a Web Site, it began to behave in a more expected manner.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.