IDE improvments in Whidbey

G. Andrew Duthie  list a lot of impressive and awaited improvements in Whidbey IDE.

That sounds fab, but why in such a long list, some stuff has not been already implemented in VS 2003 ?

I know it's sounds like a dumb question, but why we have to wait for a beta next spring apparently and a final release surely end of 2004 to see some obvious important features done and dusted in our current tool ?

I know that MS learned a lot from their mistakes, but how it's not possible from now to have Intellisense working already in Web page @Page directive etc...?

After all Microsoft created Intellisense, so why they didn't think that it should be useful for more than some code behind?

And this is only one item, because if I look at Andrew post, I can find a lot of absurd nonsense, and the list is long like the drag and drop from the source, the formatting idiocracy, etc...

So my wish would be to have a service pack to VS.Net from Now to implement not some new features but maybe some must-be-there things.

 

2 Comments

  • They have to have something to sale. Just wait til you see the list of what's not in Whidbey that should be which will make it easy to sell Orcas. :)

  • Item #1 for Orcas might likely be Longhorn native support. Seems Whidbey will be touted as .NET - therefore able to work ON Longhorn - but only Orcas is touted as able to work WITH Longhorn.

Comments have been disabled for this content.