ASP.NET 2.0 Multiview Control makes VS Designer harder
Frustrated :( I like VS 2005, but I really don't like ASP.NET 2.0 Multiview Control. It was suppose to save my day with tab pages on web applications. But I had a few problems and it was slowing down my development work.
Before I share with the problems I have. This was what I had done.
I had a mutltview, 3 views and 1 menu controls. I wanted to achieve something like window forms tab pages. It could be done. I had also written a bunch of CSS and applied these styles to my multiview.
Currently, I am using P4 1.9 GHz (not the fastest in the market) and 1GB of SD RAM (think so).
Ok I am done. Back to my topic, you will face a lot of issues in VS 2005 designer when you want to have mutliple asp.net 2.0 standard controls on top of your multiview control.
The simplest example, "most of the time" I was not able to change my controls ID like label, textbox or calendar. I had to change inside my html code. You can also see the multiview control refreshes a lot of times in VS 2005 designer. Sometimes I tried to change properties for button 1, but it ended up applied in button 2 or 3. Weird huh?
Wonder other people faces this problem too? Or there is something wrong with my code or machine. [Shy :( ]