[Mono-bugs] [Bug 354539] New: IsolatedStorageFile. GetStore throws exception when evidence arguments are null

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Thu Jan 17 13:59:27 EST 2008


https://bugzilla.novell.com/show_bug.cgi?id=354539


           Summary: IsolatedStorageFile.GetStore throws exception when
                    evidence arguments are null
           Product: Mono: Class Libraries
           Version: 1.2.4
          Platform: x86
        OS/Version: Kubuntu
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: CORLIB
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: gavin at hexillion.com
         QAContact: mono-bugs at lists.ximian.com
                CC: gavin at hexillion.com
          Found By: Third Party Developer/Partner


Created an attachment (id=190910)
 --> (https://bugzilla.novell.com/attachment.cgi?id=190910)
Test case

According to the Microsoft docs...
http://msdn2.microsoft.com/en-us/library/system.io.isolatedstorage.isolatedstoragefile.getuserstoreforassembly.aspx

the following two lines should be equivalent:
IsolatedStorageFile.GetStore(IsolatedStorageScope.Assembly |
IsolatedStorageScope.User, null, null);

IsolatedStorageFile.GetUserStoreForAssembly();

On Mono, however, the GetStore line results in this:
Unhandled Exception: System.IO.IsolatedStorage.IsolatedStorageException: No
code identity available.
  at System.IO.IsolatedStorage.IsolatedStorageFile.PostInit () [0x00000] 
  at (wrapper remoting-invoke-with-check)
System.IO.IsolatedStorage.IsolatedStorageFile:PostInit ()
  at System.IO.IsolatedStorage.IsolatedStorageFile.GetStore
(IsolatedStorageScope scope, System.Type domainEvidenceType, System.Type
assemblyEvidenceType) [0x00000]

GetUserStoreForAssembly seems to work fine. 

The attached test case outputs "Hello" on Windows .NET 1.1 but throws the above
exception on Mono 1.2.4 on Kubuntu.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the mono-bugs mailing list