The basic idea:
In a different project, create classes that will hold your custom settings. For example:
public class EndPoint
{
public string HostName { get; set; }
public int Port { get; set; }
}
public class EndPointCollection : Collection<EndPoint>
{
}
Build the project containing the classes.
Go to the Settings tab in Project Properties. It will say that there is no settings file yet and ask if you want to create it.
Add a new settings file. In the type field select Browse and type the full class name. For example: ClassLibrary.EndPointCollection
. Save and rebuild the project.
Hit the edit button for the setting value. (Note that this will not be available if the classes made in the earlier step are in the same project.) Use the UI to edit the settings.
If you open the web.config / app.config file, you will see something like this:
...
<applicationSettings>
<WebApplication1.Properties.Settings>
<setting name="MyEndPoints"
serializeAs="Xml">
<value>
<ArrayOfEndPoint xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<EndPoint>
<HostName>MyHostName</HostName>
<Port>12345</Port>
</EndPoint>
<EndPoint>
<HostName>MyHost1</HostName>
<Port>1212</Port>
</EndPoint>
</ArrayOfEndPoint>
</value>
</setting>
</WebApplication1.Properties.Settings>
</applicationSettings>
...
Finally, to read these settings from your code, simply use
var endPointCollection = Settings.Default.MyEndPoints;
The designer will have created, behind the scenes, the strongly-typed objects to allow the above to work. You can see the full details in the Settings.Designer.cs
file.
Bottom line: you can make all kinds of custom type settings, as long as those settings have XmlSerializable or have type converter. This technique works on Web Applications, WinForms, WPF, Console Applications etc.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…