locked
[UWP]Unable to find Resource / Key after updating project to Anniversary Edition RRS feed

  • Question

  • Hi, 

    We are  developing a windows universal app in which we have set :

    Min. version to : 10.0;build 10240 and

    Target version to : 10.0; build 14393 (Anniversary edition : to make use of recent control available)

    But if we try to deploy our App to 10240 or 10586 (Minimum versions) , then visual studio unable to find predefined resources like :

    PivotItemBackground / RadioButtonBackground.

    These templates are available inside inbuilt generic.xaml but visual studio is unable to find these resources.

    Is there any problem with anniversary edition of universal SDK ?

    or How we can use update control / properties available in Anniversary edition ?

    Thanks.


    Pardeep



    • Edited by Pardeep89 Wednesday, September 14, 2016 11:14 AM
    • Edited by Xavier Xie-MSFT Thursday, September 15, 2016 6:53 AM subject
    Wednesday, September 14, 2016 7:44 AM

Answers

  • Hi Pardeep89,

    The style of PivotItem is different between “14393” and previous build version.

    The “10240” and “10586”:

    The “14393”:

    The PivotItemBackground ThemeResource is not available in “10240” and “10586”, so you faced this issue.

    >>” Is there any problem with anniversary edition of universal SDK ?”

    I think it has no problem. This resource is available in 14393. If your project was target for “14393”, then this resource would not be available in “10240” and “10586”.

    If you have to deploy it to previous build version, you should not use “PivotItemBackground”.

    Best Regards,

    Xavier Eoro


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    • Proposed as answer by Azat Tazayan Thursday, September 15, 2016 3:53 PM
    • Marked as answer by Xavier Xie-MSFT Thursday, September 29, 2016 12:19 PM
    Thursday, September 15, 2016 7:40 AM

All replies

  • Hi Pardeep89,

    The style of PivotItem is different between “14393” and previous build version.

    The “10240” and “10586”:

    The “14393”:

    The PivotItemBackground ThemeResource is not available in “10240” and “10586”, so you faced this issue.

    >>” Is there any problem with anniversary edition of universal SDK ?”

    I think it has no problem. This resource is available in 14393. If your project was target for “14393”, then this resource would not be available in “10240” and “10586”.

    If you have to deploy it to previous build version, you should not use “PivotItemBackground”.

    Best Regards,

    Xavier Eoro


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    • Proposed as answer by Azat Tazayan Thursday, September 15, 2016 3:53 PM
    • Marked as answer by Xavier Xie-MSFT Thursday, September 29, 2016 12:19 PM
    Thursday, September 15, 2016 7:40 AM
  • Hi Xavier,

    We have created our project while targeting :

    Min. version = 10240 & Target Version = 10586

    But recently we have to upgrade our project due to updated controls/properties available inside Anniversary edition.

    Due to this now we can't run our app on older versions like 10240 because some of the unavailable/renamed ThemeResources(which result in app crash) .

    So according to your reply, Do we need to delete all those ThemeResources  from our project and controls ?

    Isn't there anything like backward compatibility while implementing anniversary update ? 

    Thanks.


    Pardeep

    Thursday, September 15, 2016 12:26 PM
  • Hi Pardeep89,

    >>"Do we need to delete all those ThemeResources  from our project and controls ?"

    No. You just need to delete those ThemeResources which are not contained in the previous build version. Or you could specify a value to the "Background" like the previous version.

    >>"Isn't there anything like backward compatibility while implementing anniversary update ?"

    For the moment, there's no such way to do it. You could use windows 10 Feedback Hub to submit your suggestion.

    Best Regards,

    Xavier Eoro


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Friday, September 16, 2016 1:35 AM