remove duplicate entry causing solution load errors.

[ranjeshj]

RadioButton_themeresources.xaml is included from multiple projects causing the mux project to not load in visual studio. msbuild seems to happily ignore it though - so it does not cause a build break in the pipelines.

Fixes #1982

[ojhad]

  <Type>ThemeResources</Type>

Out of curiosity, why delete the 'DefaultStyle' type duplicate entry instead of the 'ThemeResources' type?

---

Refers to: dev/RadioButtons/RadioButtons.vcxitems:38 in 868a941. [](commit_id = 868a941, deletion_comment = False)

[marcelwgn]

@ojhad The thing is that the ThemeResource is also referenced in the CommonStyles.vcxitems file, while the other is not. I have to admit its quite confusing that we have "RadioButton_themeresources.xaml" and "RadioButtons_themeresources.xaml".

[marcelwgn]

On a different note, maybe we could also remove the reference to the "RadioButton_themeresource.xaml" file from here:

microsoft-ui-xaml/dev/CommonStyles/CommonStyles.vcxitems

Lines 17 to 20 in ee03bac

	<Page Include="$(MSBuildThisFileDirectory)..\RadioButtons\RadioButton_themeresources.xaml">
	<Version>RS1</Version>
	<Type>ThemeResources</Type>
	</Page>

The RadioButton file is the only file referenced there that is not in the "CommonStyles" folder but sits in another project.

[ranjeshj]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[kmahone]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ranjeshj]

uttons/RadioButtons.vcxitems:38 in 868a941. [](commit_id = 868a941, deletion_comment =

This took a bit of digging, but turns out we use these tags in our targets/build tasks to put together what goes in the themeresources and generic.xaml. See here for more.

[ranjeshj]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ranjeshj]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[StephenLPeters]

@ranjeshj want to move this in?