scottgu

The Silverlight.js file is optional, but something we recommend adding to a page that hosts Silverlight.  It includes automatic support to detect when Silverlight is installed for the first time, and handles automatically refreshing the HTML page and loading the content.  You don't need to write any custom code to integrate these feaures - just adding the silverlight.js file to the page will do it.

Hope this helps,

Scott

Hi Irascian,

The WCAG and 508 guidelines don't say much about using 'strong' in place of 'b'.  We are looking into it more, though, to see if there is a formal recommendation.  I believe JAWS (the most popular screen reader out there) fully supports both. 

The "summary" attribute for a table is actually a pri3 WCAG requirement.  You can add it with both ASP.NET 1.1 and ASP.NET 2.0 by setting a "summary" attribute on the 'asp: datagrid' or 'asp: gridview' controls.  This will then be passed through to the output as an expando property.

Radiobuttons and checkboxes inside a datagrid now output a 'for' attribute which associates them with the corresponding label element -- so this should no longer be a problem with ASP.NET V2.0.  I have a code workaround that I can send you for ASP.NET V1.1 that shows how to-do that today (unfortunately this doesn't work built-in).

Hope this helps,

Scott

Hi MGrassman,

We don't officially support classic ASP with VS 2005, although I was just playing around with it and you'll probably find that you get an ok experience.

Specifically, because there is no longer a project file for web-projects, you don't have to worry about adding it to "a project" in order for the files to show up.  Instead just copy a .asp file into you site directory and you are good to go. 

There is still some intellisense support for classic ASP in the text editor.  I noticed that objects like request, response, etc do have code statement completion. You also get full support for HTML statement completion, xhtml validation, tag navigator, etc support for classic ASP contnet.

Hope this helps.  I'd recommend downloading the Visual Web Developer express edition when the beta comes out and giving it a try to see if this meets your classic asp needs.

Thanks,

Scott

Hi Rasx,

You can actually export and import all settings within VS 2005 to XML files.  This makes it easy to copy them from machine to machine, as well as use them in group developer scenarios. 

Just go to the Tools->Import and Export Settings menu item and a wizard will walk you through it.

Hope this helps,

Scott

Hi DotNetjunkie,

We changed the default from loading the page in the designer to the source editor because we've seen a number of developers say that prefer source mode over a design surface.

The good news is that you can configure the behavior anyway you want -- just go to the preferences dialog box if you prefer design-mode when opening files.  We'll then honor it anytime you open one.

Hope this helps,

Scott

We support intellisense on XML files that have either an XSD or DTD schema.  So for pure XML intellisense we work with either.

For HTML intellisense we have a standard schema that people can use to implement the intellisense rules.  I think it is XSD based (although need to double-check) to make it extensible and allow you to add your own new html formats to the list.

We do provide built-in validation/intellisense support for XHTML strict as well as for transitional.

Hope this helps,

Scott

Actually you'll find there are a lot more feature than Apache, and several scenarios that are not possible today with Apache.  A few specific web-server benefits that IIS7 will have over Apache 2.x:

1) Richer process isolation management and control
2) Richer command-line scripting and admin model
3) Rich admin tool (Apache has none)
4) Richer real-time diagnostics and tracing support
5) Multi-protocol activation (to enable web-service scenarios like queing)
6) Better performance

ASP.NET obviously provides some benefits as well -- the list above just compares the web-server pieces.

Hope this helps,

Scott

Hi Doug,

Our plan is to enable IIS7 to work on the client and server.  We are also looking to change some of the limitations previous versions have had on client-platforms to make it a more full-featured offering.

Hope this helps,

Scott