Re: Help with VS designer messing up HTML!
From: Stuart Campbell (stuart.NOSPAMcampbell4_at_btinternet.com)
Date: 03/15/04
- Next message: JH: "launch condition (setup and deployment)"
- Previous message: tony: "RE: Back Button"
- In reply to: Pat: "Re: Help with VS designer messing up HTML!"
- Next in thread: Pat: "Re: Help with VS designer messing up HTML!"
- Reply: Pat: "Re: Help with VS designer messing up HTML!"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 15 Mar 2004 16:10:38 +0000 (UTC)
Thanks Pat. Commenting the LINK tag out is indeed a workaround.
But I think you will agree with me that it is in no way acceptable that we should have to do
this in Microsoft's flagship IDE nearly a year after this second version was released!
And now I hear Whidbey is to be delayed further...
Please Microsoft! Where are the service packs/patches/hotfixes/updates?
"Pat" <lest3560@bellsouth.net> wrote in message news:FHQ4c.60688$JN2.8613@bignews4.bellsouth.net...
> I definitely don't figure that this is the recommended way...........but
> what I do, is just comment out the "bad lines" when i want the view the
> designer view. This has been my workaround (if Im understanding the problem
> right). Works for me. Let me know if I'm not approaching the problem
> correctly.
>
>
> "Stuart Campbell" <stuart.NOSPAMcampbell4@btinternet.com> wrote in message
> news:c2s9le$oj8$1@titan.btinternet.com...
> > Hi,
> >
> > Is there any way of preventing the VS.NET designer from reformatting my
> HTML every time I move something on the webform?
> >
> > My problem is this:
> >
> > I wanted server-side access to the LINK tag. I added runat="server" and an
> id...Perfect! I could work with it as I expected.
> > However, the minute I change something on the form VS.NET removes the
> closing tag and causes a parser error on the next run:
> > Unexpected end of file looking for </link> tag.
> >
> > I couldn't live with this. So I decided to set the HEAD tag to run at
> server. then I programmatically created a LINK control
> > (HtmlGenericControl) and added it the head tag's control collection.
> Perfect! I thought I had out-smarted VS.NET :D....
> > However...the VS.NET designer also messes up the HEAD tag!!! It reformats
> it so that the id="ctlHead" is on a new line. As a result
> > the Head tag is no longer available on the server!! Go figure! So VS is
> naughty because it reformats and ASP.NET is naughty because
> > it doesn't read in the attributes that are on a new line.
> >
> > It is very frustrating! I am aware that Whidbey is going to be a lot
> better when it comes to preserving your HTML...but what happens
> > in the mean time? Are there going to be any patches?
> >
> > TIA
> > --
> > Stuart Campbell
> >
> >
>
>
- Next message: JH: "launch condition (setup and deployment)"
- Previous message: tony: "RE: Back Button"
- In reply to: Pat: "Re: Help with VS designer messing up HTML!"
- Next in thread: Pat: "Re: Help with VS designer messing up HTML!"
- Reply: Pat: "Re: Help with VS designer messing up HTML!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|