What we do
Tools
Industries
Department
How we workLet's talk →
Home/C# Developer for Add-ins and Windows Tools
C# Development

C# Developer Work Inside Revit, Excel and the Windows Desktop

An estimator exports a Revit schedule to Excel, retypes it into the quoting sheet, and does it all again when the model changes. The fix is a C# add-in, because Revit's API is .NET. Plenty of C# work that isn't a website looks like this: a tool inside software you already own, a desktop app on the office PCs, or a Windows service moving files with nobody logged in.

Which kind of C# job is it?

A plugin or add-in for software you already run? Revit, AutoCAD and SolidWorks publish .NET APIs, and Excel and classic Outlook still take VSTO add-ins written in C#, though Office's newer add-in model uses JavaScript. Most of the job is that product's API and its version rules.

A desktop tool on the office PCs? That's WinForms or WPF, and the hard questions are installing, updating and signing it on every machine.

Something that runs with nobody logged in? A Windows service or scheduled job, now usually built as a .NET Worker Service. If it belongs to an older web app on its own server, the .NET developer page fits better.

A Unity game or simulation? Same language, different runtime and tools. The Unity developer page covers it.

Why a C# tool that worked on one PC fails on the next

The code is rarely what fails. It's what the tool assumed about the machine, the host product or the person running it.

The host product's new release changed its .NET

How you'll know: After the yearly Revit or AutoCAD upgrade, the add-in doesn't load at all.

Fix: Autodesk moved its 2025 products from .NET Framework 4.8 to .NET 8, so older add-ins need retargeting and rebuilding. Keep one build per host version you support, and test it before the office upgrades.

The runtime isn't on the new machine

How you'll know: It runs on the laptop it was built on. On a new PC it asks to download .NET, or opens and does nothing.

Fix: Publish it self-contained so the runtime travels with the app, or install the right .NET Desktop Runtime as part of setup. Pick one and write it in the install notes.

Updates installed by walking round the office

How you'll know: Three versions of the tool are in use, and they give three slightly different numbers.

Fix: Ship it through an installer that updates itself, such as ClickOnce or MSIX, so every PC picks up the same build without anyone visiting it.

An unsigned installer

How you'll know: SmartScreen warns staff the app is from an unknown publisher, and IT blocks it.

Fix: Sign the installer and the app with a code-signing certificate your company owns, not one that belongs to whoever built it.

A service running as someone's own login

How you'll know: The overnight file job stopped the day an employee changed their password or left.

Fix: Run it under its own service account with only the folder and database rights it needs, and log each run to the Windows Event Log or a file someone reads.

Have these to hand before C# work starts

Whoever builds it will need these early. Having them ready keeps the estimate close to the real job.

  • The host product, and every version of it in use

    Revit 2024 on some desks and 2026 on others means two builds. The same goes for mixed Office versions with an Excel add-in.

  • Where the source code and signing certificate live

    If a past developer kept the repository or the certificate, updates go out under a new publisher name and staff see new warnings.

  • Who installs software on the office machines

    IT-managed PCs may block installs per user or ask for an MSI package. That changes how the tool ships.

  • What the tool reads and writes

    Shared drives, a SQL Server database, a CRM's API. Each one needs an account and permission that isn't a person's own login.

  • One example of the job done by hand

    A filled-in quote sheet, an exported file, a short screen recording. It's the test the finished tool has to pass.

Let's talk

C# tools your team installs once and forgets about

n-frames builds C# add-ins for CAD and Office products, desktop tools for the office PCs and Windows services that move data between systems, delivered with the installer, the signing and notes on what each one touches. If the job turns out to be web or cloud work, it's quoted as backend or Azure work instead.

Estimate a C# add-in or service →

C#, .NET and Unity: where the lines fall

Do you build in C# for .NET, Windows apps, and Unity, or just one?

n-frames builds business software in C#: add-ins for products with .NET APIs, Windows desktop tools and services, and the APIs and integrations behind them. Unity projects are scoped on their own, through the Unity page, because the engine changes the job even when the language stays the same.

Is this different from hiring a .NET developer?

A little. .NET work tends to mean a web app or API on the Microsoft stack, often an older one being moved forward, and the .NET page covers that. This page is the rest of C#: code that lives inside another product, on a desktop, or in a background service. The language is shared. The questions to ask aren't.

What if the C# work is really a Unity project?

Say so first, because it changes what matters: the Unity editor version, the platforms you ship to and the plugins in the project count for more than any .NET detail. Unity runs C# on its own scripting runtime, so server-side .NET experience carries over less than the shared language suggests.

Can you take over a C# add-in or desktop tool someone else built?

Yes, as long as the source still exists. We build it from source first and compare that build with the version people actually use. If only the compiled DLL survives, it can be decompiled for reading, but that's a rescue, and a rebuild should be planned.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.