A few really annoying VS.NET 2005 ASP.NET bugs
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.
Other Posts you might also like
- Adding minimal OWIN Identity Authentication to an Existing ASP.NET MVC Application
- Resolving Paths To Server Relative Paths in .NET Code
- Map Physical Paths with an HttpContext.MapPath() Extension Method in ASP.NET
- Back to Basics: Rewriting a URL in ASP.NET Core
- Getting the Client IP Address in ASP.NET Core
The Voices of Reason
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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
# re: A few really annoying VS.NET 2005 ASP.NET bugs
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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.
# re: A few really annoying VS.NET 2005 ASP.NET bugs
Im using master pages, but my controls are in the content area ... flaky indeed..
# re: A few really annoying VS.NET 2005 ASP.NET bugs
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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
# re: A few really annoying VS.NET 2005 ASP.NET bugs
Any fixes that anyone is aware of as of yet?
Thanks in advance.
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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.
# re: A few really annoying VS.NET 2005 ASP.NET bugs
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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.
# renaming bug repro steps found
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
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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.
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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.
# re: A few really annoying VS.NET 2005 ASP.NET bugs
# re: A few really annoying VS.NET 2005 ASP.NET bugs
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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.
# re: A few really annoying VS.NET 2005 ASP.NET bugs
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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.
# re: A few really annoying VS.NET 2005 ASP.NET bugs
(http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackid=FDBK44986)
-fastbowler
# re: A few really annoying VS.NET 2005 ASP.NET bugs
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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...
# re: A few really annoying VS.NET 2005 ASP.NET bugs
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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.
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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.
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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!!!
# re: A few really annoying VS.NET 2005 ASP.NET bugs
Yes, deleting the websitecache does work but should we really have to do that?!
Com'n guys. Let's get an SP.
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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.
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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
# re: A few really annoying VS.NET 2005 ASP.NET bugs
# re: A few really annoying VS.NET 2005 ASP.NET bugs
# re: A few really annoying VS.NET 2005 ASP.NET bugs
# re: A few really annoying VS.NET 2005 ASP.NET bugs
<!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>
# re: A few really annoying VS.NET 2005 ASP.NET bugs
Thus my page in I.E. displays error like "Table1 is not a property its a field"
Any help on this would be appreciated
# re: A few really annoying VS.NET 2005 ASP.NET bugs
# re: A few really annoying VS.NET 2005 ASP.NET bugs
<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!
# re: A few really annoying VS.NET 2005 ASP.NET bugs
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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.
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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/
# 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
# re: A few really annoying VS.NET 2005 ASP.NET bugs
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...