Rename Content property back to Control (IViewContent, IPadContent, IOptionsPanel) to prevent the C# compiler from automatically picking up a Content property from a base class.
The name 'Content' could result in a hard to understand exception 'Specified element is already the logical child of another element. Disconnect it first.' when implementing IOptionPanel in a WPF UserControl. See forum-9233.
git-svn-id: svn://svn.sharpdevelop.net/sharpdevelop/trunk@4018 1ccf3a8d-04fe-1044-b7c0-cef0b8235c61
// We cannot extend an existing interface in 3.x because we don't want to break addin compatibility.
// TODO: merge this interface with IBuildable in SharpDevelop 4.0
publicinterfaceIBuildable2:IBuildable
{
/// <summary>
/// Creates the project-specific build options.
/// </summary>
/// <param name="options">The global build options.</param>
/// <param name="isRootBuildable">Specifies whether this project is the main buildable item
/// (i.e. the ).</param>
/// <param name="isRootBuildable">Specifies whether this project is the main buildable item.
/// The root buildable is the buildable for which <see cref="BuildOptions.ProjectTarget"/> and <see cref="BuildOptions.ProjectAdditionalProperties"/> apply.
/// The dependencies of that root buildable are the non-root buildables.</param>
[Obsolete("This property does not do what one would expect - it merely checks if protected+internal are set, it is not the equivalent of AssemblyAndFamily in Reflection!")]
boolIsProtectedAndInternal{
get;
}
[Obsolete("This property does not do what one would expect - it merely checks if one of protected+internal is set, it is not the equivalent of AssemblyOrFamily in Reflection!")]
Daniel Grunwald
17 years ago