News

RC2 of ASP.NET MVC Released

Microsoft this week unexpectedly issued a second release candidate (RC) of its ASP.NET Model View Controller (MVC), the company's a design pattern for test-driven development of enterprise-scale Web applications.

The release comes just over a month after Microsoft posted RC1, at the time describing it as feature-complete and likely to ship by March. But based on feedback from the RC1 beta, the company decided some key fixes were needed, according to Phil Haack, senior program manager on Microsoft's ASP.NET team, who is working on the ASP.NET MVC Framework.

"We realized it would be prudent to have one more public release candidate," Haack said in a blog posting Tuesday. Most of the changes are in the installer and few alterations were made to the runtime and tooling, he noted.

One of the changes is that the new installer will require developers to install the .NET Framework 3.5 SP1. Microsoft is also recommending developers install Visual Studio 2008 SP1, though it is not required.

"The reason we made this change is that we were including the System.Web.Routing.dll and System.Web.Abstractions.dll assemblies with the MVC installer," Haack said. "However, it does not make sense for us to co-ship assemblies which are part of the Framework as this would negatively affect our ability to service these two assemblies."

RC2 also offers a new server-only install mode to the installer that does not have Visual Studio on production systems. "The installer will no longer block on a machine that does not have Visual Studio installed," Haack said. "Instead, it will continue the standard MVC installation without installing the Visual Studio templates. The assemblies will still be installed into the GAC and native images will also be generated."

Microsoft removed some other requirements, as well. For instance, if an installation has Visual Web Developer Express Edition 2008 without SP1, the installation will still proceed, though the developer will receive a warning, Haack said.

Also added was an upgrade to jQuery 1.3.1, noted Steve Michelotti, principal software engineer at Applied Information Sciences, who wrote a cover story on ASP.NET MVC in the January issue of Visual Studio Magazine.

"I was very happy to see that they also included the upgrade to jQuery 1.3.1." Michelotti said in an e-mail.

Though the need for an RC2 was a surprise to Michelotti, he welcomed the changes. "Better to do more RCs and get it right with the support of the developer community than to rush something out the door," he said. "They're proactively making these changes while still being sensitive to not make drastic API changes this late in the game as the product moves towards a mature RTM."

The source code can be downloaded on Microsoft's CodePlex site here.

About the Author

Jeffrey Schwartz is editor of Redmond magazine and also covers cloud computing for Virtualization Review's Cloud Report. In addition, he writes the Channeling the Cloud column for Redmond Channel Partner. Follow him on Twitter @JeffreySchwartz.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube