ASP.NET MVC 2 (Release Candidate 2) Now Available

[In addition to blogging, I am also now using Twitter for quick updates and to share links. Follow me at: twitter.com/scottgu]

Earlier this evening the ASP.NET team shipped ASP.NET MVC (Release Candidate 2) for VS 2008/.NET 3.5.  You can download it here.

The RC2 release of ASP.NET MVC 2 is a follow-up to the first ASP.NET MVC 2 RC build that we shipped in December.  It includes a bunch of bug fixes, performance work, and some final API and behavior additions/changes.  Below are a few of the changes between the RC1 and RC2 release (read the release notes for even more details):

  • The new ASP.NET MVC 2 validation feature now performs model-validation instead of input-validation (this means that when you use model binding all model properties are validated instead of just validations on changed values of a model).  This behavior change was based on extensive feedback from the community.
  • The new strongly-typed HTML input helpers now support lambda expressions which reference array or collection indexes.  This means you can now write code like Html.EditorFor(m=>m.Orders[i]) and have it correctly output an HTML <input> element whose “name” attribute contains the index (e.g. Orders[0] for the first element), and whose “value” contains the appropriate value.
  • The new templated Html.EditorFor() and Html.DisplayFor() helper methods now auto-scaffold simple properties (and do not render complex sub-properties by default).  This makes it easier to generate automatic scaffolded forms.  I’ll be covering this support in a future blog post.
  • The “id” attribute of client-script validation message elements is now cleaner.  With RC1 they had a form0_ prefix.  Now the id value is simply the input form element name postfixed with a validationMessage string (e.g. unitPrice_validationMessage).
  • The Html.ValidationSummary() helper method now takes an optional boolean parameter which enables you to control whether only model-level validation messages are rendered by it, or whether property level validation messages are rendered as well.  This provides you with more UI customization options for how validation messages are displayed within your UI.
  • The AccountController class created with the default ASP.NET MVC Web Application project template is cleaner.
  • Visual Studio now includes scaffolding support for Delete action methods within Controllers, as well as Delete views (I always found it odd that the default T4 templates didn’t support this before).
  • jQuery 1.4.1 is now included by default with new ASP.NET MVC 2 projects, along with a -vsdoc file that provides Visual Studio documentation intellisense for it.
  • The RC2 release has some significant performance tuning improvements (for example: the lambda based strongly-typed HTML helpers are now much faster).

Today’s RC2 release only work with VS 2008 and .NET 3.5.  We’ll shortly be releasing the VS 2010 RC (which will be available for everyone to download). It will include ASP. NET MVC 2 support built-in (no separate download required).

Hope this helps,

Scott

P.S. The source code for the ASP.NET MVC RC2 release (along with a MVC futures library that goes with it) can be downloaded here. You can learn even more about ASP.NET MVC 2 by reading the ASP.NET MVC 2 blog series I’m working on.

Host Integration Server 2006 Service Pack 1 has been released

Microsoft Host Integration Server 2006 Service Pack 1 has been released and is available for download here

This Service Pack includes hotfixes based on customer request and other fixes initiated by the product team. It improves the quality, reliability and supportability of Host Integration Server 2006 and BizTalk Adapters for Host Systems.

The following KB articles regarding this Service Pack will be available soon on Microsoft support site:

%u00b7 KB 979238 – A list of the bugs that are fixed in Host Integration Server 2006 Service Pack 1 – http://support.microsoft.com/kb/979238

Regards,

Ofer

Host Integration Server 2006 – Service Pack 1: Now Available

Wow, it must be the week for Service Pack announcements. First we see the BizTalk 2006-R1 SP and now HIS 2006 gets its very own SP.  Details from about the release are below. Please note, that the Knowledge Base articles listed below might not be active for a couple of days. So if you try and them and they don’t work, give it a day before you hammer me on posting dead links.

>>>>

Host Integration Server 2006 Service Pack 1 is now available for download at the following location:

http://www.microsoft.com/downloads/details.aspx?FamilyID=c0cc5e8d-fc47-41ac-bcad-67832249eb41

Host Integration Server 2006 Service Pack 1 provides the latest updates for Microsoft Host Integration Server 2006 and Microsoft BizTalk Adapters for Host Systems. It delivers customer requested hotfixes that improve the quality, reliability and supportability of Host Integration Server 2006 and BizTalk Adapters for Host Systems. The following two Knowledge Base articles will be available soon to describe the list of fixes and how to download the service pack:

KB 979238 – A list of the bugs that are fixed in Host Integration Server 2006 Service Pack 1 – http://support.microsoft.com/kb/979238

KB 979497 – How to obtain the latest Host Integration Server 2006 service pack – http://support.microsoft.com/kb/979497

Congratulations to the HIS Product Team, BPD Engineering Services team and CSS engineers who made this happen.  Having this service pack available for our customers now allows us to efficiently support customers and focus on future releases of Host Integration Server.

>>>>

Cheers and keep on BizTalking

Peter

ESB Itinerary Selector: Parameter name cannot be null or an empty string. Parameter name: key

Event Type:Error

Event Source:BizTalk ESB Toolkit 2.0

Event Category:None

Event ID:6060

Date:1/31/2010

Time:7:06:00 AM

User:N/A

Computer:WS03_OFFICE07

Description:

Parameter name cannot be null or an empty string.

Parameter name: key

Source: Microsoft.Practices.ESB.Resolver.ResolverMgr

Method: System.Collections.Generic.Dictionary`2[System.String,System.String] Resolve(Microsoft.Practices.ESB.Resolver.ResolverInfo, Microsoft.BizTalk.Message.Interop.IBaseMessage, Microsoft.BizTalk.Component.Interop.IPipelineContext)

Error Source: Microsoft.Practices.EnterpriseLibrary.Caching

Error TargetSite: Void ValidateKey(System.String)

Error StackTrace: at Microsoft.Practices.EnterpriseLibrary.Caching.Cache.ValidateKey(String key)

at Microsoft.Practices.EnterpriseLibrary.Caching.Cache.GetData(String key)

at Microsoft.Practices.EnterpriseLibrary.Caching.CacheManager.GetData(String key)

at Microsoft.Practices.ESB.Cache.Cache`1.Get(String key, Boolean returnAndRemove)

at Microsoft.Practices.ESB.Cache.Cache`1.Get(String key)

at Microsoft.Practices.ESB.Resolver.ResolverMgr.GetResolver(ResolverInfo info)

at Microsoft.Practices.ESB.Resolver.ResolverMgr.Resolve(ResolverInfo info, IBaseMessage message, IPipelineContext pipelineContext)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The issue was that I had the BRI string like this: BRI:// instead of BRI:\\ in the pipeline component’s configuration. The latter is the correct way