mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,5 Tsd.
aktive Profile

#nuget

4 Beiträge4 Beteiligte0 Beiträge heute

I'm working with a team that does not like #dotnet #nuget packages.

They would prefer nothing, but if forced into reusable modules they would choose git submodules first.

This is surprising to me, but one of the reasons listed holds weight: with git submodules you can hack, modify, and change the modular code inline. No review, build, & publish pipeline to try out a idea.

I am trying to deduplicate a lot of copy and paste "mostly the same" code, and firm up the abstractions and interfaces of these modules (there's a rant in there for a different time)

I'd like some more opinions on the nuget vs git submodule topic. Git intuitively seems like the wrong package management tool to me, but I don't know if I'm holding on out of stubbornness or if there is something on the tip of my tongue I just can't articulate yet.

I'm fairly new to open source #dotnet #nuget package coding and I've just released v1.0.0 of my package, however I've just discovered a good way to move the package forward, that will lead to a breaking change. Do you find it problematic to release a v2.0.0 aprox. two months after v1.0.0 with no version inbetween? (If anyone wants to take a look at the project: signalrgen.net - still WIP)

signalrgen.netSignalRGenA dev-friendly experience to SignalR communication