.NET Development Services

Frequently Asked Questions

• Is .NET a worthwhile platform to build on in 2027?
  Certainly, .NET is one of the most successful enterprise platforms, and Microsoft does invest in it, which ranges from .NET Core to Azure integration. This is a fantastic platform to use for building, not only maintenance. Our specialists keep abreast of yearly releases since a technology that was revolutionary two years ago becomes obsolete if there is no constant monitoring of releases. NET today won’t leave you stuck with outdated tooling in three years. For most business software, internal tools and customer-facing platforms alike, it’s a safe, well-supported choice.

• Is .NET a good fit for a cloud-based application?
  Yes, very likely, especially better than many developers would think. The cloud-first approach of .NET Core is what makes it well-suited to build a cloud application and not merely an adaptation of an existing app for cloud deployment.
  
  The native support of Microsoft Azure is what leads to fewer difficulties in deployment, monitoring, and scalability, in comparison to forcing a cloud approach into an existing stack. Everything that relates to containers, orchestration, and managed services works perfectly fine right out of the box with .NET, so there is no need to develop workarounds for something that is supposed to be part of cloud technology.

• How does .NET handle microservices architecture?
  .NET Core framework is excellent for developing microservices because of its modularity as well as support for Docker and Kubernetes without additional changes. Each microservice is independently developed, deployed, and scaled. This is important as, at times, a certain part of the system may require more resources than other parts. It is also important for ensuring that an issue in one of the microservices will not affect the operation of all others.

• How much does .NET development cost?
  The cost of .NET development depends on the scope, composition of the team, and delivery model. Staff augmentation is charged per hour according to the level of developers involved, whereas the cost of full team or full outsourcing delivery models is usually charged either time-and-materials or fixed price depending on how detailed the requirement is at the beginning.
  
  A small internal tool is far less expensive than a multitenant SaaS solution with billing and compliance capabilities. We give a scoped estimate after a discovery call rather than a generic range that doesn’t reflect your actual development process, industry, or team size needs.

• How long does a typical .NET build take?
  The timeframe varies based on the scale of your .NET development project. The MVP goes from initiation to release within a couple of months through incremental sprints. The modernization or migration of enterprises is a lengthy process that involves multiple stages in the roadmap. We provide you with an exact timeframe after the completion of the discovery phase.

• Do you work with .NET Framework or only .NET Core?
  Both. A considerable amount of our .NET migrations include moving away from .NET Framework and moving to newer versions. However, we also develop and support Framework-based solutions if migration makes no sense in that particular case.
  
  There might be some dependencies, internal integrations, or other valid reasons to continue working on Framework for a certain period of time, and we will inform you about this honestly without recommending a migration if it’s not necessary. We can tell you which case applies to you after analyzing your actual codebase.

• What’s the difference between .NET Framework and .NET Core?
  The first version of Microsoft’s framework was the .NET Framework, developed exclusively for the Windows operating system. The second generation is known as .NET Core and was introduced in 2014. Microsoft merged .NET Framework and .NET Core into a single .NET environment starting with .NET Core is the recommended platform for further development because of its cloud-first approach. In general, developers use .NET Core or .NET, depending on the release; in either case, there is no need to keep the framework version. This applies especially to new projects.

• Can you migrate our existing applications to Azure?
  Absolutely. Our migration services are designed to move on-premises .NET applications to Azure, which includes database migration, containerization wherever appropriate, and the creation of CI/CD pipelines for subsequent app versions, so future releases don’t require the same manual lift the migration did.
  
  Migration is done in phases, not scheduled on a cut-over weekend in the hopes that nothing will break. This phased approach allows time for problems to be discovered before they become a production problem. Most migrations have an initial phase where we identify what’s safe to move and what needs rework.

• Who manages the project, you or us?
  That all comes down to how we engage. Being a software development company designed to take projects from concept to completion, we default to full outsourcing, so our PMs are responsible for delivering everything.
  
  Team or staff augmentation can work both ways — either our PM manages your team or your PM manages ours. While some of our clients prefer to hand over full ownership so they can concentrate elsewhere, others are interested in seeing each sprint being done. Either way works fine for us.

• Can our team continue to maintain the application once you’ve finished?
  Yes, definitely. Our company always provides technical documentation, installation guidelines, and a knowledge transfer to your in-house team, if you have one. Should you still need to build an in-house team, we will provide our support services until then.
  
  The documentation is prepared not for us but for people who will be using this system further. And the transfer of knowledge is crucial, because many issues we are asked to deal with are caused by a poorly documented system.

• Do you build integrations with tools like Salesforce, SAP, or Yardi?
  Yes, integrating is a normal process for us. We have already developed our own integration layer, which allows us to connect .NET applications with different CRMs, ERPs, and specialized software within the scope of development solutions where standard connectors do not satisfy the needs of our clients. The integration with Yardi, for example, is quite popular in our real estate projects because we often encounter the necessity to implement custom logic in property management systems.

• Can you integrate with our existing in-house development team?
  Absolutely. This is the whole point of staff augmentation and the dedicated team model. We integrate into your current processes and work environment instead of trying to change you to our own. We participate in your sprint planning, work within your ticketing system, and report to whoever is managing your team instead of establishing a new process only we know. It makes sense to use this solution in case your team already has some structure but just needs some additional hands or skills.

• What distinguishes Jelvix among other .NET application development vendors?
  The majority of software development companies play their competitive game based either on the number of employees or the hourly rate. The difference with us is that we do not need to change your teams during the process, as 84% of our experts are either middle- or senior-level, and 62% of our people work for Jelvix for 3+ years. This means that an expert who scoped your project is very likely going to be working on it one year after the start.