Media tagged with asp.net - Channel 9

Announcing Microsoft Ajax Library Preview 6

James Senior — Fri, 16 Oct 2009 10:47:00 GMT

I sat down with Stephen Walther from the Microsoft Ajax team to talk about their new release - Preview 6 - of the Microsoft Ajax Library.

Stephen walks us through the three big enhancements in this release:

- Addition of the imperative syntax
- The Script Loader
- jQuery support enhancements

We go on to talk about how this will be the last release before we launch the Microsoft Ajax Library before the upcoming Microsoft PDC conference in November and also mention the new Microsoft Ajax CDN where we now have hosted the Microsoft Ajax Library and jQuery.

To download the latest preview and get more information on the Microsoft Ajax Library head over to http://www.asp.net/ajax and also be sure to check out these related blog posts from the rest of the Microsoft Ajax team:

Scott Guthrie has the big announcement
James Senior has details on the Script Loader
Bertrand Le Roy has a blog post on imperative templates

Web Application Toolkit: Template-Driven Emails

Jonathan Carter — Thu, 24 Sep 2009 18:03:00 GMT

This Web Application Toolkit is designed to demonstrate how to generate and send dynamic, template-based emails from a web application. There are many common scenarios where notification emails need to be sent to end users. Examples of these common scenarios may involve notifying a user of their newly created account, sending a new password in respond to a forgotten password request, or emailing an alert under specific business circumstances, such as the creation of a order. Typically the E-mails sent from a Web application scenario are formatted as HTML, include CSS stylesheets, and images and need to be generated dynamically with custom or user-specific data.

This Web Application Toolkit provides a reusable component named TemplateDrivenEmail that can be used to easily generate and send dynamic, HTML-formatted emails based on templates that you can easily create and customize. The TemplateDrivenEmail component is a .NET Class Library that can easily be included in your solution and used with an ASP.NET Web Application, a background application such as a Windows Service, or any other type of .NET application. The email templates are based on a standard XML technology know as Extensible Stylesheet Language. This Web Application Toolkit also includes an example that shows how to use the TemplateDrivenEmail component.

Download this toolkit here.

For screencasts about other Web Application Toolkits, click here.

To download other Web Application Toolkits, click here.

ToolShed Tooltip #22 - Channel9 and the Tool Shed ... A Treasure Chest of Resources

Russell Fustino — Mon, 24 Aug 2009 22:49:00 GMT

This Tool Shed Tooltip is about a very valuable resource for all developers... Channel9. Do you know there are other Microsoft communities linked to Channel9 for ASP.NET, Silverlight, IIS, Mix, TechNet Edge and more? Do you know... not every video posted to the channel9 site makes it to the home page? How do you find all of the videos? Do you know you can download a video in many different formats from Zune to High Def for offline viewing? Do you know about the upcoming enhancements to Channel 9? Do you know you can rate videos and provide much wanted feedback? Did you know there is a channel9 toolshed site with links to all of the resources covered in the TV Shows as well as a toolshed code site? Watch this video to learn answers to these questions and many other tips and tricks to optimize your resource experience.

This clip was originally filmed as part of Episode 4 of It's All About The Tools, but it is not included in the final version. So, this is never seen before footage! This was presented in front of a live audience. And even though it was a roomful of Niners... each person I talked to after the event, still walked away learning something. Hopefully you will too!

The show is hosted by Russ Fustino and Co-Host Stan Schultes. Download code, ppt and demo script from http://code.msdn.com/toolshed for all episodes. Also, use the links on http://channel9.msdn.com/toolshed to download tools. Finally, check out some more great videos on the Developer Evangelist East site: http://channel9.msdn.com/dpeeast

Hanselminutes on 9 - ASP.NET MVC 2 Preview 1 with Phil Haack and Virtual Scott

Glucose — Fri, 31 Jul 2009 06:15:00 GMT

Scott's in Redmond (or IS he?) and talking to Phil Haack about the release of ASP.NET MVC 2 Preview 1. Phil give us a tour of some of the new features in this high-tech and inappropriate use of technology. A video of a Phil's screen? Hasn't Scott or Phil heard of a screencast? Still, enjoy. :)
You can download ASP.NET MVC 2 Preview 1 if you like, too.

Jan Welker über dotnet-kicks.de

Dariusz Parys — Mon, 27 Jul 2009 15:43:00 GMT

Auf dem .NET Open Space Süd hatte ich die Gelegenheit mit Jan Welker über das Projekt dotnet-kicks.de zu sprechen. Jan erzählt was letztendlich mit dieser Seite gemacht werden kann und wie es dazu kam das er zusammen mit Gordon und Klaus diese Seite aufgebaut hat.

Viel Spaß beim reinschauen,
Dariusz

Scott Guthrie at Vista Squad on ASP.NET MVC Part 2

Mike Ormond — Thu, 09 Jul 2009 17:16:00 GMT

On 3rd July 2009, ScottGu happened to be in London and couldn't resist an invitation to do a special ASP.NET MVC session for the Vista Squad user group at the Microsoft offices in Reading.

Part 1 of this video can be found here.

Scott Guthrie at Vista Squad on ASP.NET MVC Part 1

Mike Ormond — Thu, 09 Jul 2009 13:39:00 GMT

Fastest To Market: RAD Web Applications with ASP.NET Dynamic Data and Entity Framework

Matthijs Hoekstra — Sat, 20 Jun 2009 09:20:00 GMT

For some applications, time to market is simply critical. If your application is heavily-data driven and backed by a well-designed database schema, you could help yourself a lot be looking at the dynamic duo of ASP.NET Dynamic Data and the ADO.NET Entity Framework. Together, these two technologies allow you to build data driven websites ... quicker than anytime before. In this session, Ingo Rammer will show you how to combine the flexibility of ASP.NET with these new features for quickly building data-driven web sites. (And yes, it even allows you to simply embed a few RAD pages in your big, existing ASP.NET application).

This video is recorded at the Dutch DevDays in Den Haag The Netherlands in June 2009. DevDays is the largest industry event for developers in the Netherlands. Thousands of professional developers visit DevDays yearly to keep in touch with the latest developments in their field.

Dynamics Duo: Wide World Importers Code

Ben Riga — Wed, 17 Jun 2009 04:00:00 GMT

In this episode we dive into some of the real code behind Wide World Importers Conference site. Girish walks us through the code-behind for the contact/profile and conference registration options pages.

There’s not really a lot of magic here. In fact, I would say it’s quite simple to understand. If you’ve used ASP.NET before it’s not much different when you’re writing for Windows Azure as we are here.

The only difference is that here we’re sending the data to Dynamics CRM using the SDK. That’s infinitely more useful for your customers as the information becomes actionable immediately. We should mention that, in this case, we’re using a 3rd party toolkit by Microsoft Gold Partner, ADXSTUDIO. Shan McArthur and his team at ADXSTUDIO helped us to put this site together and their toolkit naturally uses the CRM SDK. It abstracts the SDK it out a little more to make writing and reading the code even simpler.

We use the Live ID token that we’re getting from the Live ID service, as we discussed in the previous episode, to allow the user to retrieve and update their profile information. It’s the unique key, of sorts, to their record in the CRM data store.

Girish promised in this episode to publish the code so expect to see that soon on his blog. We’ll have to hold him to that. :)

This episode is part of a 5-part series. In this series we’ve tried to explain how you can combine the Microsoft Web Platform with Dynamics CRM to quickly build and deploy self-service solutions. The full set of videos include:

Both Girish and I enjoyed recording this series. We hope you enjoyed them as well. If you have comments or suggestions for other topics, feel free to add comments below or email Girish or me (Ben) directly.

Phil Haack - ASP.NET, MVC, and Ninjas On Fire

Robert Hess — Tue, 09 Jun 2009 19:28:00 GMT

Phil Haack had a session at MIX09 who's name caught my eye: "ASP.NET MVC Ninjas on Fire Black Belt Tips", which I suppose was part of the intent.

I asked Phil to drop by and share with us some of the details about what MVC is, how it can help you develop websites.

After watching this brief glimpse (sans ninjas) you might want to check out his full session from MIX09:

ASP.NET MVC Ninjas on Fire Black Belt Tips

And for even more details you can also check out:

10-4 Episode 22: Simplifying Data-Driven Web Applications

Jonathan Carter — Sat, 06 Jun 2009 18:24:00 GMT

In this episode of 10-4, we discuss how the development of data-driven web applications has evolved in ASP.NET and how in the .NET Framework 4 it becomes even easier. Whether you're working on a new or existing application, getting your UI to light up model-level metadata/validation becomes as simple as a single line of code.

For more 10-4 episodes, be sure to visit:
http://channel9.msdn.com/shows/10-4

Visual Studio Topic Area on Channel 9:
http://channel9.msdn.com/VisualStudio

Visual Studio 2010 CTP VPC:
http://tinyurl.com/GetCTP

10-4! Over and out!

Extreme ASP.NET Makeover: Getting Your House in Order - Cmd Line Build

Howard Dierking — Fri, 05 Jun 2009 06:57:00 GMT

Let me give you a very brief introduction to MSBuild. In MSBuild terminology, build steps are called "targets." We will define three common targets initially: Clean, Init, and Compile. You can create other targets to automate other common tasks such as running tests, creating installer packages, deploying to a staging server, or generating documentation. MSBuild uses tasks to define operations within a target. There are many default tasks, such as RemoveDir, MakeDir, MSBuild, and Exec, among others. MSBuild also has the notions of items and properties. Items are files, directories, and references. Properties are name-value pairs representing configuration (Debug/Release), architecture (x86/x64/ia64/AnyCPU), or anything else.

Let's start by defining the Clean target, as shown in the following code:

<ItemGroup>

      <BuildArtifacts Include=".\buildartifacts\"/>

</ItemGroup>

<Target Name="Clean">

      <RemoveDir Directories="@(BuildArtifacts)"/>

</Target>

We use the RemoveDir/ task to remove the $\build\buildartifacts\ directory. Nothing surprising here.

Next we want to initialize our build environment, which means recreating the $\build\buildartifacts\ directory:

<Target Name="Init" DependsOnTargets="Clean">

      <MakeDir Directories="@(BuildArtifacts)"/>

</Target>

Note that the Init target depends on the Clean target so the $\build\buildartifacts\ directory will be removed and recreated if it already exists. This ensures a clean build.

Moving onto the Compile task itself, I don't want to re-specify the project references, C# files, and configuration options that are already present in the project file. (Some developers do like to have this level of control with their builds and use the project files solely for organizing files within Visual Studio.) I will simply use the MSBuild/ task to compile the solution (which will compile the associated project files) defined by ScrewTurnWiki.sln. I override OutDir to place the build output in $\build\buildartifacts\ rather than in various <Project>\bin\Debug directories. I pass through the build configuration (Debug or Release) and set it to Debug if it is left unspecified, as shown in Figure 7. You can override additional options, such as CPU architecture, in a similar manner:

Compile Using MSBuild

<PropertyGroup>

      <Configuration Condition=" '$(Configuration)' == " ">Debug</Configuration>

</PropertyGroup>

<ItemGroup>

      <BuildArtifacts Include=".\buildartifacts\"/>

      <SolutionFile Include="..\ScrewTurnWiki.sln"/>

</ItemGroup>

<Target Name="Compile" DependsOnTargets="Init">

      <MSBuild Projects="@(SolutionFile)"Properties=

      "OutDir=%(BuildArtifacts.FullPath);Configuration=$(Configuration)"/>

</Target>

Full Build Script

      
<?xml version="1.0" encoding="utf-8"?/>

      <Project ToolsVersion="3.5" DefaultTargets="Compile"

             xmlns="http://schemas.microsoft.com/developer/msbuild/2003">

            <PropertyGroup>

                  <Configuration Condition=" '$(Configuration)' == " ">Debug</Configuration>

            </PropertyGroup>

            <ItemGroup>

                  <SolutionRoot Include=".."/>

                  <BuildArtifacts Include=".\buildartifacts\"/>

                  <SolutionFile Include="..\ScrewTurnWiki.sln"/>

            </ItemGroup>

            <Target Name="Clean">

                 <RemoveDir Directories="@(BuildArtifacts)"/>

            </Target>

            <Target Name="Init" DependsOnTargets="Clean">

                 <MakeDir Directories="@(BuildArtifacts)"/>

            </Target>

            <Target Name="Compile" DependsOnTargets="Init">

                 <MSBuild Projects="@(SolutionFile)" 

                 Properties="OutDir=%(BuildArtifacts.FullPath);Configuration=$(Configuration)"/>

            </Target>

      </Project>

Notice the Project DefaultTargets="Compile"/, which specifies that the Compile target should be run if none is specified. You can have msbuild run a specific target using the /t switch. For example, to only run the Clean target:

msbuild build/ScrewTurnWiki.build /t:Clean

For more information on creating MSBuild scripts, I encourage you to read Sayed Ibrahim Hashimi's Best Practices For Creating Reliable Builds Part 1 and Part 2. I would also like to extend my thanks to Sayed for his assistance in troubleshooting a MSBuild issue that I encountered while writing this article.

Conclusion

This article is just the beginning of our journey as we set out to improve ScrewTurn Wiki. It is never too late to implement good development practices on an existing codebase, such as version control, issue tracking, automated self-contained build scripts, and automated testing. These practices provide your team with a safety net that allows you to more confidently make changes to improve an existing codebase. The next article will focus on automated testing, including acceptance testing with WatiN, a Web testing framework, and unit/integration testing with NUnit.

Read the full article at http://msdn.microsoft.com/en-us/magazine/dd758790.aspx

Extreme ASP.NET Makeover: Getting Your House in Order - Inspecting a Proj File

Howard Dierking — Fri, 05 Jun 2009 06:56:00 GMT

Creating an Automated Build Script

In creating a build script, we want to automate common tasks for building the project source code as much as possible. Whether you know it or not, you are already using build scripts. When you create a new project, Visual Studio creates a build script for that project in the form of a .csproj or .vbproj file. (MSBuild was introduced with .NET Framework 2.0, so project files created by Visual Studio 2005 and above use the new MSBuild format under the covers.) If you open a project file in a text editor such as Notepad rather than Visual Studio, you will see something like this clip.

To run a build from the command line, simply launch a Visual Studio 2008 Command Prompt, navigate to the solution root, and execute:

msbuild ScrewTurnWiki.sln

Running the Visual Studio 2008 Command Prompt instead of the standard command prompt ensures that the Visual Studio and the .NET Framework directories are added to the PATH environment variable, enabling you to execute commands like msbuild.exe without specifying the full path to the executable. In addition to compiling the entire solution, you can compile individual projects.

msbuild src\app\Core\Core.csproj

Rather than editing the project files directly, I will create a separate build file for building the solution from the command line. If you are creating a custom build file, the two most commonly used build engines on the .NET platform are MSBuild and NAnt. (Other options include rake, Bake, and psake, among others.) I will use MSBuild since it is installed by default with .NET Framework 2.0 and above.

Read the full article at http://msdn.microsoft.com/en-us/magazine/dd758790.aspx

Extreme ASP.NET Makeover: Getting Your House in Order - Source Control

Howard Dierking — Fri, 05 Jun 2009 06:56:00 GMT

Version Control

All software development projects should use a version control system (VCS) for tracking and coordinating changes to code files and other project artifacts. The size of the project team doesn't matter as even a single developer benefits from using version control. If you are still using ZIP files to track changes to your source, you should reconsider.

A VCS helps a team coordinate changes to source code and other artifacts during development. If a developer tries to commit changes without updating to the latest version in the repository, the VCS will require the developer to update before committing. This will give the developer a chance to resolve any conflicts that may be present. The VCS also prevents one developer from accidentally overwriting the changes made by another developer.

A VCS also acts as a safety net for developers. If a developer makes a change that breaks the application, the change can easily be reverted by rolling back to a build with the latest known good state in the repository. Even if the change has been committed to the repository, it is possible to revert the change. Modern version control systems support branching, merging, and diffing. (For definitions of these and other terms, please take a look at our Glossary.) They can answer questions such as who last changed this code, what changes were made, and which other files were modified at the same time. They prevent developers from accidentally overwriting other changes either via edit/merge or a pessimistic locking (also known as checkout) mechanism. Although it sounds dangerous at first glance, edit/merge causes less friction on a development team and works better in practice than pessimistic locking. In most cases, merges happen automatically because developers are working on different parts of a code file. If developers happen to be working on the same part of the codebase, they should probably be coordinating their efforts somewhere other than the VCS.

There are many modern version control systems available today. For open source projects, the most popular—and free—choice is Subversion (SVN) and it is supported by most open source project host sites, such as SourceForge, Google Code, and CodePlex. (CodePlex actually uses Microsoft Team Foundation Server for source control, but hosts SvnBridge, which allows Subversion clients to talk to Team Foundation Server.) In corporate environments, teams often install these same version control systems, such as Subversion (SVN) or Team Foundation Server , behind the firewall.

The ScrewTurn Wiki project manages its source code using Subversion. If you want to get started with Subversion, I would recommend downloading TortoiseSVN (http://tortoisesvn.net), which is a Windows Explorer Shell Extension and provides context menus for source control operations. TortoiseSVN will also optionally install the command line tools, which allow you to use Subversion from cmd.exe or PowerShell. Let's take a quick tour of Subversion and TortoiseSVN ( see Figures 2 and 3):

Figure 2 TortoiseSVN File Manager View Showing Overlay Icons

You will notice the icon overlays in Figure 2, which is TortoiseSVN indicating the current status of a file/directory. (Green check = no pending changes; red exclamation = pending changes; question mark = not versioned; grey dash = ignored file) If you right click on a file/directory, as shown in Figure 3, you can see the TortoiseSVN context menu appear.

Figure 3 Context Menus for Source Control Operations

Glossary

branch: A temporary development line in a VCS repository. Often used while creating a patch, stabilizing a release (while development on the trunk continues), or experimenting with a new (and disruptive) feature.

changeset: Combined set of changes that should be atomically committed to a repository.

commit: Send a changeset to the VCS repository.

diff: Changes made to a file.

merge: Integrating multiple changes into a working copy. The changes can be from a different developer working on the trunk or from another branch.

patch: Changeset expressed as a single file that can be electronically sent to another developer.

tag: An important milestone in a VCS repository, such as a publicly released version (alpha, beta, full release, or patch). Similar in concept to labels in VSS.

trunk: The main development line in a VCS repository.

update: Retrieve any changes made to the trunk (or branch) since last update.

working copy: Local copy of a project checked out from a VCS repository.

Read the full article at http://msdn.microsoft.com/en-us/magazine/dd758790.aspx

Extreme ASP.NET Makeover: Getting Your House in Order - Overview

Howard Dierking — Fri, 05 Jun 2009 06:56:00 GMT

I don’t have to remind everyone that we’re in the middle of a world-wide economic downturn. When the economy is good, it is hard enough to convince your client to re-build an application from scratch. When the economy is bad, it is close to impossible. As developers, we’re going to see more push from our clients for evolutionary development of applications rather than wholesale replacement. We will be called upon to improve existing codebases, implement new features, and take these projects in initially unforeseen directions.

In this nine-part article series, I will take you on a journey to improve an existing "classic" ASP.NET Web application. By classic, I mean a Web application written in ASP.NET 1.X or 2.0, but before the widespread use of AJAX techniques or ASP.NET MVC. In other words, a Web application that you wouldn't be surprised to find running in your corporate data center or somewhere on the internet, or a workhorse of an application that gets the job done, but doesn't necessarily do it in a manner that is maintainable or that improves the productivity of its users.

In choosing a suitable Web application, I had a few requirements:

· Typical ASP.NET 2.0 codebase

· Good quality codebase

· Familiar business domain concepts

· Real Web application with publicly available source

Based on these requirements, I chose ScrewTurn Wiki, which is available from http://www.screwturn.eu/.

Let me explain why I chose ScrewTurn Wiki.

Typical ASP.NET 2.0 Codebase

I wanted the code to feel familiar so that techniques discussed can be easily transferred to your own codebases. The ScrewTurn Wiki codebase should be familiar to anyone who has ever written an ASP.NET 2.0 Web application—ASPX pages, ASCX controls, master pages, dynamic content stored in a database (or files).

Good Quality Codebase

I wanted the code to look like code that any of us could have written last year, last month, or last week. I want to show ways to improve the codebase, not ridicule its inadequacies. The reason for selecting ScrewTurn Wiki is not because it is desperately in need of improvement. On the contrary, ScrewTurn Wiki is an overall good codebase and could use improvement the way any quality codebase would benefit from improvement.

Familiar Business Domain Concepts

I wanted to choose a business domain that was easily recognizable and understandable to nearly everyone. Shopping carts and eCommerce sites have been used as examples far too frequently. A stock trading application is not a good choice in the current economy. Many other business domains, such as shipping, accounting, and others, simply require too much explanation of core concepts.

With the success of wikis such as Wikipedia.org, every developer should have at least a passing familiarity with the business domain concepts in a wiki—pages, edits, history, diffs, and similar. I hope that this familiarity makes the code easily approachable for a wide developer audience.

Real Web Application with Publicly Available Source

I wanted to improve a real Web application, not some contrived example. Additionally, I wanted to find an application with the source code available so that you could follow along as I refactored the codebase (a code download is available from the MSDN Code Gallery). ScrewTurn Wiki has a public Subversion repository and you can get the latest version of the source code from here:

svn://svn.screwturn.eu/STW/Trunk

You'll need a Subversion client such as TortoiseSVN, available from http://tortoisesvn.net, to download the latest source.

Note that I will be starting from the ScrewTurn Wiki 3.0 Beta codebase, "The Trunk" (noted above). Most ScrewTurn Wiki sites are currently running ScrewTurn Wiki 2.0. I felt that it would be more valuable and relevant to work with the latest source code rather than a previous version.

Other Advantages

Choosing ScrewTurn Wiki for this series has a number of other advantages:

· It is the software behind many wikis on the internet

· It was recently included in Microsoft Web Platform Installer v2

As such, many of you have probably heard of ScrewTurn Wiki even if you haven't looked at the source code.

Another big advantage is that when I contacted ScrewTurn Wiki's author/maintainer, Dario Solera, about using it as the Web application for this article series, he was excited and supportive. When finished with the article series, I will donate all source created back to the ScrewTurn Wiki project.

The Series

So what will I be doing to ScrewTurn Wiki in this nine-part series? I will apply a combination of good software engineering practices and integrate new technologies into the existing ScrewTurn Wiki 3.0 codebase. Each article will cover a different type of improvement and can be read alone or as part of the larger series. Topics will include everything from build automation/scripting, testing, and refactoring to HTTP handlers/modules, AJAX, jQuery, and ASP.NET MVC. This article will focus on “Brownfield Basics” or how to get started with improving an existing application.

What is a Brownfield Application?

Most developers have probably heard the term "greenfield development," meaning a brand new project without any existing source code. The project is a clean slate on which you can make your mark as an architect, developer, or designer. It is your own personal playground.

So what is brownfield? Wikipedia defines brownfield as:

...land previously used for industrial purposes, or certain commercial uses, and that may be contaminated by low concentrations of hazardous waste or pollution and has the potential to be reused once it is cleaned up.

In software development terms, a brownfield application is an existing application which is developmentally hindered by poorly implemented practices, but has the potential for improvement. Poor practices might sound overly harsh, but almost every project can improve its software development practices in one way or another. When starting (or continuing) work on an existing application, we should consider the current practices implemented on the project and how they can be improved. I will examine ScrewTurn Wiki in light of some brownfield basics. (For a deeper look at brownfield development, I recommend Brownfield Application Development in .NET by Kyle Baley and Donald Belcham.)

Brownfield Basics

There are some fundamental software engineering principles that every project should adopt, regardless of the particular methodology to which you might subscribe. They are:

1. Version control

2. Issue tracking

3. Automated, self-contained builds

4. Automated testing

In the rest of this article, we will discuss the first three. Automated testing will be the topic of the next article.

Read the full article at http://msdn.microsoft.com/en-us/magazine/dd758790.aspx

Scott Hanselman - NerdDinner.com

Robert Hess — Thu, 04 Jun 2009 23:39:00 GMT

Scott Hanselman did an interesting session at MIX09 called "File|New -> Company", where he essentially started with a blank screen, and using Visual Studio, ASP.NET, Ajax, and Model View Controller he created an entire website called "NerdDinner.com", which is a social networking sites for... well... nerds, to allow them to coordinate with their friends what restaurants to go to and what to eat.

While we didn't have time in this episode to let Scott repeat this feat, we did get a chance to talk with him about how the various technologies he utilized worked with the tools in order to make it possible.

If you really want to see him take on this challenge, you can watch his session from MIX09:

File|New -> Company: Creating NerdDinner.com with Microsoft ASP.NET Model View Controller (MVC)

And if you want more details about Scott, NerdDinner.com or Model View Controller, here are some additional links:

10-4 Episode 21: Web Tooling Improvements

Drew Robbins — Fri, 29 May 2009 17:20:00 GMT

In this episode of 10-4, Drew Robbins covers some of the new web tooling features in Visual Studio 2010. There is new Code Snippet support for both HTML and JavaScript. In addition, Visual Studio now has a new dynamic JavaScript IntelliSense engine that infers the return type from functions and provides appropriate intellisense. This makes working with JavaScript libraries a lot easier.

More detail about the web deployment features is covered in Episode 10: Making Web Deployment Easier.

Be sure to check out all of the 10-4 episodes where we cover many of the features in Visual Studio 2010 Beta 1 and .NET Framework 4 Beta 1.

Cannon PI - To Catch An Eagle

Mark Brown — Fri, 15 May 2009 17:49:00 GMT

Welcome to Episode #1. In this episode watch Cannon PI, and his sidekick "Jim" as they help two developers get their web developer platform setup and ready to go with the applications they need using the Web Platform Installer.

PS: There is a reference to "The Wizard of OZ" in this episode. See if you can find it in this video. Good luck :)

Cannon PI - Introduction

Mark Brown — Fri, 15 May 2009 06:07:00 GMT

There comes a time only maybe once in our lives where a true hero for the web developer emerges. They are daring problem solvers but may be a little rough around the edges, drive fast cars from the 80’s, drink a bit too much and sometimes are misunderstood.

Well the time has come and a new hero joins us and brings help to Web Developers everywhere. I’d like to introduce you to the, fast driving, hard drinking, moustache wearing, Hawaiian shirt loving, and problem solving, Cannon P.I.

Enjoy our short series and have a few laughs and over the series see if you recognize a few people you may know.

ASP.NET MVC 1 with Phil Haack

Adam Kinney — Wed, 18 Mar 2009 17:15:00 GMT

ASP.NET MVC 1.0 has been released today at MIX09! Phil Haack stopped by the studio last week to explain what makes this version 1 of the MVC Framework for ASP.NET and spends a little time explaining the MVC pattern. Phil then demos the scaffolding functionality which allows you to quickly build a functional website based on your existing data services.

Stephen Walther - New Features of ASP.NET 4.0

Robert Hess — Sat, 14 Mar 2009 00:32:00 GMT

Stephen Walther is preparing two great talks for MIX09 which illustrate some of the new features of ASP.NET 4.0. We were able to spend a little time with him and discussed a couple of the things that he thinks will help developers be more productive in this release.

His MIX09 Sessions are:

Microsoft ASP.NET 4.0 : What’s Next?
Come learn all about ASP.NET 4.0 and the new Microsoft Visual Studio improvements that will make you more productive. Hear how to build a simple video gallery website that takes advantage of new features to control the rendering of client ids and view state, and see how ASP.NET AJAX client-side templates and jQuery animations can be used to create a richly interactive web application.

Microsoft ASP.NET: Taking AJAX to the Next Level
Hear how ASP.NET AJAX 4.0 makes building pure client-side AJAX Web applications even easier, and watch us build an entire data-driven ASP.NET AJAX application from start to finish by taking advantage of only JavaScript, HTML pages, and Windows Communication Foundation (WCF) services. Also learn about new ASP.NET AJAX features including the DataView control, declarative templates, live client-side data binding, WCF, and REST integration.

10-4 Episode 11: Bi-Directional Routing with ASP.NET WebForms 4.0

Jonathan Carter — Thu, 05 Mar 2009 04:30:00 GMT

In this episode of 10-4, we introduce another new feature of ASP.NET WebForms 4.0: Routing. The ASP.NET Routing engine was added in the .NET Framework 3.5 SP1 release and is heavily leveraged by both ASP.NET MVC and ASP.NET Dynamic Data to provide bi-directional routing functionality. With the release of ASP.NET WebForms 4.0, you can take full advantage of the common route engine that allows you to customize the URLs that your application exposes. In addition, new expression builders allow you to generate dynamic URLs that are based on your route definitions, alleviating you from having to hard code static links.

For more 10-4 episodes, be sure to visit:
http://channel9.msdn.com/shows/10-4

Visual Studio Topic Area on Channel 9:
http://channel9.msdn.com/VisualStudio

Visual Studio 2010 CTP VPC:
http://tinyurl.com/GetCTP

ASP.NET Routing:
http://msdn.microsoft.com/en-us/library/cc668201.aspx

10-4! Over and out!

10-4 Episode 10: Making Web Deployment Easier

Drew Robbins — Thu, 26 Feb 2009 06:04:00 GMT

In this episode of 10-4, we'll look at new features coming in Visual Studio 2010 that make deploying web applications a lot easier. We'll look at web.config transformations, the Microsoft web deployment tool and web one-click deployment.

For more 10-4 episodes, be sure to visit:
http://channel9.msdn.com/shows/10-4

Information on the Web Deployment Tool:
http://www.iis.net/extensions/WebDeploymentTool

PDC Session by Vishal Joshi on Visual Studio 2010 Web Deployment:
http://channel9.msdn.com/pdc2008/PC33/

Visual Studio Topic Area on Channel 9:
http://channel9.msdn.com/VisualStudio

Visual Studio 2010 CTP VPC:
http://tinyurl.com/GetCTP

10-4! Over and out!

10-4 Episode 8: Pure Client-Side Development with ASP.NET AJAX 4.0

Jonathan Carter — Wed, 11 Feb 2009 20:40:00 GMT

In this episode of 10-4, we introduce some of the new features and functionality of ASP.NET AJAX 4.0. We’ll see how ASP.NET AJAX can be leveraged in a complete client-side environment, making it easier to develop rich web applications. This episode demonstrates the new client templates, data binding and command bubbling behavior that makes creating data-centric applications using JavaScript simpler. We’ll also see the new ADO.NET Data Services integration which makes performing CRUD operations, complete with change-tracking, very trivial.

For more 10-4 episodes, be sure to visit:
http://channel9.msdn.com/shows/10-4

Visual Studio Topic Area on Channel 9:
http://channel9.msdn.com/VisualStudio

Visual Studio 2010 CTP VPC:
http://tinyurl.com/GetCTP

ASP.NET AJAX 4.0:
http://www.codeplex.com/aspnet/Wiki/View.aspx?title=AJAX&referringTitle=Home

10-4! Over and out!

10-4 Episode 4: No More Parallel Development Pain

Brian Keller — Wed, 07 Jan 2009 20:34:00 GMT

In this episode of 10-4, we'll examine how the improvements to branching and merging in Team Foundation Server 2010 will help eliminate the pain associated with parallel development. Brian Keller demonstrates the new "first class branches," branch visualizations, and the improved conflict resolution experience.

For more 10-4 episodes, be sure to visit:
http://channel9.msdn.com/shows/10-4

Visual Studio Topic Area on Channel 9:
http://channel9.msdn.com/VisualStudio

Visual Studio 2010 CTP VPC:
http://tinyurl.com/GetCTP

Branching and Merging Guidance:
http://tinyurl.com/BranchAndMerge
http://tinyurl.com/BranchAndMerge2

Visualization Interview with Matthew Mitrik:
http://tinyurl.com/C9BranchingVisualization

Over and out!

Media tagged with asp.net - Channel 9

Announcing Microsoft Ajax Library Preview 6

Web Application Toolkit: Template-Driven Emails

ToolShed Tooltip #22 - Channel9 and the Tool Shed ... A Treasure Chest of Resources

Hanselminutes on 9 - ASP.NET MVC 2 Preview 1 with Phil Haack and Virtual Scott

Jan Welker über dotnet-kicks.de

Scott Guthrie at Vista Squad on ASP.NET MVC Part 2

Scott Guthrie at Vista Squad on ASP.NET MVC Part 1

Fastest To Market: RAD Web Applications with ASP.NET Dynamic Data and Entity Framework

Dynamics Duo: Wide World Importers Code

Phil Haack - ASP.NET, MVC, and Ninjas On Fire

10-4 Episode 22: Simplifying Data-Driven Web Applications

Extreme ASP.NET Makeover: Getting Your House in Order - Cmd Line Build

Compile Using MSBuild

Full Build Script

Conclusion

Other videos from this article

Read the full article at http://msdn.microsoft.com/en-us/magazine/dd758790.aspx

Extreme ASP.NET Makeover: Getting Your House in Order - Inspecting a Proj File

Creating an Automated Build Script

Other videos from this article

Read the full article at http://msdn.microsoft.com/en-us/magazine/dd758790.aspx

Extreme ASP.NET Makeover: Getting Your House in Order - Source Control

Version Control

Glossary

Other videos from this article

Read the full article at http://msdn.microsoft.com/en-us/magazine/dd758790.aspx

Extreme ASP.NET Makeover: Getting Your House in Order - Overview

Typical ASP.NET 2.0 Codebase

Good Quality Codebase

Familiar Business Domain Concepts

Real Web Application with Publicly Available Source

Other Advantages

The Series

What is a Brownfield Application?

Brownfield Basics

Other videos from this article

Read the full article at http://msdn.microsoft.com/en-us/magazine/dd758790.aspx

Scott Hanselman - NerdDinner.com

10-4 Episode 21: Web Tooling Improvements

Cannon PI - To Catch An Eagle

Cannon PI - Introduction

ASP.NET MVC 1 with Phil Haack

Stephen Walther - New Features of ASP.NET 4.0

10-4 Episode 11: Bi-Directional Routing with ASP.NET WebForms 4.0

10-4 Episode 10: Making Web Deployment Easier

10-4 Episode 8: Pure Client-Side Development with ASP.NET AJAX 4.0

10-4 Episode 4: No More Parallel Development Pain