Bug 39863 - [iOS] Internationalization settings in Project properties are ignored
Summary: [iOS] Internationalization settings in Project properties are ignored
Status: RESOLVED DUPLICATE of bug 29323
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 4.0.0 (C6)
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-03-23 11:51 UTC by Prashant Cholachagudda
Modified: 2016-03-29 07:51 UTC (History)
5 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Prashant Cholachagudda 2016-03-23 11:51:09 UTC
Internationalization settings in Project properties are ignored in Visual Studio

# Steps to reproduce

- Create an iOS project
- Open project properties
- Enable `west` in iOS Build/Advanced/Internationalization
- Build the project
- Close VS
- Reopen the project, and notice that previously set Internationalization settings are lost

# Expected behaviour
Internationalization settings should be persisted between the sessions

# Version Information
VS 2015 (Update 1)
Xamarin v4.0.1.147 (1cc3a99)
Comment 1 Brendan Zagaeski (Xamarin Team, assistant) 2016-03-23 18:06:34 UTC

*** This bug has been marked as a duplicate of bug 29323 ***