KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
Which is best way to organize resource files in an application? Currently in my application my resources are added inside an ResourceLib project which has this structure: Color [folder] ColorTheme1.xaml ColorTheme2.xaml ColorTheme2.xaml . . . StyleResource[Folder] Button.xaml ToggleButton.xaml TextBox.xaml ListBox.xaml Treeview.xaml . . . . HeaderStyle [folder] HeaderStyle1.xaml HeaderStyle2.xaml . . . etc This list will keep on increasing as the day progresses. In the App.xaml i am referencing this Library and merging these dictionary file for one time initialization. DynamicResource is used to support theme facility. Will there be any performance impact if continue with this structure?. Is there any advantage or performance impact if i put all these xaml in to one resource name (Style.xaml)? What are the performance implications of a Style.xaml with 5000 lines versus splitting same into 10 different xaml files? Finally, which is the best or accepted method?
Tags (comma-separated)
Save Edits
Cancel