Got Twittering ? check out our new bTwitter application…
On est enfin public…. Wahooowww….
from Scott Guthrie’s blog One of the big features that web developers will quickly discover with VS 2008 is its dramatically improved HTML designer, and the rich CSS support it brings.
VS 2008 now uses the same web designer that ships with Microsoft’s new Expression Web product. In addition to providing lots of new functionality, you’ll also find that this web designer is much faster than the VS 2005 version (which was based on a much older code base).
Below is a quick tour of some of the new web designer features that you’ll be able to take advantage of with both VS 2008 as well as the free Visual Web Developer 2008 Express:
Split View Editing
In addition to supporting both source-view and design-view, VS 2008 adds support for a new “split-view” mode when working on pages. This allows you to see both the HTML source and the Design View at the same-time, and easily have any changes you make in one view be updated in the other:
CSS Style Manager
VS 2008 supports a new tool window inside the IDE called “Manage Styles”. This shows all of the CSS stylesheets, and their corresponding rules, for the page you are currently editing. It can be used both when you are in design-view, as well as when you are in source view on a page:
A circle around a CSS rule in the manage styles window indicates that particular rule is in use within the current document. Using the mouse to hover over the rule allows you to quickly see the CSS rule values:
You can then either right-click on a CSS rule and select “Modify Style” to bring up a graphical CSS rules editor, or you can double click on the rule in the manage styles window to automatically open the stylesheet file and jump immediately to the CSS source definition to edit (with full intellisense):
For even more tips/tricks about how to best use the “Manage Styles” tool window please read this blog post.
CSS Properties Window
One of the other cool new CSS features that is also supported in both design and source view is the new CSS Properties Window:
When you select an HTML element or ASP.NET server control, the CSS property window will show you all of the CSS settings currently applied to it. You can also change any of the values using the CSS property grid. The “target rule” drop-down in the style toolbar allows you to determine under what rule the settings are applied (read this blog post to learn more about the style toolbar and target rule dropdown).
If, like me, you sometimes struggle with large CSS stylesheets and find yourself shouting “why the $!#@ is it looking like that?”, you’ll find the “summary” view of the CSS Properties window really useful (just click the summary button at the top of the CSS properties pane). When you press this button it enables a filtering mode that shows you the full inheritance set of CSS rules for the current HTML element or ASP.NET control you are working with:
In the properties grid above you’ll notice that some values are duplicated multiple times – with red arrows striking out previous values. This indicates that a parent CSS rule setting is being overridden by another CSS rule’s value. You can see both the original value as well as the overridden one in the summary view at the bottom.
You can click on the individual values to see where in the CSS precedence hierarchy this value was inherited from or overridden. In the example below you can see that the final color for the current element that my cursor is on is a dark brown color. If I select this final color value, the CSS properties window will draw a blue box in the applied-rules list above indicating that this setting is set in the “singlecontent h3” rule:
If I click on the lighter brown color setting that this rule overrode (and which has the red strike-thru), you can see that it originated with the page’s HTML body CSS rule (notice how the body rule below is selected in the applied rules list when I select the overridden value below):
Please read this dedicated CSS Properties Window blog post to learn even more how to use the CSS property window.
CSS Source View Intellisense
The HTML designer supports the ability to select an element or control in design-view, and graphically select a rule from the CSS list to apply to it.
You’ll also find when in source mode that you now have intellisense support for specifying CSS class rules:
This is true for both HTML element (like above), as well as with ASP.NET server controls:
This CSS intellisense is supported in both regular HTML / ASP.NET pages, as well as when working with pages based on master pages and nested master pages.
Nested Master Page Support
Earlier this month I wrote a dedicated blog post that covered the new VS 2008 Nested Master Page Support. All of the above designer and CSS features obviously work with that as well:
The above post provides a quick look at some of the new HTML designer and CSS tool support in VS 2008 (all of the above features also ship with the free Visual Web Developer 2008 Express edition).
Because VS 2008 now has multi-targeting support you’ll be able to use these feature immediately without having to install .NET 3.5 on your servers. You can open existing ASP.NET 2.0 projects in VS 2008, have VS 2008 continue to target .NET 2.0 as the runtime target, and begin using these features immediately.
Over the next week I’ll also be starting a new multi-part blog series that covers the new <asp:listview> control that ships as part of ASP.NET in .NET 3.5. One of the big benefits of the <asp:listview> is that it enables developers to have total control over the HTML output emitted in data scenarios. This works well with all of the new CSS tool features above, and enables you to more easily create great looking web sites and applications.
from Scott Guthrie’s blog
Recently I was looking over the shoulder of someone writing some code, and saw them using some other new text editing features that I hadn’t seen before (“wait – how did you just do that?”).
Below is a non-exhaustive list of a few new code editing improvements I’ve learned about this week. I’m know there are many more I don’t know about yet – but I thought these few were worth sharing now:
Transparent Intellisense Mode
One of the things I sometimes find annoying with intellisense in VS 2005 is that the intellisense drop-down obscures the code that is behind it when it pops-up:
With VS 2005 I often find myself needing to escape out of intellisense in order to better see the code around where I’m working, and then go back and complete what I was doing. This sometimes ends up disturbing my train of thought and typing workflow.
VS 2008 provides a nice new feature that allows you to quickly make the intellisense drop-down list semi-transparent. Just hold down the “Ctrl” key while the intellisense drop-down is visible and you’ll be able to switch it into a semi-transparent mode that enables you to quickly look at the code underneath without having to escape out of intellisense:
When you release the “Ctrl” key, the editor will switch back to the normal intellisense view and you can continue typing where you were in the Intellisense window.
VB Intellisense Filtering
The VB team has made some nice improvements to intellisense that make it much easier to navigate through APIs.
Intellisense completion now automatically filters the member list available as you type to help you better pinpoint the API you are looking for. For example, if in an ASP.NET code-behind page you type “R” it will show the full list of types and members available (with the selection starting in the “R” list):
When you type the second character of what you are looking for (in this case “e”), VB will automatically filter to only show those types that start with “Re” and highlight the most likely option:
When you type the “s” it filters the list even further:
When you type “p” it filters down to just the one option available:
I find this cleaner and more intuitive than the previous model that always showed everything in the drop-down.
VB LINQ Intellisense
I’ve done several posts in the past about LINQ and LINQ to SQL. Both VB and C# obviously have full support for LINQ and LINQ to SQL. I think the VB team in particular has done some nice work to provide nice intellisense hints to help guide users when writing LINQ statements in the editor.
For example, assuming we have a LINQ to SQL data model like the one I built in Part 2 of my LINQ to SQL series, I could use the VB code editor to easily work with it. Notice below how VB automatically provides a tooltip that helps guide me through writing the LINQ query syntax:
I can then start writing my query expression and the VB intellisense will guide me through creating it:
The above expression retrieves three column values from the database and creates a new anonymous type that I can then loop over to retrieve and work on the data:
Organize C# Using Statements
The C# editor has added some great intellisense improvements as well. Some of the biggest obviously include language intellisense and refactoring support for the new language features (Lambdas, Extension Methods, Query Syntax, Anonymous Types, etc). Just like in our VB example above, C# supports type inference and intellisense completion of anonymous types:
One of the small, but nice, new features I recently noticed in VS 2008 is support for better organizing using statements in C#. You can now select a list of using statements, right-click, and then pull up the “Organize Usings” sub-menu:
You can use this to alphabetically sort your namespaces (one of my pet peeves), and optionally use the ‘Remove Unused Usings” command to remove un-necessary namespace declarations from the file:
When you use this command the editor will analyze what types you are using in your code file, and automatically remove those namespaces that are declared but not needed to support them. A small but handy little feature.