IDE improvements in VS.NET Whidbey for ASP.NET Development - TLS341

Improved Project System

  • No need for FrontPage
  • Supports file system webs, allowing ASP.NET development even when IIS is not installed locally (Whidbey ships with its own lightweight Web server)
  • Build and debug without being an Admin
  • Directory-based project system (reduces contention for project files)
  • Makes it easy to do single-file editing, with complete IntelliSense support.
  • When you create a project, very few files or folders are created automatically. When the IDE needs to add something (such as a web.config to enable debugging), the user is provided with a notification before the file is added.
  • Debugger visualizers allow you to hover over an object at debug time and get an expanded view of the state of that object.

Remote Site Publishing

  • Support for UNC, FTP, SharePoint, IIS (IntelliSense works for all of these scenarios)
  • Publish all files or individual files, and keep local and remote sites in sync easily
  • Logging is built into the Remote Publishing Wizard

Source Editor Improvements

  • Intellisense Everywhere - in inline code and codebehind, in script blocks, in CSS styles, in web.config (yay!), and in XML files.
  • Added tools to navigate your code - view at a glance the hierarchy of tag relationships.
  • Outlining is available to allow you to expand or collapse on a tag-by-tag basis
  • Code formatting (which can be turned off completely...really completely) can be customized based on tag categories (server vs. client) and even on a per-tag basis, allowing you to format upper/lower case, self-closing or paired tags, line breaks, etc. Formatting options for the client also determine what the server controls render to the client, making it very easy to write XHTML-compliant code.
  • Cleaner code-behind. Based on partial classes, removes the requirement for separate control declarations in code-behind, and other "generated goop".
  • If you select text in Source view, then switch to Design view (or vice versa) your selection is preserved, so selecting an element in Design view makes it easy to locate the tags for that control.
  • Drag and drop is supported in Source view.
  • Formatting us supported at the page level, as well as at the selection level, and does not automatically introduce whitespace when formatting.
  • The formatter also supports automatic word-wrapping of tags.
  • Tag formatting can be customized based on whether the tag contains content or is a self-contained tag, in addition to the parameters discussed above.
  • The IDE supports exporting and importing of your desired formatting settings, so it's easy to share formatting across a development team to enforce a standardized format.
  • Everything built in the design surface is validated to XHTML 1.1, and can optionally be validated against various browsers, and even accessibility standards.
  • IntelliSense is now even supported in the @ Page directive, as well as in all inline code, including in <% %>blocks.

Whidbey Design Surface

  • Never, ever, EVER, modify your code (without your asking)
  • 100% XHTML 1.1 compliant and uses styles for formatting.
  • Master pages provide shared layout, and provides visual representation of both the master page, and the customized content
  • User Controls are rendered on the design surface
  • Added smart tags to expose common control tasks (databinding, autoformatting, etc.)
  • Improved table editor, with both pre-existing table templates, and/or editable table attributes.
  • Added visual feedback for resizing templates, including display of the changes in pixel measurements (or percent, depending on how you defined the table) as you resize.

Faster Web Development

  • No builds, save and refresh and see your changes.
  • Faster project open time.
  • Build Page feature - Allows you to locate compilation errors and validation problems on a page-by-page basis.
  • New Code directory that provides dynamic compilation and linking for class files, including Intellisense support.
  • Easier for teams to develop together since a compiler error on a single page doesn't prevent others from working on different pages.
  • Pre-compiler allows you to compile your entire application (including HTML and other tags) into a single assembly, which runs just like an app deployed with source code.

Seamless Upgrades

  • Allows you to upgrade a v1.1 application to Whidbey seamlessly.
  • You can choose in-place upgrade, or make a copy to modify to the new version.

IMPORTANT! Not all of these features are in the PDC bits...about 2/3rds are there, and the rest will be in the beta coming in the spring.

8 Comments

  • Great summary! :-)

  • Damn, ScottGu stole my comment. But I clicked here so I am going to say the same thing :) Great Summary.



    -Scott

  • Succinct reporting... thanks...:-)

  • Any intellisense improvements like C# enumerations (ala the way VB does it)



    or switch/select statements against a enum will build out the entire statement?

  • I'm going to fall over and die if I have to wait tell spring for all of this. Just keep putting more &quot;cookies&quot; in the &quot;cookie jar&quot; that I can't quite reach.

  • Scott,



    What I'm reporting here are not just announcements...this talk in particular demonstrated all of the features that I reported, in working code. Some of the features may not be in the build of Whidbey that was given out to attendees, but they all will be in the beta in the spring, and I've seen them in action, both in this session, and up close.



    So no vaporware here...it's all working code. :-)

  • Scott,



    There's probably nothing I could say to convince you, but the likelihood at this point of these *working* features being pulled from the product is slim. Once the beta has been released, it will be even slimmer. That doesn't mean it's a guarantee, but the builds that the ASP.NET team is showing off are not some forked-off &quot;demo&quot; code. They are what the product is going to be. Sorry if you're skeptical about that, but I guess we can just wait to see whether your skepticism is justified.

  • I assure you Scott, that none of the stuff talked about here was 'demoware.' We did not bake the bits to make it look good. I recognize what your talking about and I'm not going to say that we never do that, but for my talk -- we went in, grabbed a build out of the tree -- made no special tweaks and demo'd all this really great stuff. Just hang tight until we release the beta -- I know you will be pleasantly surprised.

Comments have been disabled for this content.