help.net
<font size="2"><br />Musing on .Net</font>
-
Strong and interesting comment :-)
Comment posted on the Feedback Center.
Now choose your camp, the discussion is opened :-) -
The vote continue...
Obviously if Microsoft open a Feedback Center they must expect some strong comments on their new tools like Visual Studio 2005.
Even if we are far to reach the 6 million developers using VS and .Net Microsoft claims to have, the list of disappointed developers grow up.
I think it's really time Microsoft show some respect to everybody and give an answer to all the comments I can see at the bottom of this page.
I know for sure you can't ignore 154 developers, becuase I believe they represent just the top of the iceberg.
Scott with a ll the respect I have for you and the fantastic job you do with your team, we need to know more than just some details on web projects. Some of the comments are quite interesting, liek the release of .Net 2.0 at the due date, but without the final IDE. Is it possible to use .Net 2.0 with VS 2003? Interesting question. -
Official name and logo for Internet Explorer 7
IE Team blog on the official name and logo for IE 7
I like the yellow orbit. -
The Island - Cool Microsoft sponsorship
Went to see the Island tonight. Not the greatest movie in the universe, but what amazed me was the omni presence of Microsoft everywhere.
-
Scott Guthrie and the 5 concerns
No I am not going to review every line of Scott reply to the community about the issues with Visual Studio 2005.
The post is dense, and contains some interesting and promising answers. However my own two cents on that.
First, Scott admit that Beta 2 was frozen way back in February and today the latest releases (CTP internal builds) have a lot of new stuff and bugs fixed.
Then my main question remain valid: who can really validate outside Microsoft that the new releases are good enough for a final release? Why Microsoft didn’t release another Beta between February and today, exception of the CTP which are not generally used?
Scott list 5 main issues and address each of them, but if you look at the feedback center, be sure to find much more problems. The list is worryingly long.
And one thing I would like to see Scott reading is a statement or a roadmap if you prefer about the evolution of Visual Studio 2005. What are the chances to see an SP1, SP2 for the IDE and when?
Scott I agree that we are all happy with .Net 2.0. But not with the new Visual Studio.
You asked me also my feedback on my last migration tests. I will post something about that later, but at the moment it’s not really conclusive. -
Roadmap
Jerry sorry but I have to disagree with your comment. Microsoft are making changes to their codebase right now. Two examples: the assemblies they modified for the migration tool, and some other small features they want to add to the final product.
Plus the new fashion they have to add patches, sorry in Microsoft language it's called a workaround.
No the Beta 2 was supposed to be close to the RTM and it's not. Top that with all the different CTP and internal builts and yes you have matter for another Beta.
OK I am realistic this won't happen. But at least it could be nice to have a roadmap on the different next steps.
What will happen after the 7th of November? We are not in the same situation than .Net 1.0 where everything was new.
Now we're talking here about an existing base of thousand of projects, applications, components, etc... all built on the promise of a continuity. -
Thanks for your vote and continue
Great, developers seems to react positively. At the moment 72 votes.
-
We want a better Visual Studio 2005 - Developers it's time to vote
Call to Developers, Developers, Developers:
It seems that an official petition (I still don't like the word but what else can I use) for a VS 2005 Beta 3 exist. -
Videos available
OK finally find the time to rip the two last videos from Roy Osherove lecture held in Dublin last Friday.
-
Give back our Exclude feature :-)
OK I know the Exclude from project feature will be back in the final VS 2005 release, but I write this post because most of the issues I got with the Migration tool recently are caused by the number of small files I want to keep in my VS 2003 project.