src/Umbraco.Web/Mvc/PluginControllerMetadata.cs

using System;

namespace Umbraco.Web.Mvc
{
	/// <summary>
	/// Represents some metadata about the surface controller
	/// </summary>
	internal class PluginControllerMetadata
	{
		internal Type ControllerType { get; set; }
		internal string ControllerName { get; set; }
		internal string ControllerNamespace { get; set; }
		internal string AreaName { get; set; }
	}
}
Added all code to support auto-routing surface controllers and started implementing the code for BeginUmbracoForm. 2012-09-25 13:09:59 +07:00			`using System;`

			`namespace Umbraco.Web.Mvc`
			`{`
			`/// <summary>`
			`/// Represents some metadata about the surface controller`
			`/// </summary>`
Changed how surface controllers are routed: because we don't load plugins in via App_Plugins/[PackageName] like we did in v5 which meant that we can autoroute all plugin controllers with their own areas, in v4 we have to do something different. Instead (because we still want areas), we have an attribute called PluginControllerAttribute which allows a dev to assign an area name as a string. A package developer should always ensure that all of their plugin controllers are assigned to the same area. This also lets us get rid of the GUID id part of the plugin (hopefully we can leave it out, just need to run some tests). Since we have areas, package devs can then put their views into their own folders and not clutter up the local devs ~/Views folder. Perhaps we use App_Plugins/[PackageName] for the views like we did in v5 but need to ask on the mail list. Otherwise it will be the standard MVC: ~/Areas/[AreaName]/Views which will still also clutter up the local devs view folder if they are using Areas. 2012-09-26 11:04:07 +07:00			`internal class PluginControllerMetadata`
Added all code to support auto-routing surface controllers and started implementing the code for BeginUmbracoForm. 2012-09-25 13:09:59 +07:00			`{`
			`internal Type ControllerType { get; set; }`
			`internal string ControllerName { get; set; }`
			`internal string ControllerNamespace { get; set; }`
Changed how surface controllers are routed: because we don't load plugins in via App_Plugins/[PackageName] like we did in v5 which meant that we can autoroute all plugin controllers with their own areas, in v4 we have to do something different. Instead (because we still want areas), we have an attribute called PluginControllerAttribute which allows a dev to assign an area name as a string. A package developer should always ensure that all of their plugin controllers are assigned to the same area. This also lets us get rid of the GUID id part of the plugin (hopefully we can leave it out, just need to run some tests). Since we have areas, package devs can then put their views into their own folders and not clutter up the local devs ~/Views folder. Perhaps we use App_Plugins/[PackageName] for the views like we did in v5 but need to ask on the mail list. Otherwise it will be the standard MVC: ~/Areas/[AreaName]/Views which will still also clutter up the local devs view folder if they are using Areas. 2012-09-26 11:04:07 +07:00			`internal string AreaName { get; set; }`
Added all code to support auto-routing surface controllers and started implementing the code for BeginUmbracoForm. 2012-09-25 13:09:59 +07:00			`}`
			`}`