If you've got fulltrust, you don't need to go to isolated storage & probably want to avoid it. IS is a sandbox for less trusted code. Dig this path for an IS location on my computer:
C:\Documents and Settings\pardre1\Local Settings\Application Data\IsolatedStorage\lzh3mi31.0mg\ujzyldhs.5yw\StrongName.5banoyyo4hbmp2 ojgawik3aymbsmb2gm\StrongName.5banoyyo4hbmp2ojgawik3aymbsmb2gm\Files That path is not something your code has any say over--you just call stuff in IsolatedStorage & the framework figures out what physical path to use. End-user file perms are no problem, but you don't really want to be discussing a path like that w/them. How about something in %APPDATA%\your-company-name\your-app-name ? -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Shane Courtrille Sent: Thursday, April 05, 2007 11:36 AM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] Smart Client Logging The application is running under full trust level. I like your idea of IsolatedStorage. Do you know off hand if there is a way to let the user have access to stuff from Isolated Storage? If the application is running at a certain logging level I could have the user be prompted on shutdown if they want to save the file. This assumes you can access files in IsolatedStorage and save them to the file system. In terms of the catastrophic stuff that's a really good idea. I'll start playing with that. Thanks, Shane On 4/5/07, Pardee, Roy <[EMAIL PROTECTED]> wrote: > > What kind of trust level does your app run under? That's going to > affect where you can write files I think (and probably your access to > their paths--e.g., you can create a file in IsolatedStorage under most > trust levels, but I don't think you're allowed to see where exactly > that file is stored). > > For catastrophic stuff (e.g., not-otherwise-handled exceptions), > consider putting up a web service your client can call that will stash > info in your own db & alert you as appropriate. > > HTH, > > -Roy > > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Shane > Courtrille > Sent: Thursday, April 05, 2007 10:19 AM > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Subject: [ADVANCED-DOTNET] Smart Client Logging > > I'm working on a small test smart client application. My next step is > to > try to implement logging so that if a client has a problem I can get > details on it. I'm using the log4net framework so I have a lot of > options as to how to log. My first thought is to try logging to file > and providing the user with the location of the file. > > Does anyone have any guidelines on logging from a smart client? I've > looked around for guidelines for saving files from a smart client and > haven't seen anything. > > Thanks, > > Shane > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
