Presented by Jeff McWherter – Web Ascender

Formal CTPs and documentation @ www.asp.net

Cutting edge drops, roadmaps, etc @ www.codeplex.com/aspnet

VS10 supports multi-targeting, can support 3.5, 2.0

FX4.0 maintains a high compatibility bar with FX 3.5, they’re really trying to make it a much better experience than from 1.1 to 2.0

VS10 – no more WinForms, now WPF rendered interface improving UI performance

Out-of-band releases (MVC, Dynamic Data, etc) rolled up into FX 4.0

ASP.NET 4.0 Themes

• Support “pattern-based” models (MVC/TDD)
• Re-invest in the core by addressing top customer pain-points
• MVC
• Ajax
• Data and Dynamic Data

Web-Forms

• Client IDs –> manage control IDs that affect client-side development
• CSS –> remove the need to use CSS adapters, defer to CSS styles, bypass existing style properties, and get rid of the table based HTML rendering in ASP.NET controls
• URL routing for web-forms:
• Friendly URL handling for web forms
• Configuration model for URL routing (ie http://store.com/products/shoes vs http://store.com/products.aspx?category=10)
• Viewstate changes
• Disable on page, enable on specific controls
• Disable on parent control, enable on child controls
• Grid/ListViews work better without viewstate

Ajax

• jQuery including Intellisense
• Continue Ajax innovation: RIA
• Appeal to JavaScript developers
• Templates and data binding:
• Client-side handling, REST or Web services
• Covers page developer and component developer scenarios
• DOM manipulation, selectors…

ASP.NET MVC

• Appeals to those wanting separation of concerns, TDD, full control
• Ruby on Rails
• Django for Java
• Symphony for PHP
• Builds on from MVC 1.0
• MVC (Model, View, Controller)
• Enforces separation of concerns and provides full control of markup, TDD is enabled (and enforced)
• URL routing, tooling support
• Get the benefits of ASP.NET: profile, membership, roles, localization

ASP.NET Dynamic Data

• Scaffolding from Ruby on Rails
• Building on from FX3.5 SP1
• Dynamic-data and MVC:
• Scaffolding
• Templates
• Data Validation
• Support for many to many relationships
• Enhanced filtering
• Enhanced meta-data
• New field templates
• Email, URL, Enum, etc.

Back to the ‘core’

• Cache extensibility and performance enabling productions like Velocity to plugin as a cache provider
• Increased scalability
• Increased performance and scalability

Presenter – Kevin Kline (Quest Software)

What is Virtualization?

• Technology that allows a server to be decoupled from the physical hardware of the system.
• Lets you run one or more virtual machines independent of the physical hardware
• If you have VMWare Enterprise level products, you can receive support from Microsoft for a SQL instance on a VMWare VM.

Benefits of Virtualization

• Server Consolidation
• Disaster Recovery
• Legacy Apps
• Testing and QA
• Training

Drawbacks of Virtualization

• Overhead
• used to be 30-35% in original VMWare software
• now at 15% with newest software and processors
• Administration complexity
• VMs obfuscate troubleshooting efforts
• Performance monitoring and tuning
• Lag in hardware support

Strategies

• Planning for best Utilization
• How is it used?
• Type 1 (bare-metal) or Type 2 (hosted) Hypervisor
• Workload and performance?
• SLAs?
• Users?
• Availability and recovery?

Licensing Complexities

• Licensing
• Enterprise - $20K per physical cpu, unlimited instances in VMs
• Standard - $5K per license, each instance is a license

Virtualization Performance

• Where does overhead hit?
• Memory
• CPU
• Dick IO
• Driver Support
• How can I virtualize production SQL Server?
• It’s doable

Best Practices for Virtualization

• Choose a Hardware-assisted virtualizing CPU
• Confirm and enable HAT and DEP
• Use the right drivers with synthetic devices
• Set pass-thru disks on the guest VM to offline using DISKPART or Volume Manager
• To prevent overhead in the Disk IO
• Only run server role for hypervisor only from the root of the OS
• Don’t use dynamic VHDs
• Stick to the best performing options
• Dedicated pass-through disks
• Fixed-size VHDs (to improve Disk IO)
• Can be expanded, but VM must be shut down
• Don’t use regular PerfMon counters, especially for CPU
• Instead, use:
• Specific Logical Processor counters

Presenter – Brad Tutterow

Ruby is a programming language, Rails is a Web Framework built on top of it.

• So, what’s the big deal?
• #1, It’s FUN!
• #2, It’s EASY!
• Standard Setup
• Convention over Configuration
• #3, It’s PRODUCTIVE
• Why should I care?
• Broaden your horizons, become a generalist, rather than a specialist
• Expand your toolbox
• It will make you a better Developer
• What is Ruby?
• Object Oriented
• Dynamically Typed
• More flexible, but less structured
• Don’t see errors at compile time
• Somewhat requires Unit Testing to prevent runtime errors
• Duck Typing
• Comes from “if it walks like a duck, quacks like a duck…”
• The Ruby Language
• .each Method (similar to foreach)
• do –> end
• Everything is an object in Ruby
• next_week = 10.days.from.now
• unless statement
• unless today.is_saturday_or_sunday? <- ? returns a boolean
• if at the end
• puts “blah” if blah
• Strongly typed, but not statically typed
• No diacritic marks ({, ())
• The Rails Framework
• Free and open source web framework
• Does Web applications with a database back-end very well
• It’s a very specific framework
• Uses MVC Framework (Model, View, Controller
• Three Tenets
• Convention over Configuration
• Via scaffolding, can write boilerplate code to get all, get by id, build tables, etc.
• Don’t Repeat Yourself
• Each piece of knowledge should have one and only one place to live
• ActiveRecord
• An object should have the logic to put itself in the database and take itself back out of the database
• RadRails for aptana
• Netbeans IDE
• Create a Rails project in 3 steps
• rails project_name at command line
• Edit yaml file for database setup
• ruby script/server
• MVC
• request comes into controller
• controller looks at the model to pull what it needs
• it then pushes that to the view
• view provides the response
• controllers have actions (which are just methods)
• URL (controller/action/parameters)
• Controller code is written to get data from the model
• Models
• Create a new model at the command prompt (rails generate model modelname)
• Database migration scripts provide information about how to setup and teardown databases
• Free Methods
• find by id
• find by name
• find all
• sort
• Forms
• Scaffolding builds the forms for you

Great Book – RailsSpace (Michael Hartl)