|
This is good advice, with one caveat.
Linking with static libraries will solve the problem only if the only parameters passed between the caller and the DLL are simple objects (char, int, ...), pointers to simple objects, or pointers to arrays of simple objects. If you try to pass something like a FILE*, there is no guarantee that the caller and the DLL agree on the format.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Truth there. The good news is that I know who my customers are and all of the data types are simple.
Shudder, I cannot imagine passing a file pointer but I guess someone might do it 
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
I admit I'm rusty here and rebuilding my knowledge base on how all of this works. I do have a clean Xp machines, excellent suggestion.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
You could try running the code with modern libraries, and it is possible (although less probable) that it would work. But much safer to rebuild completely, since the dependencies are often hidden deep in the libraries or OS. One thing you may like to consider is whether you really need your library as a DLL rather than static. The only advantage of using a dll is in situations where you have multiple active applications that are all calling in to it. If it is only used by a single application then a static library, or even no library, is a better choice.
|
|
|
|
|
Quote: The only advantage of using a dll is in situations where you have multiple active applications that are all calling in to it.
There are some other cases. Once I had a data collection app that needed to interface with potentially hundreds of different instruments. Having a monolithic app would have been impractical.
Mircea
|
|
|
|
|
Well once it is in memory and the dll is loaded it will take up pretty much the same space as it would with a static library.
|
|
|
|
|
The thing was, in my case, that no user had all the instruments. Forcing them to load all the unused code would have been too taxing.
Pretty much the same case as an OS that needs drivers (DLLs) for different devices. Loading code for all wouldn’t be a solution.
Mircea
|
|
|
|
|
This is where I am struggling. Not using a DLL just won't work for this application as it allows independent applications to talk to our system.
The issue at hand (I think) is that I have Visual Studio / Microsoft rot. My laptop is over 4 years old, and I just don't pay attention to the ramifications of installing <insert version="" here=""> of visual studio that may in fact also install an SDK. The development environment is a hodge podge mix of this stuff. It's almost certainly why everything is confused at the moment. I'm trying to clean it up.
So, it's my understanding that all of these OS dlls come from the SDKs, am I correct? These SDKs tend to be generally related to OS releases. If I have a DLL, what's the best practice - make sure I always use the latest SDK? This also trails into the runtime libraries that are a necessary part of an installation package. Off to msdn...
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
charlieg wrote: The issue at hand ...
 . That certainly needs to be fixed.
charlieg wrote: So, it's my understanding that all of these OS dlls ...
Windows itself contains all the standard run time libraries. If you want to develop your own applications then you need a compiler and its associated SDKs (.lib and .dll files), some of which may be newer versions than the Windows versions. Once you build your application then you need to ensure that the correct .dlls are installed on any system that installs the application. That is why you need installers, rather than just copying the .exe files.
Visual Studio has all the tools necessary to do this, although most people seem to prefer one of the non-Microsoft installers.
|
|
|
|
|
My understanding as well. I have some clean Windows 10 Professional VMs, so I'll start with those.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
oh the life of manufacturing systems.
If I build a dll on a Windows 10 machine, is there hope for it to run under Xp? Assuming I don't do anything silly and use post Windows Xp features?
I've just discovered with this inherited piece of code that the customer runs it under Xp. I'm thinking just use the Xp tools and stay there.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Judging by other reports I have seen the answer is: it depends. Microsoft has never tried to be backwards compatible in their systems but some applications will still work. The only way to find out would be exhaustive testing. But for a commercial product I would suggest that you should stick to XP for all development and testing.
|
|
|
|
|
By any slim chance, does anyone have the code for triangular plate bending finite elements? I'm looking first for the stiffness matrix. I can read C, Fortran, python, Java and probably figure out some others. Any help would be appreciated - Thanks, Ed
|
|
|
|
|
You seem to think there's only one way to write that kind of code.
And, no, nobody is just going to hand over there hard work writing that kind of code, unless they want to publish it on the web. In that case, Google is your best friend.
|
|
|
|
|
In earlier 70s I used one of such types of triangle thin bending elements (so called "incompatible elements").
The base knowledge about FEM I got from the O.C. Zienkiewicz book: it called somehow like "finite element method in engineering science" or similar. There were some ideas of to implement this type of element and a lot of Fortran code examples 9very simple but very useful!)
Not sure you will be able to find in Web something useful about it, but just try!
As for me, I have lost all my sources (punch cards desks and listings) many years ago.
|
|
|
|
|
Victor, I have that book and many others. I've written the code for quadrilateral plate elements (also when we used punch cards) but I have a client that wanted something quickly. I just thought I'd ask and try to save myself a couple of days. Thanks.
|
|
|
|
|
I create an application in C++(MFC) but I did not find a way to design a report in VS2019 toolbox;
please can anyone help with an example in how to create or generate a report in C++/MFC;
thanks in advance;
|
|
|
|
|
What kind of "report" do you mean? 
|
|
|
|
|
a FMC program to calculate electricity bill then print out a report with a header and footer
|
|
|
|
|
Do you mean something similar to CR-report?
Or just a List Control (MFC CListCtrl) in report (Detail) style?
|
|
|
|
|
|
|
I find it easier to create an HTML file that I can format, and then open that file with the default browser. The user can then print at their discretion.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
How can I know the version of an console application executable ? (obviously, this exe is not made it by me)
|
|
|
|
|
Unless the executable contains version information you can't. It is possible to add version information in a resource definition file when building a console app, but few people do so. Right click the .exe and check the properties.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
