We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Run the following powershell command
&"C:\Program Files (x86)\Telerik\JustAssembly\Libraries\JustAssembly.CommandLineTool.exe" "E:\git\compare\current\content\lib\ikvm\JVM.DLL" "E:\git\compare\server\content\lib\ikvm\JVM.DLL" "JVM.DLLJVM.DLL.xml"
Assembly comparison should execute and succeed
Error with message First assembly path is in incorrect format or file not found. Exit code: 1
lower casing the file extensions for both inputs worked well
&"C:\Program Files (x86)\Telerik\JustAssembly\Libraries\JustAssembly.CommandLineTool.exe" "E:\git\compare\current\content\lib\ikvm\JVM.dll" "E:\git\compare\server\content\lib\ikvm\JVM.dll" "JVM.DLLJVM.DLL.xml"
This class: https://github.com/telerik/JustAssembly/blob/master/UI/JustAssembly.CommandLineTool/FilePathValidater.cs#L30
should be validating the input file extensions regardless their casing. at the moment, only lowercase "dll" or "exe" are valid inputs
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Steps to reproduce it
Run the following powershell command
Expected Result
Assembly comparison should execute and succeed
Actual Result
Error with message
First assembly path is in incorrect format or file not found.
Exit code: 1
workaround:
lower casing the file extensions for both inputs worked well
Possible cause:
This class:
https://github.com/telerik/JustAssembly/blob/master/UI/JustAssembly.CommandLineTool/FilePathValidater.cs#L30
should be validating the input file extensions regardless their casing. at the moment, only lowercase "dll" or "exe" are valid inputs
The text was updated successfully, but these errors were encountered: