[Mono-bugs] [Bug 537947] New: Environment.SpecialFolders.MyDocuments points to the wrong path

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Wed Sep 9 22:36:21 EDT 2009


http://bugzilla.novell.com/show_bug.cgi?id=537947


           Summary: Environment.SpecialFolders.MyDocuments points to the
                    wrong path
    Classification: Mono
           Product: MonoTouch
           Version: unspecified
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Runtime
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: fak at kruegersystems.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


Created an attachment (id=317521)
 --> (http://bugzilla.novell.com/attachment.cgi?id=317521)
Two projects demonstrating the difference

Description of Problem:

The documents folder retrieved in Cocoa does not match the folder returned by
Environment.GetFolderPath(Environment.SpecialFolders.MyDocuments) points to a
different path than NSSearchPathForDirectoriesInDomains(NSDocumentDirectory,
NSUserDomainMask, YES)).

This is important because the "Documents" folder is some how (magically)
preserved between Simulation executions while none of the other folders are.
It's the place where the app is supposed to write its preserved data.

Steps to reproduce the problem:
1. Compile Xcode project - note path
2. Compile Mono project - note path


Actual Results:

Xcode
====
/Users/fak/Library/Application Support/iPhone
Simulator/User/Applications/4181F9C2-1102-48D7-BB5E-349770A1E787/Documents/hello
! Couldn't read
Wrote

MonoTouch
====
/Users/fak/Library/Application Support/iPhone
Simulator/User/Applications/BE47D555-33E7-4964-8ED1-B4CACDDB499D/hello
! Couldn't read
Write



Expected Results:

-- You get the idea

How often does this happen? 


Additional Information:

-- 
Configure bugmail: http://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