this post was submitted on 09 Aug 2023
21 points (100.0% liked)

C Sharp

1526 readers
31 users here now

A community about the C# programming language

Getting started

Useful resources

IDEs and code editors

Tools

Rules

Related communities

founded 1 year ago
MODERATORS
Ategon@programming.dev
nibblebit@programming.dev
Spyros@programming.dev
21
Privacy issues with SponsorLink, starting from version 4.20 · Issue #1372 · moq/moq (github.com)
submitted 1 year ago by canpolat@programming.dev to c/csharp@programming.dev
4 comments fedilink hide all child comments
top 4 comments
sorted by: hot top controversial new old
[–] Coehl@programming.dev 12 points 1 year ago* (last edited 1 year ago) (1 children)

Summary: kzu was frustrated with funding of moq. Developed a library called sponsorlink and dogfooded it into moq with little notice.

Sponsorlink is closed source and obfuscated. While building, it takes a moment to find your GitHub info (supposedly hash it, trust me bro?) And look up your data on azure.

If you're not a sponsor, asks you to become one.

Now happens in projects with moq 4.20+.

I probably don't have to explain more than that. Huge GDPR issues.

[–] RubberDucky@programming.dev 9 points 1 year ago* (last edited 1 year ago)

Also saw in the dotnet discord that builds take ±1680ms longer (for tests of course) Screenshot

[–] canpolat@programming.dev 10 points 1 year ago (1 children)

I think the developer basically killed the project. I'm not sure Moq can recover from this. I recommend everyone to move to NSubstitute as soon as possible. I suspect most of the migration can be done via Find/Replace.