1 2004-07-11 Gonzalo Paniagua Javier <gonzalo@ximian.com>
3 * IsolatedStorageInfo.cs: useGetFolderPath instead of getting "HOME".
5 2004-06-13 Gert Driesen <drieseng@users.sourceforge.net>
7 * IsolatedStorage.cs: really mark the storage_scope field private
9 2004-06-09 Gert Dresen <drieseng@users.sourceforge.net>
11 * IsolatedStorage.cs: use private variable for holding scope,
12 set scope in InitStore method, removed need for extra protected
13 member (public API fix)
14 * IsolatedStorageFile.cs: use InitStore to initialize scope
16 2004-05-12 Sebastien Pouliot <sebastien@ximian.com>
18 * IsolatedStorage.cs: More details on MonoTODO. Throw exceptions on
19 AssemblyIdentity and DomainIdentity properties.
20 * IsolatedStorageFile.cs: More details on MonoTODO.
21 * IsolatedStorageFileStream.cs: Removed MonoTODO on class. Now use
22 Path.Combine to build filenames (constructor) and throw an exception
23 when we try to get the handle (as documented).
25 2003-07-30 Duncan Mak <duncan@ximian.com>
27 * IsolatedStorageInfo.cs (CreateAssemblyFilename):
28 (CreateDomainFilename): Replace String.Format with Path.Combine.
30 * IsolatedStorageFile.cs:
31 (GetStore): Update storage_scope accordingly.
32 (GetUseStoreForAssembly): Include IsolatedStorageScope.User.
33 (GetUseStoreForDomain): Include IsolatedStorageScope.User and
34 IsolatedStorageScope.Assembly.
38 (MaximumSize): throw InvalidOperationExceptions. This is a
39 subclass responsibility.
40 (Scope): Implemented using a static field, storage_scope.
42 (SeparatorExternal): Implemented. Use Path.DirectorySeparatorChar
43 for SeparatorExternal.
45 2003-02-18 Jonathan Pryor <jonpryor@vt.edu>
46 * IsolatedStorageFile.cs: Fix spelling error (GetUseStoreForDomain -->
47 GetUserStoreFor Domain). Reported by
48 Torsten Rendelmann <torsten.rendelmann@procos.com>.
50 2003-01-19 Sebastien Pouliot <spouliot@videotron.ca>
52 * IsolatedStorageFile.cs: Added missing [CLSCompliant(false)]
53 to CurrentSize and MaximumSize to fix compilation (at least
56 2003-01-18 Jonathan Pryor <jonpryor@vt.edu>
58 - General: Get a simple implementation working. Simple, not-all-there, but
59 sufficient to get "Programming C#" example 21-17 working under Mono. This
60 doesn't say much, as it's not a stress-test by any means.
61 * INormalizeForIsolatedStorage.cs: re-indent to fit mono code style
62 * IsolatedStorage.cs: match mono coding guidelines
63 * IsolatedStorageFileStream.cs: Add members that "C# In A Nutshell" claims
64 the class should override. Most of these members just delegate to the
65 base class, though. CreateIsolatedPath is used to get the actual filename
66 for the IsolatedStorageFileStream.
67 * IsolatedStorageScope.cs: Documentation goes in monodoc, so there's no
68 point in having C# doc-tags. Add "Roaming" member, which "C# In A
70 * IsolatedStorageFile.cs: Public class documented in "C# In A Nutshell".
71 Simple implementation. Will probably need work to conform with .NET,
72 address security concerns.
73 * IsolatedStorageInfo.cs: Abstract IsolatedStorage information used by other
74 classes, such as the directory isolated storage is located under, how to
75 calculate the size of isolated storage, etc.
77 2002-02-19 Duncan Mak <duncan@ximian.com>
79 * IsolatedStorageFileStream.cs: Added MonoTODO here. This class
80 is completely stubbed out (over the summer) and didn't get
83 2002-02-08 Duncan Mak <duncan@ximian.com>
85 * IsolatedStorage.cs: Looked at MemberInfo.cs, another fellow
86 abstract class. Oh, that's what it means! Removed unnesscessary
89 2002-02-07 Duncan Mak <duncan@ximian.com>
91 * IsolatedStorage.cs: Added to CVS, stubbed out the API.
92 * IsolatedStorageException.cs: Implemented.
94 2002-01-07 Duco Fijma <duco@lorentz.xs4all.nl>
95 * Created INormalizeForIsolatedStorage