Pages "stuck" unless debugged...

Here's something really bizarre that I've not encountered in my 4 yrs. of
..NET development which hopefully, someone here can provide an explanation
for...

I've inherited an in-house app which is very poorly written (spaghetti code,
huge footprint, super-slow, hard to maintain, no standards or consistency,
etc.) This thing has a few demons in it but this one is most disruptive.

I can, for example, add a new feature to a page or fix a big and then go
back and run the application to test it. In many cases, until I run the app
through vs.net in debug-mode the changes/fixes just won't "appear". That
is...I can't see my changes until I run the debugger...then the app begins to
behave as expected...but not until then.

Nothing is being cached (neither client or server-side).

What would cause this?

=?Utf-8?B?emFtYml6emk=?=

Make sure that the complete solution is re-built. When you start debugging
the IDE does a re-build, so you'll find it all fine.

Check if the start project has any project/assembly references and they're
all current before you run it.

"zambizzi" <> wrote in message
news:0652159D-1D2F-4EDF-B87B-...
> Here's something really bizarre that I've not encountered in my 4 yrs. of
> .NET development which hopefully, someone here can provide an explanation
> for...
>
> I've inherited an in-house app which is very poorly written (spaghetti
code,
> huge footprint, super-slow, hard to maintain, no standards or consistency,
> etc.) This thing has a few demons in it but this one is most disruptive.
>
> I can, for example, add a new feature to a page or fix a big and then go
> back and run the application to test it. In many cases, until I run the
app
> through vs.net in debug-mode the changes/fixes just won't "appear". That
> is...I can't see my changes until I run the debugger...then the app begins
to
> behave as expected...but not until then.
>
> Nothing is being cached (neither client or server-side).
>
> What would cause this?

mallik