Skip to content
  • Sponsor
  • Notifications You must be signed in to change notification settings
  • Fork 0

Commit d68a0de

Browse files
authoredMay 23, 2020
Update README.md (#3)
1 parent cc56f3f commit d68a0de

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed
 

‎README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# sprintf.NET ![.NET Core](https://github.com/adamhewitt627/sprintf.NET/workflows/.NET%20Core/badge.svg?branch=master) [![NuGet Status](http://img.shields.io/nuget/v/sprintf.NET.svg?style=flat)](https://www.nuget.org/packages/sprintf.NET/)
1+
# sprintf.NET ![Continuous](https://github.com/adamhewitt627/sprintf.NET/workflows/Continuous/badge.svg) [![NuGet Status](http://img.shields.io/nuget/v/sprintf.NET.svg?style=flat)](https://www.nuget.org/packages/sprintf.NET/)
22
For many reasons, a .NET developer *should* use [composite formatting](https://docs.microsoft.com/en-us/dotnet/standard/base-types/composite-formatting). (Culture-specific, no P/Invoke cost, string interpolation, etc) However, sometimes it is desirable to have a C-style format string, as when sharing localization strings across platforms.
33

44
P/Invoke to `swprintf` is generally sufficient, but:

0 commit comments

Comments
 (0)
Please sign in to comment.