moving to 1.1 - codebehind not compiling

[Dude]

I migrated to 1.1 Changes I make to the aspx page are fine, changes to
codebehind page are not reflected after I compile and view in the
browser. I deleted all the files from the cache directory on the
server.

[Martin Maat]

If you want instant results after updating source outside Visual Studio, you
should use Src instead of Codebehind in your page directives. Codebehind is
something Visual Studio recognizes and works with, it means nothing to
ASP.NET hence ASP.NET won't find your code when it is time to recompile.

The docs say that Visual Studio will choke on the Src attribute, I don't
know if you would get away with using both Src and Codebehind. Check it out
and tell us how it really works.
"Dude" <ho********@yahoo.com> wrote in message
news:5a**************************@posting.google.c om...

I migrated to 1.1 Changes I make to the aspx page are fine, changes to
codebehind page are not reflected after I compile and view in the
browser. I deleted all the files from the cache directory on the
server.

[Dude Man]

I am using studio.net 2003

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Martin Maat]

> I am using studio.net 2003

Then rebuild your application after you made the changes.

[Dude Man]

I did...
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Martin Maat]

> I did...

I knew you were going to say that.

- Do you see a virtual directory named after your web project in IIS ?

- Do you have a bin directory in your web project directory?

- If you do have that bin directory, you open a command prompt in your
project directory and you rebuilt your page manually like:

csc /t:library /out:bin\yoursourcefile.dll yoursourcefile.cs

do you then see the updated page in your browser? (if you use Visual Basic
instead of C#, replace any cs occurence with vb)

Martin.