C++ Library API Design
I’m looking for a good resource for learning about good API design for C++ libraries, looking at shared objects/dlls etc. There are many resources on writing nice APIs, nice classes, templates and so on at source level, but barely anything about putting things together in shared libs and executables. Books like Large-Scale C++ Software Design by John Lakos are interesting but massively outdated.
Memory concerns while plotting escape from DLL Hell in Delphi [closed]
It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 11 years ago. I work on a program with about 50 […]
How to update dependency during runtime in my .NET application?
I have a server-client application. Sometimes the server is updated which requires some DLLs in the client to be updated as well (The DLLs are the dependencies of the main executable). For now, we have to close the client, manually deploy the DLLs, and then start the client again. This is kind of an inconvenience because the client is an automated application, so normally it doesn’t need any user intervention.
GPLv2 – Multiple AI chess engines to bypass GPL
I have gone through a number of GPL-related questions, the most recent being this one:
Communication between a C# application and C++ DLL
I am currently building an audio streamer and I have a CPP .dll that I use functions of inside the WPF C# GUI.
should I be putting database connections into a class library?
This might be a stupid question but I’ve never created a class library before
Restrictions Calling DLLs Across Technologies?
I want to call a DLL in my programming language of ‘choice’. The documentation surrounding this clearly states that it must be a 32-bit DLL written in C, C++ or Delphi. But I wanted to call a DLL written in C#. It goes on to mention that the default calling mode is cdecl.
Program modules separated in different DLLs
We have an existing ERP system written in VB 6 that we are converting to .Net incrementally. Now, every module in the system is being separated into DLLs so that the product becomes customizable and flexible. I’m not sure if this is the way to do this.
Sharing dlls in a software deployment
We are moving our software project from the practically auto-creating Visual Studio Installer in Visual Studio 2010 to a WiX installer. I’d like to use this change to make sure things are right.
Sharing dlls in a software deployment
We are moving our software project from the practically auto-creating Visual Studio Installer in Visual Studio 2010 to a WiX installer. I’d like to use this change to make sure things are right.