UpdatePriority too restrictive

Jan 25, 2011 at 4:42 PM

Just a thought, using an enum for UpdatePriority is a bit restrictive. I'm implementing MvcSiteMapProvider in a project where we need to mimic existing functionality and there are six levels of priority set for the sitemap (0.5, 0.6. 0.7, 0.8, 0..9 and 1.0).

Unfortunately, I'm limited to three usable priorities in the current version of MvcSiteMapProvider (Normal = 0.5, High = 0.75 and Critical = 1.0).

It might be useful to make this a simple string parameter so we can pass in whatever priority value we want.

Jan 27, 2011 at 7:05 AM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.