|
akadajet posted:here's a nuget of wisdom: running a local nuget repo sucks idk i found it to be insanely easy, but also you should be using your azure devops repo instead. nuget sucks for a bunch of reasons tho. it allows for scripting that runs when packages are added or removed which is just stupid. the reason this was done is also stupid: msbuild sucks poo poo. it doesnt have good extensibility, so everything must be managed through procedural build steps in your project file. many nuget scripts modify your config file to add build steps. this causes all the problems you think it would since theres no guarantee the project file is in a state appropriate for the scripts to run and the scripts cant possibly handle every edge case. likewise when you remove these packages they will often try to remove the poo poo they did to your project file which will almost always break something. the way nuget handles symbols is loving stupid. you can have nuget create symbol packages, but visual studio cant use them. Symbol packages are intended to be loaded to a symbol server and then visual studio connects to that. Symbol servers are an archaic and stupid concept where you have symbols stored somewhere on the network and when you need them visual studio tries to find them on the server. servers are configured at the user level, not at the project or solution level. this means any time you try to search for symbols in any project ever it searches all your symbol servers. So all the slowness of network processing is compounded by the number of servers you have. The alternative to this would be to just to throw the symbol server feature in the dumpster where it belongs and instead download the nuget symbol package (if it exists) for the specific package you're using and then use those symbols locally. or just switch to using source packages like maven does which works way way way better.
|
#
¿
Dec 29, 2021 20:06
|
|
|
|
| # ¿ May 14, 2024 22:20 |
|
|
these days people dont use the scripting stuff, but the symbols are still a pain in the dick
|
|
#
¿
Dec 29, 2021 20:15
|
|
|
the scripting issues are also not really nuget's fault, as they were always hacks for failings in msbuild. msbuild should have been relegated to legacy languages and dumpstered for a maven clone.
|
|
#
¿
Dec 29, 2021 20:17
|
|
|
Canine Blues Arooo posted:nuget is pretty good. setting up your own nuget infrastructure is...fine. C# is the lord's language. unfortunately, no package manager is going to stop you from downloading bad software hth C# is great and its the best for web poo poo, but msbuild/nuget is absolutely awful when you contrast it with maven.
|
|
#
¿
Dec 30, 2021 21:22
|
|
|
tbh its wierd to me that anyone ever used log4j 2.0 at all. its litterrally a clone of slf4j but it came out years after slf4j so i'd think most people are either still using 1.2 or migrated to slf4j. who starts a new project with log4j 2.0? ive been out of the java world for years now, tho, so idk.
|
|
#
¿
Dec 31, 2021 21:33
|
|