-
You will be able to drag a SQL Server table and drop it into a page, which will give you a data binded datagrid, mostly through property manipulation, the grid will be sortable, editable and updatable
-
One goal of ASP.NET 2.0 is to reduce the amount of code needed by 70-75%, Scott thinks Whidbey will get very close to that mark
-
Another goal is to simplify administration, ASP.NET 2.0 will offer a rich configuration API along with rich admin tools, in the bottom you will still have good old XML config files
-
We will get Intellisense in config files and in code embedded in web forms (as opposed to code-behind classes)
-
We will get some 40 new controls, including things like a rich treeview and security controls (authentication). Controls will work with both two-tier and three-tier data models.
-
We will have building blocks APIs services, like for example: membership services, role management and a personalization system
-
This APIs will use a provider model, so that you can create, for example, your own credentials provider and replace the one that's used out of the box by the authentication block (SQL Server tables, it seems)
-
The template columns design-time editor will get a major update, including two-way databinding and custom controls that can be dragged and dropped into the column (for example, drop-downs)
-
ASP.NET 2.0 will be 64-bit enabled
-
In particular, IIS 6.0 will allow two use the ASP.NET authentication information to control access to classic ASP pages and even other resources like images or JSP pages
-
An administrator could be notified by e-mail every time a certain exception raises
-
Nothing to do with ASP.NET 2.0: in a few weeks a utility to convert classic ASP pages to ASP.NET will be available at
www.asp.net
-
Enterprise Services will allow you to start/stop a transaction at any fixed point in your code, you will not be constrained to object boundaries
-
There will be a data access layer designer which will allow you to choose tables, views, add properties and then access all this elements in a strongly-typed way
-
Alternatively, you will be able to use Object Spaces, which is an object-relational mapping tool that will be released as part of Whidbey
-
Yukon and Whidbey have the same release timeframe
-
To create Yukon user-defined types you will be able to use any CLR value class (C# struct)
-
The Cache object will be enhanced so that you can, for example, make a dataset valid as long as the underlaying source (a table, usually) doesn't change.