Closed jplumhoff closed 2 years ago
@jplumhoff Thank you for reaching out.
As I looked over your error message, I suspected the following message as a root cause.
'protoc-gen-protolint' is not recognized as an internal or external command,
operable program or batch file.
This error is common when you don't put a binary in the appropriate path.
Did your latest protoc-gen-protolint
put in the same place as before?
I apologize for wasting your time with something so trivial! I really should have seen that error...
I was switching between versions by changing my PATH variable. Apparently I had v0.39.0 in a folder like "protolint 0.39.0", while the other versions had an underscore like "protolint_0.41.0". When I'd update my path, I missed the underscore. Once I used the correct paths, the problem was resolved. Both 0.40.0 and 0.41.0 work perfectly.
Good to hear that. No biggie 😸
A few months back, issue #264 was addressed in 0.39.0, allowing us to lint files in Visual Studio that had a protoroot folder specified. I just tried upgrading to 0.40 and then 0.41. I'm guessing there is some kind of regression... The same csproj file that works perfectly on 0.39 is failing on both 0.40 and 0.41. This is the debug output I get with version 0.40 and 0.41:
This is my csproj file: