Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / New Users / April 2005

Tip: Looking for answers? Try searching our database.

Framework 2.0: Application settings per library and per user

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
StealthyMark - 09 Apr 2005 21:59 GMT
I'm developing a library intended to be used by several applications. This
library contains some Forms. I want to persist settings like window size,
splitter positions etc.

Currently, I'm using an autogenerated *.settings file. Visual Studio
generates a wrapper class for the
System.Configuration.ApplicationSettingsBase. In the form designer, I'm
binding some control properties to some properties in the settings class.
The settings are automatically saved to
%LocalApplicationData%\%CompanyAttribute%\%AssemblyNameFileName%_CrypticValue\%FileVersionAttribute%\user.config

%LocalApplicationData%    The path to the non-roaming user data directory.

The following informations are extracted from the *application* using the
library
%CompanyAttribute%        The value of the Company attribute
%AssemblyNameFileName%    The name of the application
%FileVersionAttribute%    The value of the FileVersion attribute

That works quite good, except for two problems.

First and most important I'd like to persist the settings globally for the
library, equal for all applications, unique for each user. How to achieve
that? Any hints?

Second, is there a way *in the settings editor* to specify whether the
property is Roaming or not? There is an attribute,
System.Configuration.SettingsManageability. But you have to apply that in
the autogenerated *.Designer.cs file... which is overwritten by the
designer.

Mark Rockmann
"Peter Huang" [MSFT] - 12 Apr 2005 03:24 GMT
Hi

Since VS.NET 2005(Whidbey) has not been released, so far for Whidbey issue,
we have a definitely newsgroup about Whidbey.
Welcome to the Microsoft Visual Studio 2005 Newsgroups
http://communities.microsoft.com/newsgroups/default.asp?icp=whidbey&slcid=us

Or post in the newsgroup below.
microsoft.beta.whidbey.*

Thanks for your understanding!

Best regards,

Peter Huang
Microsoft Online Partner Support

Signature

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.