No hooks logs in Visual Studio with Husky.Net

[NilkOne]

Version

0.5.1

Details

In Visual Studio Enterprise 2022 (64 bits) - Preview Version 17.3.0 Preview 6.0,
I can't view hook error logs.

I can view an error message "One or more errors occurs" but no details when comiting.
No more details in Output window (Git source control section).

I can view logs only if I run a git command line in dos/powershell.

(if I copy the hook directly in Git Hooks folder, that work and I can see error message in VS window)

Any solutions ?

Steps to reproduce

• open a VS solution with git hooks
• try a bad commit
• no more information about errors

[alirezanet]

Hi @NilkOne,

First of all, I don't have this problem in Visual Studio 2022 v17.0.6. for me, it shows the error message directly!

maybe if update your visual studio it will fix.

second, if the visual studio doesn't provide any way to check git error messages I can not do much about that in husky.

[NilkOne]

Thanks for your rapid answer

Can you share your hooks please ?

[alirezanet]

Can you share your hooks please ?

I've tested this problem with the current husky repo.

[alirezanet]

I moved this issue to discussions, feel free to ask any question if you couldn't manage to solve the problem.

[NilkOne]

thanks @alirezanet

[alirezanet]

I've tested this on my laptop and also updated my visual studio to 17.3.0 but still, I'm getting the error messages! could be related to your visual studio language, can you try to use English?

[NilkOne]

Hello,
I tried with English language in 17.3.0 version on Windows 10 : same problem
Do you test on a clean clone folder of the project ?

Because when I clone the project, I need to install Husky otherwise I can commit with 'test' commit message.

I tested all logging verbosity but nothing change

[alirezanet]

Yes, after cloning the project you either must install the husky manually or build and restore the project (it will automatically install the husky).
I'm still looking for a way to simulate the problem and hopefully find a solution for you.

[NilkOne]

OK thanks