Distributing a data access solution across multiple solutions
I have 3 solutions, one of them is a dataccess solution with all the repositories etc. At the moment when a change is made to it, the others have to go get the latest nuget version locally, we have a nuget server on the LAN. Its a pain to debug though.
How to avoid binary dependency on size change
class A { public: int i; }; // A.h and defined in project libA.vcxproj (libA.dll) I’m using class A in multiple places at various projects as below. Apporoximately 100 projects. include “A.h” class UseA { public: A *a; UseA(){ a = new A(); } ~UseA() {delete a;} } My problem is whenever I add a […]
How to avoid binary dependency on size change
class A { public: int i; }; // A.h and defined in project libA.vcxproj (libA.dll) I’m using class A in multiple places at various projects as below. Apporoximately 100 projects. include “A.h” class UseA { public: A *a; UseA(){ a = new A(); } ~UseA() {delete a;} } My problem is whenever I add a […]
How to avoid binary dependency on size change
class A { public: int i; }; // A.h and defined in project libA.vcxproj (libA.dll) I’m using class A in multiple places at various projects as below. Apporoximately 100 projects. include “A.h” class UseA { public: A *a; UseA(){ a = new A(); } ~UseA() {delete a;} } My problem is whenever I add a […]
Handling changes specific to a customer
The problem
Handling changes specific to a customer
The problem
Handling changes specific to a customer
The problem
Handling changes specific to a customer
The problem
Handling changes specific to a customer
The problem
Multiple entrance points in project
My question is related to C++ but it comes from Java actually.