ApplicationSettingsBase fails silently in special case with pre-generated serialization assembly - by Martin S. Müller

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 777672 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/28/2013 5:30:00 AM
Access Restriction Public


Please see "Steps to reproduce".

Note that the program works fine when no serialization dll is generated. And the program works fine when the declaration of StringList is moved before the declaration of MyStringCollection (because this changes the types contained in the serialization dll).

What I especially dislike with this issue is that the failure is completely silent - no errors, no exceptions.
Sign in to post a comment.
Posted by Piyush [MSFT] on 2/15/2013 at 1:45 PM
Hi Martin,
Thanks for your feedback. Since there is a workaround available right now, we have decided not to fix this in the current release. We will continue to monitor the customer feedback and reevaluate if more customers run into this.
Posted by Microsoft on 1/30/2013 at 12:55 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Martin S. Müller on 1/29/2013 at 3:36 AM
Well, maybe the MSDN should contain some more documentation where to find the settings files ;-)
Posted by Martin S. Müller on 1/29/2013 at 2:47 AM
The settings file is named user.config and stored in


which is typically

C:\Users\<your user>\AppData\Local\<Company>\...
Posted by Microsoft on 1/29/2013 at 2:27 AM
Hi Martin S. Müller, i can't find the xml settings file. Please help. thanks.
Posted by Macy [MSFT] on 1/28/2013 at 5:52 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(