dotnet support for SLNX format
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 107
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 5
Description
As a developer of modern dotnet applications and solutions, I would like frogbot to support the SLNX format.
Without proper support, frogbot think there are no solution files in my repo. I get issues like this:
15:54:31 [Info] Calculating NuGet dependencies...
15:54:31 [Warn] expecting 1 'proj' file but fuond 0 files in path: C:\Users\ContainerAdministrator\AppData\Local\Temp\jfrog.cli.temp.-1767992070-2575979220
As soon I revert back to the legacy SLN format, everything works perfectly again.
I tried many variations related to restore, but none worked. Fundamentally it seems to think there is no project or solution to restore or something.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported dependency-restore failure with a repository that uses an SLNX solution file, then trace how frogbot discovers and restores .NET solution and project files. Done means SLNX-based repositories are detected and their NuGet dependencies are scanned without requiring the legacy SLN format.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100