ASP.NET Weblogs

Welcome to ASP.NET Weblogs Sign in | Join | Help
in Search

Josh Schwartzberg high-fives the CLR

and plays with his shiny golden hammer....

Removing HTML Auto-ID-Population in Visual Studio .NET (2003)

I've searched the internet high and low for a solution to this problem.

My current occupation requires me to support the now legacy ASP 3.0 language.  Naturally... my IDE of choice/usage is Visual Studio .NET 2003... it really does a great job of almost everything.  The only major complaint I have is the auto-ID-population of many HTML elements (such as INPUT) when you do a copy and paste with these elements.  I'm sure most of you have seen this major annoyance.  I understand that every element SHOULD have a unique identifier, but I'd rather handle that on my own, not have VS.NET creating a text1, text2, text3 for me, when I just have to go back and change it.

How to reproduce:
just copy and paste this     <input type=text>     into visual studio.net 2003 on a page recognized by the IDE as an HTML page (You are going to have to use the PASTE AS HTML option).... and watch the auto ID creation begin.

I have seen posts from microsoft rep's saying they there is no way to disable this in the current versions.  But with an Visual Studio .NET 2003 API, anything is possible.

So does anyone have a solution, script, crack, or prayer to disable the VS.NET HTML Auto-ID-Population setting?

Published Jan 06 2004, 02:01 PM by dotjosh
Filed under:

Comments

 

Alexandre Rocco said:

Looking forward to this one too. It's a big pain when you copy a huge file to another and it creates such auto IDs. I have the same problem on VS2002 and VS2003.

-- Alexandre
January 6, 2004 2:32 PM
 

Frans Bouma said:

Can't be switched off, together with the auto-html formatting 'feature'... I haven't checked if whidbey still does this...
January 6, 2004 2:34 PM
 

David Cumps said:

I hope it can be turned off in the future :)
January 6, 2004 4:46 PM
 

Alexandre Rocco said:

Maybe doing a find/replace with a nice RegEx would do the trick. I will try to come up with one and give it a shot! :)

-- Alexandre
January 7, 2004 6:00 AM
 

Eric Carlisle said:

Been hunting around for a solution to it. Here's a fix!
BOOYA!

http://www.codeproject.com/macro/wiicwgp.asp
April 13, 2004 1:32 PM
 

TrackBack said:

^_^,Pretty Good!
April 10, 2005 4:59 AM

Leave a Comment

(required) 
(optional)
(required) 
Submit