What we review
Dot Net Masters reviews developer tools, IDEs and editors, code-analysis and profiling utilities, hosting and deployment platforms, libraries and packages, technical books and courses, conferences, and learning resources relevant to the .NET and Microsoft developer ecosystem.
How a review gets started
We choose what to review. Vendors do not pitch us into reviewing their product, and we do not accept "review packages" or pre-written copy. A review begins when an editor or contributor decides a tool is worth a serious look — usually because we already use it, are evaluating it for our own work, or readers have asked about it.
Independence
We are editorially and financially independent of every product we review. Specifically:
- No affiliate links. If we link to a product, we do not earn a commission when you click or buy.
- No sponsorship of reviews. Vendors cannot pay to be reviewed, to be reviewed favourably, or to be reviewed sooner.
- No exchange for free licenses. When we review a paid product, we either purchase it ourselves or use a vendor-provided trial. Receiving a free license never obligates us to publish a positive review — or to publish anything at all.
- No vendor approval before publication. Vendors do not see, edit, or pre-approve a review before it goes live. They can respond after publication, and we'll consider corrections of factual errors.
- No advertising influence. Dot Net Masters does not currently run paid advertising. If that ever changes, advertisers will have no editorial influence — and we'll update this page accordingly.
How we test
For tools and libraries, we use the product on real work for at least a week before writing about it. For larger platforms (hosting providers, IDEs, profilers), the test period is longer — often a full project lifecycle. For books and courses, we read or complete the material end-to-end. We disclose how long we used a product and what we used it for in every review.
Disclosures
Where a contributor has any relationship with the vendor of a reviewed product — current or former employment, consulting, advising, friendship with a senior employee, or any kind of equity stake — that relationship is disclosed inline at the bottom of the article. If a relationship is severe enough that a fair review is not possible, we assign the review to a different writer.
Updates & revisions
Software changes. A negative review of a tool that has since improved its problem area is noted with a follow-up — sometimes a fresh review, sometimes an addendum. We never silently flip a review's verdict without a clear update note.
Questions about a review
If you believe a review on Dot Net Masters contains a factual error, missing context, or undisclosed conflict of interest, please tell us via the Contact page. Substantive complaints are reviewed by a member of the editorial team within three business days.