StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7823764
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-19T15:26:52.773
FavoriteCount
0
LastActivityDate
2011-10-19T15:26:52.773
LastEditDate
LastEditorUserId
0
OwnerUserId
646466
ParentId
4911994
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
I found this to be such an interesting question that I took the time to write an extensive tutorial on how to use DLL's to share data among multiple DLLs (either implicitly, or explicitly linked) but also make sure the data is not shared among separate processes of the same executable file. You can find the full article here: <a href="http://3dgep.com/?p=1759" rel="nofollow">http://3dgep.com/?p=1759</a> <hr> A solution to this problem that I found to work quite well is to create a "common" or "shared" dll that defines all the data and methods that you want to share across multiple DLL's (but not shared among processes). Let's suppose you want to define a singleton class that can be accessed from the main application code (the EXE) but you also want to access the singleton instance in shared (either implicitly or explicitly linked DLL). First, you would need to declare the singleton class in the "common" DLL: <pre><code>// Export the class when compiling the DLL, // otherwise import the class when using the DLL. class __declspec(dllexport) MySingleton { public: static MySingleton& Instance(); }; </code></pre> When compiling the CommonDLL project, you have to export the class declaratoin by decorating the class with <code>__declspec(dllexport)</code> and when you are using the DLL (in the application for example), the class definition needs to be imported by decorating the class with <code>__declspec(dllimport)</code>. When exporting a class by decorating the class with the <code>__declspec(dllexport)</code> specifier, all of the class's methods and data (even private data) are exported from the DLL and usable by any DLL or EXE that implicitly links to the common DLL. The definition of the MySingleton class might look something like this: <pre><code>MySingleton& MySingleton::Instance() { static MySingleton instance; return instance; } </code></pre> When compiling the common dll, two files will be produced: <ol> <li>The Common.DLL file which is the shared library that defines the mehthods and data exported used by the DLL.</li> <li>The Common.LIB file which declares stubs for the methods and members exported from the DLL.</li> </ol> If you link you application against the exported LIB file, then the DLL file will be implicitly linked at runtime (as long as the DLL file is found in the DLL search paths) and you will have access to the singleton defined in the CommonDLL.DLL file. Also, any shared library (plug-ins for example) that also links against the CommonDLL.LIB file will have access to the same singleton instances when dynamically loaded by the application. For a full explanation of this solution including a source code sample, check-out the following article I posted titled "Using Dynamic Link Libraries (DLL) to Create Plug-Ins": <a href="http://3dgep.com/?p=1759" rel="nofollow">http://3dgep.com/?p=1759</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSharing a global/static variable between a process and DLL
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJeremiah
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.