Bug 13079 - "Open Containing Folder" always throws an error
Summary: "Open Containing Folder" always throws an error
Status: VERIFIED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.0.9
Hardware: PC Windows
: --- normal
Target Milestone: master
Assignee: Bugzilla
URL:
: 19797 ()
Depends on:
Blocks:
 
Reported: 2013-07-06 16:06 UTC by eduard.qualls
Modified: 2014-05-15 14:34 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
VERIFIED FIXED

Description eduard.qualls 2013-07-06 16:06:17 UTC
Within any project, select "Open Containing Folder" option for any file listed in the Solution explorer.

"An error has occurred"
"Error while executing command: Open Containing Folder"

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ComponentModel.Win32Exception: The system cannot find the file specified
   at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start(String fileName)
   at MonoDevelop.Ide.Desktop.PlatformService.OpenFolder(FilePath folderPath)
   at MonoDevelop.Ide.DesktopService.OpenFolder(FilePath folderPath)
   at MonoDevelop.Ide.Gui.Pads.ProjectPad.FileOperationsCommandHandler.OnOpenFolder()
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters)
   at MonoDevelop.Components.Commands.DefaultCommandHandler.Run(Object target, Command cmd)
   at MonoDevelop.Components.Commands.CustomCommandTargetAttribute.Run(Object target, Command cmd)
   at MonoDevelop.Ide.Gui.Components.NodeCommandHandler.TransactedNodeHandlerAttribute.Run(Object target, Command cmd)
   at MonoDevelop.Components.Commands.CustomCommandTargetAttribute.MonoDevelop.Components.Commands.ICommandTargetHandler.Run(Object target, Command cmd)
   at MonoDevelop.Components.Commands.CommandHandlerInfo.Run(Object cmdTarget, Command cmd)
   at MonoDevelop.Components.Commands.CommandManager.<>c__DisplayClassb.<DispatchCommand>b__2()
   at MonoDevelop.Components.Commands.CommandManager.DispatchCommand(Object commandId, Object dataItem, Object initialTarget, CommandSource source)

The directory tree for the file in question when this trace was made is "c:\Prog\C#\MonodroidSamples\monodroid-samples-master\CalendardDemo\CalendarListActivity.cs".

Is it possible that the code in question does not support Windows/NTFS file names fully? (I.e., is a failure to handle the [perfectly 'legal'] "#" in the path making it fail?) {Surely it wouldn't be path length...}
Comment 1 eduard.qualls 2013-07-23 10:34:33 UTC
This exception is not thrown when the path is something "vanilla", like "c:\Xamarin\MonodroidSamples\monodroid-samples-master".

There appear to be multiple little instances where the file-system code inside XS makes filename assumptions that are not coherent. [Case changes in filenames can cause trouble for the code that generates Resource.designer.cs, particularly as it refuses to accept case-changes from project/solution renaming (solely involving case change) done within the XS solution explorer pane.]
Comment 2 Roy Deistung 2014-03-04 10:26:32 UTC
bug still persists in 4.2.3 :(
Comment 3 Mikayla Hutchinson [MSFT] 2014-03-04 18:54:00 UTC
Fixed in master.
Comment 4 Danish Akhtar 2014-03-26 07:59:41 UTC
I have checked this issue with:

XS 4.2.4(build 266)- 57fa6b7639703775ae1d5c46536e42ab424cb177
X.Android 4.13.00004
Win 8

Now this issue is not exist, we are successfully able to open 'Containing Folder' in XS without any error.

Hence marking this as Verified Fixed.
Comment 5 Mikayla Hutchinson [MSFT] 2014-05-15 14:34:38 UTC
*** Bug 19797 has been marked as a duplicate of this bug. ***