Ever since I upgraded to VS2005 SP1 I've experienced the problem where I'll add a control, or change the ID of a control in an ASPX page, but the associated codebehind doesn't learn about the change/addition, often until I restart Visual Studio.

Now all of a sudden, no matter what I do, Visual Studio will not believe me that a particular control exists on the page. I'v restarted the machine and Visual Studio several times.

Please HELP!

Aaron

Small update:

It's definitely related to renaming a control. A textbox in this case. It gives me a bc30456 error: xxxx is not a member of yyyy. I changed the name back, restarted VS and I'm fine. Very weird though, and very frustrating.

Aaron

In VS2003 you can get the same problem if, on a web form, you add a control by typing in the physical tag and then switch to your code behind, you will not be able to access that control until you switch to the designer view and the control is rendered on the page. Not sure if this relates to your problem or not.

================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
^^Took that from planoie's profile^^
^^Modified text taken from gbianchi profile^^
================================================== =========
Technical Editor for: Professional Search Engine Optimization with ASP.NET
http://www.wiley.com/WileyCDA/WileyT...470131470.html

Discussion:
http://p2p.wrox.com/topic.asp?TOPIC_ID=56429

I remember that about VS2003. It was because adding a control to the design view of the page, also added a declaration in a hidden section of the codebehind. If you added it to the html you had to also manually add it to the declarations. It was one of the things I hated about 2003. Since 2005 did away with that model, and indeed most of the painful aspects of 2003, that doesn't apply in this case unfortunately. Thanks for responding though. :)

Aaron