deramor
04-18-2013, 04:23 PM
Hello. Sometimes during builds, they fail. Suppose the build fails on a step that contains a file path. An example of this would be a Visual Studio step. Often times, in order to fix the errant code, the solution would need to be opened. It would be helpful if the step included a button or some other way to open an explorer window to the file defined in the step.
In some instances, these files are defined by a fully written out path. This would let me copy the path and quickly get there. However for build systems that include macros in the path, those macros may have correct definitions however only VBP understands them. Windows will not which makes navigating to a file more manual.
My particular use includes files that can be many levels deep into a folder structure. It is more a convenience then anything but that is how new features get added :)
Thanks,
Rob
In some instances, these files are defined by a fully written out path. This would let me copy the path and quickly get there. However for build systems that include macros in the path, those macros may have correct definitions however only VBP understands them. Windows will not which makes navigating to a file more manual.
My particular use includes files that can be many levels deep into a folder structure. It is more a convenience then anything but that is how new features get added :)
Thanks,
Rob