For .NET teams with shared code

Custom NuGet Package Development

Turn duplicated .NET code into versioned, documented NuGet packages — published to nuget.org or your private feed.

Book a Free Call

YourCompany.Shared — release

$ dotnet test

Passed! Failed: 0, Passed: 148, Skipped: 0

$ dotnet pack -c Release

Successfully created package 'YourCompany.Shared.2.1.0.nupkg'.

$ dotnet nuget push *.nupkg --source company-feed

Your package was pushed.

$ dotnet add package YourCompany.Shared

PackageReference for 'YourCompany.Shared' version '2.1.0' added.

Public NuGet packages: 6
Package downloads: 1,500+
Multi-targeted builds: .NET 6–8

Service Overview

I package your shared .NET code — helpers, API clients, domain logic, validation rules, UI components — into clean, versioned NuGet libraries that every team installs with one command. As the author of six public NuGet packages with more than 1,500 downloads, I handle the whole lifecycle: API design, multi-targeting, Semantic Versioning, README and XML docs, automated tests, and CI pipelines that publish to nuget.org, Azure Artifacts or GitHub Packages.

Every package is built to the standards public libraries are held to. Projects multi-target the frameworks your apps actually run (for example .NET 8, .NET 6 and .NET Standard 2.0), builds are deterministic, and SourceLink plus symbol packages let developers step into the library while debugging. The public API is kept small and intentional, breaking changes only ship in major versions, and every release comes with notes. Central Package Management, analyzers and a test suite run in CI, so a version is published only when the build is green — straight to your private feed or nuget.org.

What's Included

Library API design and refactoring of shared code
Multi-targeting: .NET 8, .NET 6 and .NET Standard 2.0
Semantic Versioning with release notes
Private feeds: Azure Artifacts, GitHub Packages or nuget.org
CI/CD publishing with GitHub Actions or Azure DevOps
README, XML docs, SourceLink and symbol packages

Technologies Used

C#.NETNuGetGitHub ActionsAzure DevOpsxUnit

How I Deliver

Code review & package boundaries
Review the shared code across your repos, decide what belongs in which package and agree the public API.
Refactor into a library
Extract the code, remove app-specific dependencies, add multi-targeting and keep behaviour identical.
Tests, docs and versioning
Add unit tests, XML docs and a README with examples; set the version and changelog conventions.
CI publishing
Pipelines build, test, pack and push to your feed on every tagged release, with SourceLink and symbols.
Adopt and hand over
Switch your apps to the package, remove the copies, and walk your team through releasing new versions.

Why It Matters

Fix once, ship everywhere

A bug fixed in the package reaches every app with a version bump — no hunting through copied folders.

Safe upgrades

Semantic Versioning and release notes tell teams exactly what changed and whether an update can break them.

Faster onboarding

New projects get your proven building blocks with one dotnet add package command and readable docs.

Private by default

Internal packages live on your own feed with your access rules; nothing is published publicly unless you want it.

What You Get

Production-ready NuGet package(s) with source code
Unit test suite and CI pipeline that publishes on release
README with install and usage examples, XML docs
Versioning and release guide for your team
Your apps migrated from copied code to the package

Who It's For

Teams copying the same helpers or clients between repositories
Companies with several .NET apps sharing domain logic
Product teams who want to publish an SDK for their API
Open-source authors who need a professional release setup

Contact Me Book a Call

Custom NuGet Package Development — Muhammad Rehman Tahir

Core ServiceAvailable

Have Questions?

Happy to answer any questions before you commit.

Ask a Question

Why teams package their code

Shared code that lives in copied folders drifts apart. A package gives it one home, one version history and one place to fix bugs.

One source of truth

Every app references the same versioned library instead of its own slightly different copy.

Versioned releases

SemVer and release notes make every upgrade a deliberate, reviewable step.

Private feeds

Azure Artifacts or GitHub Packages with your organisation's access rules.

Docs developers read

README examples, XML docs in IntelliSense and SourceLink for debugging.

Publishing on autopilot

Tag a release and CI builds, tests, packs and pushes the package for you.

Copied code vs a NuGet package

Topic	Copy-paste / shared folder	Internal NuGet package
Fixing a bug	Patch every repository by hand	Release a new version, apps update
Knowing what changed	No history per copy	Semantic Versioning and release notes
Breaking changes	Found in production	Only in major versions, flagged up front
New projects	Find and copy the right folder	dotnet add package
Testing	Different in every copy	One test suite, gated in CI

FAQ

Custom NuGet Package Development — FAQs

It depends on how much code is involved and how many apps will use it. A focused library (a client, a set of helpers) usually takes a few days; a larger shared framework takes a few weeks. After a free review call I give a fixed quote, so you know the cost up front.

Yes. Most of my package work is published to private feeds such as Azure Artifacts or GitHub Packages, with access limited to your organisation. Publishing to nuget.org is only done if you want the package to be public.

The package can multi-target, for example .NET 8, .NET 6 and .NET Standard 2.0, so newer and older apps can use the same version. We pick targets based on what your applications run today.

No. The code is extracted with its behaviour unchanged and covered by tests first. Apps then switch from the copied code to the package one at a time, so each change is small and easy to verify.

You do. All source code, the package IDs and the pipelines belong to your company, and the full intellectual property is transferred to you.

Yes, if you want. I can handle new versions, .NET upgrades and fixes on an ongoing basis, or hand over a documented release process so your team can do it.

What I Do

My Services

End-to-end software solutions tailored to your business needs.

Hire a Remote .NET Developer
A dedicated ASP.NET Core developer who works your hours — hourly, monthly or fixed-scope, with clear weekly reporting.
C#ASP.NET CoreEntity FrameworkSQL ServerReactAzure
Details about Hire a Remote .NET Developer
.NET Framework to .NET 8 Migration
Move .NET Framework 4.x applications to modern .NET step by step — faster, cross-platform and supported again.
.NETASP.NET CoreEntity FrameworkC#SQL ServerAzure
Details about .NET Framework to .NET 8 Migration
Full-Stack Web Development
Your complete website or web app — designed, built, launched and supported by one dedicated developer.
React.jsAngularASP.NET CoreAzureSQL Server
Details about Full-Stack Web Development
Custom Solution Implementation
Software built around the way your business actually works — not the other way around.
C#.NETASP.NET CoreEntity FrameworkSQL ServerAzure
Details about Custom Solution Implementation
ASP.NET Core Development
Robust, scalable web applications and APIs using ASP.NET Core with clean architecture principles.
C#ASP.NET CoreEntity FrameworkSQL ServerAzure
Details about ASP.NET Core Development
Database Design & Optimization
Efficient, normalized databases with optimized queries for maximum performance and scalability.
SQL ServerPostgreSQLMySQLSQLiteEntity Framework Core
Details about Database Design & Optimization
Payment Gateway Integration
Secure Stripe, PayPal and custom wallet integrations with reliable checkout and transaction workflows.
StripePayPalASP.NET CoreC#Webhooks
Details about Payment Gateway Integration
Desktop Application Development
Feature-rich Windows desktop applications using WPF and WinForms with professional UIs.
WPFWinFormsC#.NETSQL Server
Details about Desktop Application Development
API Integration & Consulting
Third-party API integrations and hands-on consulting for complex system architectures.
ASP.NET Core Web APIRESTJSONPostmanAzure
Details about API Integration & Consulting
Quality Assurance & Testing
Comprehensive manual and automated testing to ensure your software is reliable, stable, and bug-free.
SeleniumCypressxUnitPostmanPlaywright
Details about Quality Assurance & Testing
Complete Web Auditing
Full website audit covering SEO, AEO, overall visibility, UX, performance, and technical health.
LighthouseGoogle Search ConsoleAnalyticsPageSpeed InsightsSchema.org
Details about Complete Web Auditing