Popular Articles
Last viewed:
- Add a Composite Control to the Visual Studio Toolbox
- Install Windws 2003 Terminal Service Licenses (Remote Desktop)
- Deploy Crystal Reports 2008 Run-time on Remote Server
- Override Default SPAN Tag for Composite Controls
- Get the list of ODBC data source names programatically using C#
- SQL Server Database Project and Database Source Control
Recent comments
- Reply
1 day 19 hours ago - Thank you!
6 days 9 hours ago - Thanks!!
6 days 10 hours ago - Lotus Email Server Stop
1 week 18 hours ago - awesome article masssthhh
1 week 2 days ago - Awesome!
2 weeks 8 hours ago - get blank pdf
2 weeks 1 day ago - TXLDnoMyeLVmZKXPTJT
2 weeks 4 days ago - hPLvcrWMPCDOIpXDg
2 weeks 6 days ago - JijKgYDvBZXRZ
2 weeks 6 days ago

A response to your observations
Yes, this would very easily be a static class or at the very least, a series of static methods within this class. There is no intrinsic state so it shouldn't cause any problems to make this static. This also saves a line of code everytime you use it so it's a good point.
On the second for the implementation details when serializing the user's data, I agree. It can be more hidden. In some ways, I think I did it this way so it was clearer when I posted the article about what was happening. Feel free to hide it or post your changes here. Thanks!