Rick Strahl's Weblog  

Wind, waves, code and everything in between...
.NET • C# • Markdown • WPF • All Things Web
Contact   •   Articles   •   Products   •   Support   •   Advertise
Sponsored by:
Markdown Monster - The Markdown Editor for Windows
advertise here

A few really annoying VS.NET 2005 ASP.NET bugs

October 08, 2005   •   47 comments
:P
On this page:

 

In some situations, when I try to rename a control on a form the property editor will not allow me to do it.  This is really annoying especially if I’ve just dropped a control on the page and simply want to give it a new name.

 

Instead I get some odd message:

 

If you have references in the markup they will not be rename.
Do you want to continue?



Really now? And what references might that be? I’ve just dropped you on the damn form <g>…

 

If I say YES, nothing happens. If I say no nothing happens. Convenient. In order to rename the control I have to drop to source view.

 

On other occasions I’ve seen the Refactoring dialogs kick in. They go through the whole project to try to fix references and it’s quite possible that they run into some sort of naming conflict. Besides this process can take a few seconds on a large project.

 

Damn it all I want to do is rename a control!

 

This has been buggy since early betas and I kind of racked that up beta issues, but seeing this now in the RC has me worried. This is a really annoying and time consuming bug if you’re working in design view (which I’m doing less and less because VS.NET’s fluky behavior). Basically I’m using design view only for dropping controls onto the form and setting properties in the property sheet, plus some simple editing.

 

Another really odd bug:

 

I frequently see VS.NET injecting multiple CSS references into my <header> tag:

 

 <head runat="server">

    <title>Untitled Page</title>

    <link href="westwind.css" rel="stylesheet" type="text/css" />

    <link href="westwind.css" rel="stylesheet" type="text/css" />

    <link href="westwind.css" rel="stylesheet" type="text/css" />

    <link href="westwind.css" rel="stylesheet" type="text/css" />

</head>

 

In this scenario I have a user control on the page which has an ‘embedded’ style sheet tag in it so I can design and see the layout properly. So I do:

 

<link href="westwind.css" rel="stylesheet" type="text/css" />

… My Html Markup

 

in the control. I haven’t found another way to see the control styled properly – anybody know of a better way? Anyway, this results in dual style references in a page which is invalid HTML if I forget to the remove the style reference.


I ‘think’ this is what’s causing the dual references above, but I’m not sure. It doesn’t happen instantly and I only notice those piled up references after a while of working on a form.


The Voices of Reason

 

Josh
October 09, 2005

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Hi Rick,

I've been most annoyed with the new 'mixed blessing' web projects - in particular, the way I now have* to add my dlls to sourcesafe.

Because there's no 'project' there's no way to exclude certain files. No fun when there's more than one person working on the project. How are you managing this, have I missed something here?

I realise that you could manually avoid ever adding the bin folder to VSS, but then you can't use MSBuild on the .sln file. It seems that MSBuild doesn't appreciate build order and doesn't copy the dependant DLLs into the web projects Bin folder...

Omar Khan (MS)
October 12, 2005

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Hi Rick,

This is Omar Khan from the Visual Studio (Visual Web Developer) team. We met at the EMP party during the MVP Summit I believe.

My team is very interested in reproducing the issue you mention about rename of the control ID giving you an error. We haven't seen this issue in our own testing and were hoping you might be able to provide more details on it.

Do you have a sample page or project that can demonstrate the problem consistently? If so, would it be possible to share that with us?

Thanks,
Omar

Omar Khan (MS)
October 12, 2005

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Also - my email is omark-at-microsoft-dot-com, you can send details to it.

Jacques
December 07, 2005

# re: A few really annoying VS.NET 2005 ASP.NET bugs

It does this on the RTM. Almost every time I rename a control in webview, it pauses for 3-5 seconds then gives me a "Directory Not Found" error.

I wish I could turn off whatever refactoring stuff is going on behind the scenes and failing.

Setting all other control properties from the designer works fine. I've just gotten in the habit of using source view to name all my controls, then using the designer to set the properties.

Tim Marks
December 15, 2005

# re: A few really annoying VS.NET 2005 ASP.NET bugs

I get the weird renaming thing too! GRRR.
Im using master pages, but my controls are in the content area ... flaky indeed..

Joel Vorpagel
December 15, 2005

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Yeah - today I started a new asp.net project and I ran into he problem with renaming controls. It is really irritating. I drop a control into the design view, I go to the properties box and try to rename the control. I mouse off of the Id property and bang - it reverts back to the default control name plus number. It really prevents you from doing very much in the designer. Really disapointing - is there a fix for this? The weird part is that once it starts happening the only way to fix it is to shut down vs 2005 and restart and reopen your project! Which is also a huge time waster! I'm really not a picky person but this will force me to continue using vs 2003 until there is a fix!

John Marks
December 15, 2005

# re: A few really annoying VS.NET 2005 ASP.NET bugs

I also noticed something else wrong with the design view in vs 2005 asp 2.0 - in all previous versions of vs you double clicked the control on the page and the code behind generated a default subroutine to react to the default event of the control. For some reason, in vs 2005 the control's name is wrong - for example:
You drop a button control in design view. The default button control name is Button1. You rename the button in the properties window to btnMyButton. You double click on it after that, but the code that is generated in the code behind is:

Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles btnNewRole.Click

End Sub

Somehow it hasn't updated the name . . . this seems to be an intermittent problem, but real annoying

R Hoffman
January 06, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

I am in complete agreeance with Joel on this one. I get the same result about renaming the controls.... most annoying for something that simply seems so trivial as renaming a damn control.

Any fixes that anyone is aware of as of yet?

Thanks in advance.

TomYoung
January 10, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

"If you have references in the markup they will not be rename.
Do you want to continue?"
Happens when the control has defined code behind event such as "OnClick". Simply remove the event definition from properties window and try again.


Rick Strahl
January 10, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Tom, you're kidding right? 'Simply remove...' - uh huh, that sounds like something I'd want to do and certainly ALOT easier than changing the script code... NOT!

Richard C.
January 13, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Certainly running into the same control Naming issues in the RTM/Retail versions of VS 2005! On large projects this really sucks, I think we definitely need an refresher update as soon as possible from Microsoft.

Have used VS 2005 RTM daily since November 2005 I have reported the following specific bugs/issues/annoyances:

1. Of course the control rename bug: where it displayed the funky message “If you have references in markup, they will not be renamed. Do you want to Continue?”, no matter what answer you give it does not rename the control. The only way to do this in source. And by the way that’s not an acceptable solution.

2. The Designer properties do not always change as you select different controls on the page. This typically happens when I'm in a solution with 4 or more projects. In other words when you click on control say TextBox1, the properties window will display properties for TextBox1, but when I click on say TextBox2 the properties window continues to display properties for TextBox1. After this happens I can click on 5 or 6 different controls before the properties window finally decides to change the view to the selected control. To force it to change I typically have to click away from the Designer, some times that works, most times I would have to close the page and open it again. Not so easy to reproduce.

3. After several debug sessions for a web project, stopping the debug session and changing anything in class files causes the IDE to crash. This seems to happen whenever the Auto-list members IntelliSense thing is kicking in. This is not specific to any particular syntax, it’s pretty random. Not easy to intentionally reproduce but on a good day I might get this about two or three times.


Solutions are welcome hit me up at rchingombe_at_www.in.gov

C. Moya
January 29, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Yeah, man. ASP.NET 2.0 IDE stuff is foo. I've experienced all the problems mentioned above. The most annoying being the property editor not reflecting newly selected controls (happens with a project of even medium complexity). I have a souped up P-M 2ghz... (about equivalent to a P-4 3ghz or so) with 2GB of RAM... there's no reason for the super-slow dim-wittet web form designer.

But there are ALL SORTS of problems with VS2005 and web projects. Not all of them "user misunderstanding" issues... but flat out BUGS.

Like for instance... Why doesn't the ClassKey property in the Expressions window show resource
files that are in App_GlobalResources??? You have to manually type in the
name of the resource file. Not only that, but even if you type in the name
of the resource file, you still have to manually give it the the name of the
resourse string!!!???? Why no dropdown? Not only that, but if you go back
into it, then a list of resource keys DO show up? Amazing! This is a flat
out bug... not a missing feature or a misunderstanding of the developer's
intent. Whatever programmer was in charge of this feature simply went to
sleep on it.

I could go on and on. VS2003 was a very stable and productive release. In this case the OLD MICROSOFT STEREOTYPE has been PROVEN once again.... Windows 3.0 vs 3.1? NT 3.51 vs 4?... .NET 2.0. You guys (i'm talking to you Omar!) got VS2005/.NET 2.0 WRONG (after three years!).

We NEED 2.1 like NOW!!!!! I don't want "new" features or gee-whiz marketing gimmicks. A nice functional environment that doesn't drive me crazy will do it.

Pete LePage
January 31, 2006

# renaming bug repro steps found

Hi!

The renaming bug that you mentioned above was a hard little bugger to track down, but I wanted to let you know that we've found consistent repro steps and are currently trying to find out what is causing the bug and how to fix it.

In the mean time, I've filed an MSDN feedback bug so that people can track the bug (http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackid=FDBK44986)

thanks!
PEte

Clockworks' Enemy
February 03, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

ugh, this is the buggiest release I have seen in a loong time.

My favorite bug has to be when using the replace in files dialouge, it injects some text in a completely different character set (all I see in the code view is a bunch of ascii boxes), over actaul code. This has happened to me 3 times now, and I end up losing work because I need to revert to previous versions from source safe.

There are issues besides the bugs, like why the hell did they remove the ability to create a typed dataset from xml? Where is the xml view for Datasets? Am I really forced to use the designed to create a DS? Bullocks!


/want's his vs.net 2003 back :(

PS - Clockwork, please stop attending the HALO tournaments, it is obviously effecting your ability to perform your developer duties on the VS team.

Irked Off Developer
February 03, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

I mean seriously,
VS replaced (again) my property and method names with jibberish on EVERY file, in every project in this solution and the funny thing is , these are items that did NOT have a match for what I was finding and replacing.

WTF

If I copy the text out of the code window and past it into notepad, the jibberish disappears and I can then repaste it back into the IDE.

Wow, this is so efficient!

Thanks MSFT for helping me meet my deadlines.

Alan
February 16, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

They show the bug as fixed now. But they also say it happens when more than one instance of VS is open but I can reproduce the issue with only one instance open.

Damon Baker
February 19, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

I am experiencing the same bug with only one VS open. This is big bug. I have quite a number of controls embedded within other controls. I am not a WEB guru and really do not want to parse the page line by line.

Mathieu
March 02, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Found one which is pretty annoying and happens in VS2005 PRO but NOT VisualWebDevExpress ...

I Have a webapp project with 15 files.

when I do ctrl+S or save after a change either in a .cs or .aspx file, vs hangs for 30 secs.

Did a full uninstall and reinstall of VS but no changes. WebDev is still the winner with no such problem detected. Problem is that my VSS doesn't work in WebDev.

Piyush Soni
March 23, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Same problem I'm experiencing....It doesn't allow me to rename the controls by the property page !!

Benoit
March 27, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Hello,

To answer Richard C.
--------------
2. The Designer properties do not always change as you select different controls on the page. This typically happens when I'm in a solution with 4 or more projects. In other words when you click on control say TextBox1, the properties window will display properties for TextBox1, but when I click on say TextBox2 the properties window continues to display properties for TextBox1. After this happens I can click on 5 or 6 different controls before the properties window finally decides to change the view to the selected control. To force it to change I typically have to click away from the Designer, some times that works, most times I would have to close the page and open it again. Not so easy to reproduce.
--------------
I have the same problem, as everybody I guess. And as everybody, I've tried to click everywhere / open / close / switch to code view etc... But I think, it's just (too) slow. So what I do, is select the textbox1 and do my changes then click once on the textbox2 and wait for the textbox2 id to appear in properties windows. It can take up to 5 seconds but at the end, the textbox2 is selected.

Hope this will work for you.

Srinath Nanduri
April 20, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Fixed by following the steps outlined in the following link :
(http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackid=FDBK44986)

-fastbowler

aajay
May 12, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

just go to source and change the control name that's it

Shiro
May 30, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

this bug really annoying = =
not other way to fix it other than follow this
http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackid=FDBK44986

I needs to open 2 IDE at the same time...

Jowen
June 08, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

that link is dead. And the bug is still annoying everybody.

Rhywun
June 15, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

I can't believe we have to wait until the "next version" to fix such a basic bug. Oh wait, yes I can. But yes, deleting the website cache does solve the problem. I guess that's another ritual we'll be adding to our daily routine.

Mathieu,

RE: when I do ctrl+S or save after a change either in a .cs or .aspx file, vs hangs for 30 secs.

Yeah, same here. The "fix" that works for me is to go into RegEdit and clear out the MRU list:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\ProjectMRUList

David Guerra
July 14, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

And what about the new functionality of GoToReference of a procedure. In Vs2003 okey, it sent you to the first method that it found and sometimes it didnt match the one you wanted but it 90% it was the one i wanted. I guess they tried to correct this "bug" in Vs2005, but it sucks. In a large project, for some reason, it tries to refactor the entire proyect and takes a long time, now i use the CTRL+F, :(.
So as the refactor -> encapsulate field. works fine in a small proyect.. but once it grows, the refactoring again. ¿Whats that for? All its added is a simple property! I prefer to do it manually now.

Ben Francis
July 21, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

After downloading a previous version of a VS2005 project and removing the source control files, VS does not display the aspx files in the solution explorer! I can see the aspx.vb files just fine. I can see the aspx files in Windows Explorer, but not in VS.

I've tried the VS2005 way; I've tried the alternative Web Application Projects. It all adds up to months of development time wasted chasing the The Next Big Thing.

Now I have to go back to VS2003, which I should never have left in the first place.

David
August 09, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Have been using Visual Studio 2005 for more than 6 months already. I have years of experience in web development with Microsoft Tools. Visual Studio 2005 is a SCAM, SCAM, SCAM, SCAM! This product was not ready and Microsoft is wasting our time with all these bugs that make their product completelly USELESS!!!!!

Developping ASP.NET 2.0 in Visual Studio 2005 applications impossible and is slow, slow, slow, sloooooooooooooooooooooooooow! No matter how powerful your PC is. This is the slowest IDE I've ever used in my life and it's plagued with serious bugs.

This is another Microsoft disaster!!!

Frustrated
August 24, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Well, Rick first reported this 10/8 of 2005. We're 11 months later and no SP to fix the original issue or the one where the property windows lags way behind.

Yes, deleting the websitecache does work but should we really have to do that?!

Com'n guys. Let's get an SP.

Alex
August 29, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

There's an easier fix for the renaming issue than the one mentioned on MSDN.

When you can't rename a control, just go to your "C:\Documents and Settings\[your username]\Local Settings\Application Data\Microsoft\WebsiteCache" folder and create a folder named as your project. Then try renaming your control again and it should work.

~Alex

Steve
September 20, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

I've had the renaming bug. That's not as bad as MISSING CLASSES!

Anyone else found this? Try to build a custom web control that can do ALL the same things that many Microsoft Controls can do and you'll find that some classes you NEED are missing.

I've even called Microsoft themselves on the phone. They didn't belive me that it was missing. They said I needed to reference the DLL, it IS referenced. But they're still missing.

The most anoying is System.Web.UI.ControlDesigner used along side System.Web.UI.ControlBuilder. But it's NOT THERE!!! I did how ever find it in a diffrent namespace System.Web.UI.Design.ControlDesigner. Yet NOTHING within that class WORKS! I need to overrride GetPersistInnerHtml and GetDesignTimeHTML etc... No luck, again I called Microsoft developer support line. They couldn't help, but the girl on the other end didn't even seem able to understand what I was building, which was a dynamic Collection for a web control. I've managed to program AROUND these bugs and issues in a very crude way, you'll get them if you have a few collections on the one control which need to be updated and managed at both design time and runtime. Try it, you'll see how hard it is to do.

I found lots of bugs. This is REALLY REALLY anoying.

Anyone had "Undefined" issues as well? Objects becoming "Undefined" when yes they are there and yes they are defined? I found the problem goes away when you delete ALL the ASP.NET Tempory Files. This was SUCH a big problem because the System namespace suddenly became "Undefined". How in god's name can that happen? Doesn't make sense, the other programmers here tried to help me fix it, but it caused MORE problems, and we think that when I ran low on space something broke, then when the space is freed up the problem doesn't go away until you delete the Temp files. My Custom web control became "Undefined", then while trying to findout why, the System namespace became "Undefined". Anyone else with this problem? I was forced to Uninstall Visual Studio 2005 since Microsoft couldn't explain why this happened. I reinstalled and it crashes, tried to reinstall again and STILL had the SAME problem with the System namespace. ?? Huh? 3rd attempt at a reinstall, I manually deleted ALL registry entries and ALL the temp files. Problem gone, it took Microsoft 4-5 days to call me back to say they can't understand why that happened. I told them how I fixed it by deleting the Temp files and reinstalling. They had no advice, but this was such a major bug that I couldn't do any work for 4days!! I found that when I had this problem, there was almost a gig of Debug data, Very strange?!?

I've also got problems with MasterPages and the stupidly annoying renaming of the controls within the content area. This just screws ALL my client side JavaScript code. And I've got a really big problem, where a popup web page interacts which JavaScript and objects on the main page, ALL Client-Side. The original version of the site used the same code across the whole site, NOW I must used diffrent JavaScript code because of the MasterPages that are only used on a few of the pages, not the Admin section of the site, nor the popup windows. I hate having 2 sets of code to manage when I should be able to use one. grrr...

It so hard to manage the name effectivly.

I even found really bad problems with the Picture box on windows forms, but those bugs are another matter for another post.

I agree with others when they say "This is another Microsoft disaster!!! " cause it bloody is.

Rick Strahl's Web Log
September 28, 2006

# ASP.NET 2.0 and Visual Studio 2005: You win some, you lose some - Rick Strahl's Web Log

With Visual Studio released now for a few months and many of us spending a fair amount of time in this environment it's time to take stock. For me it's a love/hate relationship with many really useful and productive features and a number of disappointments and productivity slowdowns in some areas.

Saju
November 06, 2006

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Aw goooad..

I cannot believe the guy from the development team. What the hell does he mean that he has not seen the bug.

This is the first bug that everybody experiences ....

Saju

Visual Studio 2005
November 24, 2006

# ASP.NET Forums - Can't UNDO, REDO and change control's ID in Design View


Daniel
January 20, 2007

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Delete the websiteCache, it does work. However, if change its name again, get one message, "failed to find definition." What wrong, another bug?

Bhaskar and Shiva
March 23, 2007

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Well, guys we had the same error.."Failed to find definition"..close the IDE and reopen it, change the name of the control and it works. This is our Jadooo....

Jack
March 27, 2007

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Add a couple more things into VS 2005. Saving the style sheet crashes VS2005. Not the first time, but the second time you save it, down the program goes. and my </form> tag keeps bouncing around on my home page. On start up I always have to track down where the blasted thing went THIS time, and move it back to where its supposed to be.

bal
May 08, 2007

# re: A few really annoying VS.NET 2005 ASP.NET bugs

I am using VS2005 with VB.net. We have implemented an asp.net solution that uses app_themes, however I have a very annoying duplication issue which I am unable to resolve. When I run the solution then view the source in a browser, using i.e and firefox, I get duplicate references. The same css file is showing in the html as being referenced twice. Any help on this would be appreciated. i.e.

<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en" xmlns="http://www.w3.org/1999/xhtml">
<head><link href="App_Themes/Standard/clearance.css" type="text/css" rel="stylesheet" /><link href="App_Themes/Standard/handsetList.css" type="text/css" rel="stylesheet" /><link href="App_Themes/Standard/msc.css" type="text/css" rel="stylesheet" /><link href="App_Themes/Standard/portalStyles.css" type="text/css" rel="stylesheet" /><link href="App_Themes/Standard/rafriend.css" type="text/css" rel="stylesheet" /><link href="App_Themes/Standard/shopStyles.css" type="text/css" rel="stylesheet" /><link href="App_Themes/Standard/tariffandplan.css" type="text/css" rel="stylesheet" /><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />

<link href="App_Themes/Standard/clearance.css" type="text/css" rel="stylesheet" /><link href="App_Themes/Standard/handsetList.css" type="text/css" rel="stylesheet" /><link href="App_Themes/Standard/msc.css" type="text/css" rel="stylesheet" /><link href="App_Themes/Standard/portalStyles.css" type="text/css" rel="stylesheet" /><link href="App_Themes/Standard/rafriend.css" type="text/css" rel="stylesheet" /><link href="App_Themes/Standard/shopStyles.css" type="text/css" rel="stylesheet" /><link href="App_Themes/Standard/tariffandplan.css" type="text/css" rel="stylesheet" /></head>

rv
May 28, 2007

# re: A few really annoying VS.NET 2005 ASP.NET bugs

i used one aspx page(VS 2005;using master page) for creating controls on the fly, controls are generated inside one server control "Table" with id="Table1", but on execution this table is always renamed by VS to "ct100_ContentPlaceHolder<any no.>_Table1" or sometimes as "ct100$ContentPlaceHolder<any no.>$Table1"
Thus my page in I.E. displays error like "Table1 is not a property its a field"

Any help on this would be appreciated

ASP.NET Forums
June 18, 2007

# Can't UNDO, REDO and change control's ID in Design View - ASP.NET Forums


Tony Redmond
June 29, 2007

# re: A few really annoying VS.NET 2005 ASP.NET bugs

I have found this to be very annoying as well but what I have detemined is that if you change the name of the object (control) prior to chaning any other property you can avoid this annoyance. Give that a shot.

Ignus Bezuidenhout
July 12, 2007

# Visual Studio web Form Designer message "If you have references in markup, they will not be renamed"


djenryte
July 17, 2007

# re: A few really annoying VS.NET 2005 ASP.NET bugs

In regards to Gal's post on May 8th, 2007 and Rick's original post. I am experiencing the same dual reference behavior on my Asp.net/C# web application. 

<head>
<link href="App_Themes/Default/Calendar.css" type="text/css" rel="stylesheet" />
<link href="App_Themes/Default/Styles.css" type="text/css" rel="stylesheet" />
<title>    Welcome!</title>
<link href="App_Themes/Default/Calendar.css" type="text/css" rel="stylesheet" />
<link href="App_Themes/Default/Styles.css" type="text/css" rel="stylesheet" />
</head>


This has gone unnoticed for quite some time. The problem occurs on every single page of my ASP.net web app. Quite frustrating. I only recently discovered the issue while experimenting with the Firefox Firebug tool. Any help would be appreciated!

Rick Strahl
July 17, 2007

# re: A few really annoying VS.NET 2005 ASP.NET bugs

I haven't seen this problem in some time, so I think it might have gotten fixed in SP1.

Akash Kava
August 24, 2007

# re: A few really annoying VS.NET 2005 ASP.NET bugs

What a crap ASP.NET 2.0,

Bugs...

Cascading Drop Downs !!! Biggest bug, however I posted solution today at code project...

Most Annoying Bug.....

Unable to set Web User Control properties at design time, especially in template parts. Microsoft feels proud to design Template method and worst ever way to code and enter properties, like if I am back to "Non Intellisence, Non Visual" Editor of Visual Studio, and some times it appears and sometime it doesnt.

Somewhere I read that if compilation error occurs, it doesnt work, however this is not completely true.

Do you guys know that every List Control based control inside Insert and Update Templates of FormView gets created twice when you post back. I came to know when I created Drop Down List, put it inside FormView, I monitored the Constructor !!! and on one post back, I saw it doing this twice.

Another Annoying factor, Microsoft hided every code which you can probably use to create your own data bound template based control.. I wanted to create DataPanel derived from Panel and which is a naming container but easily editable panel and to avoid FindControl all the time. Guess what, its big secrete by microsoft to load posted values of Data Bound controls.

Microsoft went ahead made ASP.NET 3.0 and belive it guys its true, not even 2.0 is stable with bugs, they went ahead with 3.5, with WPF is the greatest invention with practically impossible to understand fundamentals of Custom or User controls. Everything is templated and themed inside some stupid xml file which no editor can open and edit. However unless you run, you never realize how it is going to look like.

C# 3.0 VAR and LINQ ... great, after creating such great Type oriented language, microsoft now going in direction of QBasic and making everything look so unorganized, they forgot that middleware maintains types and they dont want you guys to code in 3 tire architecture any longer.

Computer Videos
December 20, 2007

# re: A few really annoying VS.NET 2005 ASP.NET bugs

Thank you Alex, your solution really help.

As you said we need to create a folder in this directory:

C:\Documents and Settings\[Your name]\Local Settings\Application Data\Microsoft\WebsiteCache

I tried this option and it is really working ok for me regarding control renaming.

Thank you!

:o)

Cheers!

http://computervideos.110mb.com/

Ali Muhammad
January 21, 2008

# re: A few really annoying VS.NET 2005 ASP.NET bugs


I have also face this same problem of renaming while renaming any webcontrol.

I resolve that issue by editing renaming control name property from source

<asp:TextBox ID="txtname" runat="server"></asp:TextBox>

txtname wase TextBox1 ....

There is logicall justification of this silly buggg...
if any buddy solve it logically by using any .net ide patch then kindly email me .
regards

West Wind  © Rick Strahl, West Wind Technologies, 2005 - 2025