Bug?? SP1, WAP with Designer files?

Last post 05-08-2007 8:51 AM by caileanadriyel. 2 replies.

Sort Posts:

  • Bug?? SP1, WAP with Designer files?

    04-10-2007, 9:31 AM

    I am using VS 2005 SP1 WAP and cannot drag and drop any standard control into the designer mode or the source mode and have it appear like it should on the designer.vb page. For instance: in dsigner mode I drag a textbox onto the screen. When I go into the code behind it doesn't have any idea what "TextBox1" is. This has happened for any control I try, dropdownlists, datasources, gridviews, etc. If it try to copy some markup (that contains valid asp.net controls) created in a pre-sp1 project into the source page the same thing happens, the designer has no idea what to do with it.

    <pause for a test in visual studio>

    I just read another post of someone who is frustruated with the designer files and I think he may have hit the nail on the head (http://forums.asp.net/thread/1441790.aspx). He pointed out that it could be a bug with the auto detection and DIV tags. I am using CSS and DIV's with nested DIV's to layout my site. I just tried to drag a textbox control onto the page in source mode in an area outside of any DIV tags and the designer detected it and declared it without any problem. Is this a bug in VS 2005 SP1 WAP model??? If so who should I contact to get it fixed. I am  sure I am not the only one experiencing this difficulty as I have read other similar posts from people who are having designer.vb/c problems.

     Thanks,
    Cailean Adriyel

  • Re: Bug?? SP1, WAP with Designer files?

    04-25-2007, 4:08 PM
    This problem is really really annoying. Some days it is ok and other days it doesn't recognize a single control does anyone have any ideas???
  • Re: Bug?? SP1, WAP with Designer files?

    05-08-2007, 8:51 AM

    I am still hoping that someone can offer some insight into this issue I know I am not alone in this. While I realize that I can add the control's declaration to the designer file myself (and I have been) that isn't how Visual Studio was designed. This makes VS quite annoying to use.

     

    Thanks,

      CaileanAdriyel

Page 1 of 1 (3 items)