Time for NuGet package?
See original GitHub issueFarmer’s API seems to be quite stable and personally I don’t expect any wild changes now. Maybe we can consider convention (add_resource
vs addResource
), but if you want to keep it that way, maybe it’s good time for v1.0.0 release on NuGet?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Managing the global packages, cache, and temp folders
Packages are not expanded, and the cache has an expiration time of 30 minutes. Windows: %localappdata%\NuGet\v3-cache; Mac/Linux: ~/.local/share ...
Read more >Fetching Nuget update list takes very long time
In Visual Studio, if I right click a project and select "Manage NuGet Packages", it takes 1-2 minutes to bring up a list...
Read more >Manage NuGet packages for solution extremely slow #10674
When all is done, it again takes some 20 seconds when I select a new NuGet package to see its information. Also, switching...
Read more >Nuget restore task taking an excessive length of time
Nuget restore task taking an excessive length of timeClosed - Not a Bug ... When you took ~2 mins to restore the Nuget...
Read more >NodaTime 3.1.9
Noda Time is a date and time API acting as an alternative to the built-in DateTime/DateTimeOffset etc types in .NET.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Closing 😃
@isaacabraham Looking at nuget branch right now and looks great. Definitely better to have only subset of resource-related stuff available at one time. 👍
If you would need any help, just ping me.