Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

.NET Framework dependency

When developing a desktop application in .NET, is it possible to not require the .NET Framework? Is developing software in .NET a preferred way to develop desktop applications? What is the most used programming language that software companies use to develop desktop applications?

Is the requirement of the .NET Framework just assumed based on the Windows OS you have installed hence why they list Windows OS version requirements?

like image 625
Bryan Roth Avatar asked Aug 14 '08 15:08

Bryan Roth


People also ask

Is .NET Framework OS dependent?

NET application is platform-dependent because of the . NET framework which is only able to run on the Windows-based operating system.

What are .NET dependencies?

Diamond dependenciesIt's a common situation for a . NET project to have multiple versions of a package in its dependency tree. For example, an app depends on two NuGet packages, each of which depends on different versions of the same package. A diamond dependency now exists in the app's dependency graph.

Does .NET Framework have Dependency injection?

.NET supports the dependency injection (DI) software design pattern, which is a technique for achieving Inversion of Control (IoC) between classes and their dependencies. Dependency injection in .NET is a built-in part of the framework, along with configuration, logging, and the options pattern.

Does .NET Framework 4.8 include 4.7 2?

if you have 4.8 then you have 4.7. 2 automatically.


1 Answers

You can still develop applications for the windows desktop using C/C++, eliminating the requirement to the .NET framework, but you'll need to make sure the necessary libraries are already on the system or installed.

The nice thing about the .NET framework is that Windows XP SP2 and Vista has the 3.0 framework runtime installed by default.

In a lot of ways, this is Microsoft's "development standard" and has been that way for a while. This allows you to not worry about having a bunch of libraries tacked onto your application. If you're sticking to all of the .NET provided libraries, you wind up only have to worry about deploying your executable, which is a big headache reliever. When you have a bunch of libraries you have to deploy as well, then you start to run into hassles when you write updates, because you have to make sure those updates are pushed out in your existing installer and to all the existing installed apps out there.

As for "preferred", that always tends to ruffle feathers at times, but there are more and more .NET developers wanted for the web and the desktop at the job hunt sites I tend to visit. 8^D

EDIT: Many thanks to Orion for pointing out my confusion on the frameworks. You get 3.0 "out the gate if you're on XP SP2 or Vista. Everything else is going to require a simple download or run of Windows Update.

like image 110
Dillie-O Avatar answered Oct 08 '22 01:10

Dillie-O