Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
I hope one day Microsoft will deprecate their non-unicode API, remove that TCHAR mess. I think they supported these legacy APIs long ey already. There's still a problem with PATH_MAX, see, for example, the dotnet MSBuild[1]. Maybe even switch to the UTF-8 instead.
[1] https://github.com/dotnet/msbuild/issues/53
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a more popular project.
Related posts
- Why does Microsoft still insist on using XML for configuration files like `.csproj`, etc.?
- [Copilot has] been a massive productivity improvement to our senior devs, and I got so used to it that it's an annoyance when Copilot doesn't respond.
- Build to order? Checking MSBuild for the second time
- Gauging broader interest in a .sln file generator based on a new DSL?
- New format for solution (.sln) files