-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
could not open beyond compare error while comparing folders in vs code. #27
Comments
I'm encountering an error while comparing folders in Visual Studio Code (VS Code) using Beyond Compare. When attempting to compare directories, I receive the error message "Could not open Beyond Compare". This suggests that there may be a problem with how Beyond Compare is being launched by VS Code. Steps to Reproduce: Open VS Code. |
Can you provide some more information on the environment? What operating system are you using? Does it work for file compares? How are you trying to launch the folder compare? Are the folders local? If it's relevant, we don't currently support launching folder compares of remote resources. For single file comparisons, we can just copy the contents to a temp directory and have BC compare against that, but we don't do that for entire directories. |
I just want to use that bcompare extnsion but certainly I got this error
I don't know why..
…On Tue, 23 Apr, 2024, 11:55 pm Zoë Peterson, ***@***.***> wrote:
Can you provide some more information on the environment? What operating
system are you using? Does it work for file compares? How are you trying to
launch the folder compare? Are the folders local?
If it's relevant, we don't currently support launching folder compares of
remote resources. For single file comparisons, we can just copy the
contents to a temp directory and have BC compare against that, but we don't
do that for entire directories.
—
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVZBFCALQKTF36OIZGNEEPTY62RTDAVCNFSM6AAAAABGURHD6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZTGEYDCMRUG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
see here ...
The text was updated successfully, but these errors were encountered: