Friday, July 21, 2006
Error Reporting - To send or not to send?
Don't think of it as 'can I be bothered to help Microsoft find their bugs' button. Think of it as a 'vote for this f#$%ing issue to be fixed' button. I find that clarifies the decision somewhat...
Broken URLs
Whyohwhyohwhy can't browsers deal with urls with line breaks being pasted into the address bar? All but the shortest urls get broken in emails, and yet the blindingly obvious solution (no it's not Shrinkster) still evades us.
Even a menu option ('Navigate to mangled url in clipboard') would do.
Even a menu option ('Navigate to mangled url in clipboard') would do.
Friday, July 07, 2006
Avoid solution folders in VS2005 for your UserControl projects
In VS2003, whenever you had a form open in the designer, any user controls in your project[*] appeared in a 'My User Controls' tab on the toolbox.
This was essential because (for some reason unbeknownst to man) you can't drag a WinForms user control from the Solution Explorer onto a form, you have to do it from the toolbox (which sucks: the ASP.Net team managed it just fine, so what's the issue?).
In VS2005 the same functionality exists (with the additional feature that it can be disabled for performance reasons with the AutoToolboxPopulate option). But it doesn't work - or not for us at any rate.
Eventually it turns out (thanks Cam) that it doesn't work for projects within solution folders. How crazy is that?
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=114542
...so I'm crossing fingers for SP1 (whenever that comes out).
[Update: Didn't publish this for ages, but no, SP1 doesn't fix it. Poo]
This was essential because (for some reason unbeknownst to man) you can't drag a WinForms user control from the Solution Explorer onto a form, you have to do it from the toolbox (which sucks: the ASP.Net team managed it just fine, so what's the issue?).
In VS2005 the same functionality exists (with the additional feature that it can be disabled for performance reasons with the AutoToolboxPopulate option). But it doesn't work - or not for us at any rate.
Eventually it turns out (thanks Cam) that it doesn't work for projects within solution folders. How crazy is that?
"The fix probably won't make it into Service Pack 1, but I will forward your feedback to the appropriate team for consideration."However the bug reports says it's fixed already:
[Ben Bradley, MSFT, link above]
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=114542
...so I'm crossing fingers for SP1 (whenever that comes out).
[Update: Didn't publish this for ages, but no, SP1 doesn't fix it. Poo]
Subscribe to:
Posts (Atom)
Popular Posts
-
Summary: Even if you think you know what you're doing, it is not safe to store anything in a ThreadStatic member, CallContext or Thread...
-
I love PowerShell, and use it for pretty much everything that I’m not forced to compile. As a result I’ve got fairly competent, and people h...
-
Look, it’s really not that hard. Programs are still in the same place, in %ProgramFiles%, unless you need the 32 bit version, which is in...