Help Improve Visual Studio.NET 2005
Posted in Development
This one goes to all of you, developers and designers, regardless of whose war camp you are in. I’ve submitted two issues with Visual Studio.NET 2005 Beta 2, FDBK25806 and FDBK25803, via the MSDN Product Feedback Center which I deem critical, and I need your input or vote to have both resolved by the time VS.NET 2005 ships.
Here’s one of the issues. At this time, in Visual Studio.NET 2005, the DTD picker is missing XHTML 1.0 Strict, while the Transitional and Frameset are there (see image below):
Apparently, someone over there thinks that the difference between XHTML 1.0 and XHML 1.1 is so negligible that XHTML 1.1 takes the place of both. I’m appalled.
I do not sugges heading to the MSDN Product Feedback Center to flame Microsoft over petty issues. God forbid! That’s what blogs are for. Enough bitching at Microsoft goes around, so now is your chance to offer constructive criticism and help us receive an outstanding product.
If you’ve got nothing to say, at least please vote. Your vote counts. Thanks, everyone!
3 comments
Milan Negovan
on May 5, 2005
They did close the submission, but we're still dicussing it off-stage.
Masklinn, what "security number thing" are you talking about?
Masklinn
on May 9, 2005
In your submit form, there is a "Type in the number above:" zone with an image number above it.
This number does not display in my Firefox, and it doesn't look like adblock's blocking it.
Opera and IE6 render it just fine, my firefox doesn't accept it and i just get "Enter this number".
(Which shouldn't be the alt text, since you probably want it to display as a help tooltip, you should use the "title" attribute)
(oh and that feature prevents any text-based or image-off browsing from posting comments on the blog)
Masklinn
on May 5, 2005
They've closed the DTD thing already, considering that "there is not much change between 1.0 strict and 1.1"...
When was the last time Microsoft got the teams of two different products to communicate with each other?
(BTW your security number thing is bugged in Firefox)