Why are C# libraries all in one file (.dll), but C++ libraries in so many diferent files

Question

1.00/5 (1 vote)

See more:

I don't understand why is using libraries in c++ so much more complicated than in c#, and if I am making a mistake by having so many folders like (/lib, /include, /LICENCE.txt ...)

What I have tried:

I am currently using cmake to build and install libraries than makes it much hard to manage projects and dependencies

Posted 13-Dec-20 8:57am

Member 15019969

Updated 13-Dec-20 22:33pm

Add a Solution

Comments

Richard MacCutchan 13-Dec-20 15:04pm

All systems are similarly complex. You just need to learn the rules.

Member 15019969 13-Dec-20 15:10pm

hey Richard, so why do I need to create so many files in a c++ project and not in a c# project

Richard MacCutchan 13-Dec-20 15:43pm

You don't.

[no name] 13-Dec-20 15:39pm

*lol* my experience is that in c++ I have in average about 20 dll while in c# it is at least factor 10 more git this and git that. Don't take this too serious ;)

Richard MacCutchan 13-Dec-20 15:45pm

"git this and git that"
In idiomatic English that is quite funny. :))

[no name] 13-Dec-20 16:12pm

Uuups I need to ggogle or you give me a hint ;)

CHill60 14-Dec-20 3:11am

:-) In British English slang a git is "a stupid or worthless person (especially a man)"
In Phonetic "Northern" English (Scotland & Northumberland anyway) "git" means "get", so "git this and git that" is very descriptive!

[no name] 14-Dec-20 7:48am

Thank you very much.

2 solutions

Solution 2

.NET creates the illusion of a container where "everything exists" ... the FrameWork [^],

A specific design goal of .NET and the GAC (Global Assembly Cache) was to eliminate "dll hell" caused by the need to explicitly manipulate DDL code libraries as their versions/facilities changed [^].

Under the illusion are many millions of lines of code, and tons of files :)

Posted 13-Dec-20 22:33pm

BillWoodruff

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2020-12-13T09:21:00

They aren't.
The basics of the .NET framework are in one library and that is required by all installations and are installed once per machine (unless you have multiple versions on .NET installed)

After that, users can add DLL files as necessary and they will be installed when the app is.

C++ doesn't do that because it uses a library system that isn't all installed - it's only added with the app when that is installed - so you only add the libraries you need to use to save space.
Unless you create a CLR C++ app, in which case it's the same as C#, with optional extra libraries.

Plus, you have to remember that C++ is based on C, and it's heritage shows in the library design. In theory, C++ apps can use any old C library (in practice, not a hope in hell - some of 'em are 16 bit, never mind trying to get a 32bit library working with a 64 bit EXE file!)