Load .dll data outside of Initial run time?

[Samishii23]

Ok. So. I have this project going right now that the data I have, being alot of images, some text data, and methods in a .dll.

But since the data I have is constantly changing, while maybe only once or twice in a month span, since this is a "Fan" program from a game.

I am making my .exe basicly being a static .exe, which will call up the Version .dll file with all that versions data in it, but only when called from the .exe while running.

Like this:

Program -> Select Version to use: 3.2, 3.1, 3.0 Exc... (This is basicly like archiving the data)


How would I go about calling in the data from each .dll without having loading them into the .exe during run time so I don't have a memory hog of a program??

[GaryTexmo]

Maybe this will help...

http://www.codeproject.com/KB/cs/pluginsincsharp.aspx

It's an excellent tutorial on plugins, which is similar to what it sounds like you want to do. Your approach is definitely different, but that tutorial should provide you with a solid understanding of how to load dlls on the fly, as well as ideas on how you might wish to set up your class structure.

Good luck!

[tlhintoq]

Instead of putting images and text in a DLL, wouldn't it just a whole lot easier to put those items in a directory in the application directory or the user documents directory... anyplace you can find easily?

Once or twice a month the image of "myTeam.jpg" changes but retains the same name. Same with the text file when it gets new statistics.

Your methods always look for "myTeam.jpg", "myLogo.gif" or whatever.

This has the advantage of not needing to load in ALL the graphics at once when you load in the DLL. You only have to load the graphics needed for a given screen, thus reducing the memory consumption at any given time.

[neocambell]

For me it seems Samishii23 has already planned on the method.

It seems that you refer a set of Win32 DLLs. (not ActiveX DLLs). Is that right?

In this case, you can simply Load each DLL and unload them to free memory.

LoardLibrary and FreeLibrary are the API functions to do so. Using these APIs, you will not be wasting memory to load all at once.

Best Regards

Neo

[Samishii23]

Thank you Gary for the tutorial. I skimed over it real quick, and it looks like it'll give me a basis on what to build into my project. Thanks.

tlhin, I have the data stored in the .dll's so I don't have to have (in my case actually) hundreds if not a 1k files roaming around the users end. Its cleaner on the eyes, especially since the people that will most likely use it will be power users... So I doubt they would want a cluster-f*ck of files on their end.

Neo, I don't believe I would be calling in any win32 dlls. Just all of my own creation. =)

[Plater]

Would a resource file not be a better choice for storing data such as that?
Pretty sure you can load/unload resource files similar to DLL files?

[Samishii23]

Plater - Thats what the dll's are basicly. Their holding the data / images i'll be using in my application. Its just there'll be multiple versions, and I'll be archiving for people to be able to look back at the old, and check it out.

[Plater]

I was just thinking that as far as using different "versions" go, i think the mechanism for dealing with different resource files is setup better then using differing DLLs.

This whole concept has me curious. If/when I get some free time I want to play around with this concept.

[Samishii23]

Plater - You have me curious as well. Feel free to explain if you get a chance, as I am still way new to the language, and could use a nudge in the right direction. =)