Client Settings FAQ

re: Client Settings FAQ

rprabhu — Tue, 19 Dec 2006 03:46:32 GMT

Aaron: One way to quickly test correct behavior is to use Ctrl + F5 in Visual Studio instead of F5. This will cause the app to run normally and not under the vshost process.

Also, there is an option in Application Properties in VS to disable the vshost process if you want to.

re: Client Settings FAQ

Aaron Oneal — Sat, 16 Dec 2006 17:01:13 GMT

Tony, I have the same problem when running my apps under Visual Studio when code is running under an app domain that doesn't have an executing assembly. For example, I have a host process (app domain) that creates several child app domains (one for each plugin). If I use the config manager under one of the plugin domains (which doesn't have an executing assembly), the config manager tries to pull the properties for the user path from the executing process EXE using a native call. Unfortunately, the executing process EXE is usually the vshost.exe wrapper process, which has Microsoft as the company, and the VS version as the version instead of the information from my process executing assembly. I suppose when deployed and not running under VS it would probably come up with the right company and version values, but it makes testing annoying.

re: Client Settings FAQ

rprabhu — Thu, 23 Nov 2006 00:39:28 GMT

Tony: IIRC, using the LocalFileSettingsProvider within VSTO is not a supported or tested scenario. It is not explicitly blocked so might seem to work, but I recommend against using it in *shipping* code, as you might run into problems (unfortunately, I don't remember what specific issues there were - I moved to a different part of Microsoft over an year ago).

But do double check by posting this question on the MSDN forums if you wish.

I would recommend writing your own provider, which is pretty simple to do, starting with the samples/docs on MSDN.

re: Client Settings FAQ

Tony — Wed, 22 Nov 2006 13:47:19 GMT

Hello rprabhu,

in the answer of the last question (Is the settings functionality available only to Windows Forms applications?) you wrote, that user.config isn't supported for VSTO apps. I found out, that this is not correct. I use userSettings in my VSTO-OutlookAddin and it works. The only 'problem' is, that the path, where the user.config is saved contains "Microsoft_Corporation" istead of the AssemblyCompany of my AssemblyInfo.

Could it become a problem? Is it safe, to use the default settings provider in a VSTO app, or should I write my own settings provider?

Thanks in advance

Regards,

Tony

re: Client Settings FAQ

rprabhu — Sun, 19 Nov 2006 22:56:50 GMT

'Gbenga: Unfortunately, I don't know the answer to your question. I suggest posting it on one of the .NET forums or newsgroups.

re: Client Settings FAQ

'Gbenga — Sat, 18 Nov 2006 01:21:51 GMT

I'm developing a Windows CE application. I need to persist some settings across applications sessions like web service url. But there is no Settings option in Win CE Device App project. Any suggestion on how to persist the settings?

Thanks.

re: Client Settings FAQ

rprabhu — Tue, 15 Aug 2006 23:17:40 GMT

Brian: Good to know you got it working!

Marty: Sorry, I am not aware of how NetRun deployment works. If you can isolate an issue, please report it through MSDN Product Feedback so the right folks can investigate.

re: Client Settings FAQ

Brian — Sun, 13 Aug 2006 00:15:26 GMT

Hello Raghavendra,

Thanks for the fast response, but I've pin pointed the problem. ;)

ApplicationSettingsBase internally uses Refleciton and Assembly.Load() to seralize/deserialze types. Deserialization failed for complex (custom) types because the EXE assembly containg these types was packed and encrypted by the loader as a resource (inside the loader EXE)... since the runtime only saw the EXE loader assembly, it failed to resolve types correcty.

Solution:

Move all seralized types that need to be accessed by the runtime to a seperate DLL library. Pack the EXE assembly and DLL assembly then hook assembly resolve type events emitted by the CLR to correct the problem.

-Brian

re: Client Settings using NetRun

Marty Cerisano — Fri, 11 Aug 2006 19:44:04 GMT

I have a windows app that is deployed using NetRun. When I run it from a users machine the configuration API is unable to retrieve the Configuration.FilePath. I am assuming this is because applications installed using NetRun execute under a restricted context.

Any experience or solutions for this scenario?

re: Client Settings FAQ

Matt — Fri, 11 Aug 2006 03:57:30 GMT

Awesome got it working.

yep my config file was unhappy killed it and re did it and all worked fine at runtime.

Still got an error message in the desinger telling me it couldnt load the provider type. So i change the line

<SettingsProvider("[assembly].[provider], [assembly]")>

to

<SettingsProvider(GetType([Provider]))> _

and all is working great.

Cheers for your quick response