Upgrade project files to SDK-style format compatible with dotnet
@adecler is already working on this.
Since Feb 17, 2026.
Assessment
This issue has not been assessed yet.
Description
Broken rules:
The project files were still using the legacy .NET Framework project files and needed to be upgraded to SDK-style format compatible with dotnet.
- Dominant language
- C#
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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.
More from BHoM/HTTP_Toolkit
-
type:feature
BHoM/HTTP_Toolkit#134 · 1 comment · 1 assignee ·
-
type:bug
BHoM/HTTP_Toolkit#72 · 1 assignee ·
-
type:feature
BHoM/HTTP_Toolkit#52 · 1 comment · 2 assignees ·
-
severity:low type:compliance type:question
Difficulty 5/5 Over a week Newbie friendliness 20/100
BHoM/HTTP_Toolkit#20 · 5 comments · 1 reaction ·
-
The number of responses resulting in the Pull is not of the expected length when using BatchRequest Opentype:bug
BHoM/HTTP_Toolkit#13 · 2 comments · 1 assignee ·
All issues in BHoM/HTTP_Toolkit
Similar issues
-
core dependencies
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
bug frontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
NavigationViewItemAutomationPeer implements IInvokeProvider but never advertises the Invoke pattern Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
unoplatform/uno#24629 ·
-
agentic-workflows Needs: Triage :mag: State: In-PR
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Down / Waiting for removal
Difficulty 2/5 1-3 hours Newbie friendliness 70/100