469,623 Members | 1,935 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,623 developers. It's quick & easy.

The current configuration system does not support user-scoped settings.

What does mean this error?
The current configuration system does not support user-scoped settings.

I'm accessing a my.settings data from a DAL dll referenced by an ASP.NET
app. I've a similar other application that works well. The one with the
problem is an 1.1 upgraded, the one that works a native 2.0. I cannot find
differences :(


May 3 '06 #1
3 8566
Ok, it was very stupid to find.. :((
"Trapulo" <tr*****@noemail.noemail> wrote in message
news:eq**************@TK2MSFTNGP05.phx.gbl...
What does mean this error?
The current configuration system does not support user-scoped settings.

I'm accessing a my.settings data from a DAL dll referenced by an ASP.NET
app. I've a similar other application that works well. The one with the
problem is an 1.1 upgraded, the one that works a native 2.0. I cannot find
differences :(


May 3 '06 #2
Hi Trapulo,

Thank you for posting.

My.Settings object in VB.NET 2005 is normally used to access user-scope
settings. User-scope settings are often used by WinForm applications which
run under a specific user account. Since ASP.NET applications run under a
server account, using user-scope settings here is not appropriate.

If you are using ConfigruationSettings.AppSettings previously in your 1.1
DAL dll, you can now use ConfigurationManager.AppSettings after upgraded to
2.0 (remember to reference System.Configuration assembly first).

If you still want to access user-scope settings, you can use Profiles in
ASP.NET 2.0.

If there is anything unclear, please feel free to post here.

Regards,

Walter Wang
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

May 4 '06 #3
Thank you.

In fact I jsut selected "user" scope insted of "application" scope on my
project's settings.
"Walter Wang [MSFT]" <wa****@online.microsoft.com> wrote in message
news:OZ****************@TK2MSFTNGXA01.phx.gbl...
Hi Trapulo,

Thank you for posting.

My.Settings object in VB.NET 2005 is normally used to access user-scope
settings. User-scope settings are often used by WinForm applications which
run under a specific user account. Since ASP.NET applications run under a
server account, using user-scope settings here is not appropriate.

If you are using ConfigruationSettings.AppSettings previously in your 1.1
DAL dll, you can now use ConfigurationManager.AppSettings after upgraded
to
2.0 (remember to reference System.Configuration assembly first).

If you still want to access user-scope settings, you can use Profiles in
ASP.NET 2.0.

If there is anything unclear, please feel free to post here.

Regards,

Walter Wang
Microsoft Online Community Support


May 5 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Thom Little | last post: by
2 posts views Thread by Terry Holland | last post: by
7 posts views Thread by Steven Cliff | last post: by
3 posts views Thread by Lattis | last post: by
7 posts views Thread by =?Utf-8?B?RG91Z2llIEJyb3du?= | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.