[Mono-bugs] [Bug 500200] New: System.IO.DirecotryNotFoundException when trying to run BlogEngine.NET remotely

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Fri May 1 16:39:20 EDT 2009


           Summary: System.IO.DirecotryNotFoundException when trying to
                    run BlogEngine.NET remotely
    Classification: Mono
           Product: Mono: Tools
           Version: unspecified
          Platform: x86-64
        OS/Version: Windows XP
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Visual Studio Integration
        AssignedTo: jpobst at novell.com
        ReportedBy: mchristensen at novell.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: Component Test

Description of Problem:

Windows XP x86_64
MonoVS plugin r1829
Opensuse 11.1 x86_64

Fist off, running a simiple WinForms app remotely works fine.

BlogEngine.NET runs fine locally on WindowsXP in Mono however, when trying to
run remotely, the status bar indicates that MonoVS is setting up a connection
with the server and then a dialog with the following error is displayed:

System.IO.DirectoryNotFoundException: Could not find a part of the path
'C:\Documents and Settings\rupert\Desktop\BlogEngine.NET_1.5_source\Bin'.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.Directory.InternalGetFileDirectoryNames(String path, String
userPathOriginal, String searchPattern, Boolean includeFiles, Boolean
includeDirs, SearchOption searchOption)
   at System.IO.Directory.GetFiles(String path, String searchPattern,
SearchOption searchOption)
   at Novell.MonoVS.Utilities.GetFilesToCopy(String path)
   at Novell.MonoVS.BaseRunner.PrepareSession(Solution solution, SessionType
   at Novell.MonoVS.RunRemotelyRunner.Run()
   at Novell.MonoVS.Package.RunRemotelyCallback(Object sender, EventArgs e)

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

More information about the mono-bugs mailing list