Closed anektar closed 8 months ago
looking at the file name it's probably a length issue of the path but it's weird that it works from VStudio O_o, you should try to change the FileNameFactory
and see if it works with one that produce shorter name.
Good morning, thanks for the quick response!
Regarding my second issue I used your configuration json and after setting all needed, including FileNameFactory, the documentation CLI worked.
Regarding my first issue, I was too very puzzled why it would work with no issue from V Studio during build but not from CI. Turns out in our CI the build task built every project with a wildcard. This might have resulted in building projects with dependencies in not the right order. So instead I changed the ci to build the actual .sln the same that's being built from the Visual Studio. And the problem is gone. Nothing to do with your library. :)
Thanks a lot for your input!
Hello,
we've been trying out your very helpful tool. When working from the .csproj all work fine while building from VStudio. When the same runs from a CI we get this error:
I have tried running from the CLI tool for a single dll:
Any thoughts/help on this?