Engineering
Studio
By industry · 12
Veodar
Technology · Microsoft platform
.NET is Microsoft’s platform for writing applications, and on Windows it is still the most direct way to build line-of-business programs: many screens, a lot of data, printing and integration with the rest of the office. We build new applications in .NET and modernize the ones that have been running for years, without stopping the work of the people who use them.
Often combined with
Situations
.NET pays off when the application lives on Windows, inside a company, and has to get along with what is already there: the directory, the printers, Office, the database server.
Record entry, queries, editable grids and validations. The .NET tools are made for that and give a Windows interface with no surprises.
Built years ago in Windows Forms or on a version of .NET that no longer gets patches, and the business depends on it. It is moved to the current platform in parts, with the application in use.
Printing properly, generating Excel, Word or PDF in the format the company uses and sending each document to its printer without asking.
Sign-in with company accounts, Windows services, shared folders, devices with their own drivers or old components that only exist there.
Services
Four kinds of job. The third is the most common: an application that works, on a base that has aged.
Module 1 · WindowsDesktop programs for Windows with their forms, grids, searches and permissions, connected to your database or your API.
Examples of deliverables
Module 2 · PrinterReports in the company’s format, export to Excel, Word and PDF, labels and direct printing to the right printer at each workstation.
Examples of deliverables
Module 3 · JackMoving from .NET Framework to current .NET and from old screens to a modern interface, module by module, with the application running in the meantime.
Examples of deliverables
Module 4 · Directory towerCompany accounts, Windows services, devices and old components; and, when speed is needed, a Rust library called from .NET.
Examples of deliverables
A working example
Working example with fictitious data. Change quantities and discounts in the grid: the totals are recalculated and the window marks what does not add up. Generate the report once it is correct.
| Item | Quantity | Price | Disc. % | Amount |
|---|---|---|---|---|
| Bearing 6204 | ||||
| Timing belt | ||||
| Hydraulic oil 5 l |
Order correct
Report
The report appears here once the order is correct.
The window is drawn in your browser and is not a Windows application: it imitates the behavior of a line-of-business form with its bound data. The items, the amounts and the customer are made up.
Integration
A .NET application is rarely alone in the office. It normally reads from a data server, writes documents and leans on what Windows already offers.
Where it comes from
Where it goes
How we work and what we deliver
We look at the application or the need: screens, data, reports, .NET version and which machines are on the workstations.
We write down which screens and which reports are in, in which order the old part is migrated and what is left out.
An installable version with the first screens, against a copy of your data.
The person who uses it every day tests it, at their workstation and with their printer, next to the old application.
How it is compiled, installed and updated, and what is left to migrate.
Questions
Missing yours? Write it to info@veodar.com and we'll reply with a specific question, not a brochure.
If it will only be used on Windows, is line-of-business and has many data screens, .NET is usually the most direct. If it also has to run on macOS or Linux, or reuse a web interface, Tauri fits better. We decide with the case in front of us, and sometimes they live together: interface in .NET and calculation in Rust.
Windows Forms still works and Microsoft maintains it in current .NET, so there is no urgency about the interface. What is worth doing is leaving old versions of .NET Framework and unsupported components behind. The engine can be modernized without touching the screens yet.
No. The migration is done by modules and the two versions live together on the same database while it lasts. Each part is switched once the person who uses it has tested it.
Current .NET runs on Windows, macOS and Linux, but the classic desktop interfaces are Windows only. For an application on several systems there are options inside .NET and outside it; we compare them with you.
Almost always. .NET gets along with native libraries, old Windows components, veteran databases and files in proprietary formats. What we review is whether those components still have someone maintaining them.
That part is written in Rust and called from .NET like one more library. The application keeps its screens and gains a fast engine exactly where it needs it.
Updated:
Related services
Other technologies
Get started
Knowing what it does, how many workstations use it and what it is built with is enough for a first answer.
What helps us assess it
Before you write, see how we price a project or our solutions by department.
Cookies
We store your language and this choice so the site works. With your permission, we measure visits and speed anonymously, with no tracking cookies or advertising.
Cookies
Necessary
Your language, this choice and spam protection on the contact form.
Anonymous measurement
Page views and load times, in aggregate, through Vercel. No cookies, no tracking across sites.