You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The styles used in the XAML should all be public styles. Refer to the Pro Style Guide for the available public styles.
The classes for the user controls located inside the Pages folder should reside in this namespace namespace MetadataToolkit.Pages. This is the convention Visual Studio follows.
A new Custom page should be added in the DAML. Screenshot of what we want is below along with code syntax.
DAML:
<!-- TODO add your custom pages for Overview here -->
<pageclass="$safeprojectname$.CustomPage">
<validation>
</validation>
</page>
Code behind and xaml:
using ....
namespace MetadataToolkitSix
{internalclassCustomPageLabel:ISidebarLabel{string ISidebarLabel.SidebarLabel{get{return CustomPageLabel.SidebarLabel;}}publicstaticstringSidebarLabel{get{return"Custom Page";}}}/// <summary>/// Interaction logic for CustomPage.xaml/// </summary>publicpartialclassCustomPage:EditorPage{publicCustomPage(){
InitializeComponent();}publicoverridestringSidebarLabel{get{return CustomPageLabel.SidebarLabel;}}}}
The styles used in the XAML should all be public styles. Refer to the Pro Style Guide for the available public styles.
The classes for the user controls located inside the Pages folder should reside in this namespace
namespace MetadataToolkit.Pages
. This is the convention Visual Studio follows.A new Custom page should be added in the DAML. Screenshot of what we want is below along with code syntax.
DAML:
Code behind and xaml:
The text was updated successfully, but these errors were encountered: