|
If you are asking what files you need to run your program then you can use the program Depends which comes with VC++. It will show you which files your program requries.
If you're asking what files you need to run install shield then read the documentation. There's a section on distributing your install program.
When you say "automatically dispose the dialog box" do you mean it closes automatically right after you start it? If that's the case then there could be lots of reasons it's failing. I suggest running a debug version of your app on your other system.
|
|
|
|
|
Say I have DialogX with its code compiled into xstuff.dll. How would I open this dialog from an application such as getx.dll.
Thanks
-Matt Newman 
|
|
|
|
|
Opps. I forgot to say I am working with MFC in both.
-Matt Newman
|
|
|
|
|
You would need to export a function in the dll to display the dialog, then use it.
One method (not actual code):
LoadLibrary(getx.dll)
GetProcAddress(DispalyDialog)
Call method to display dialog
|
|
|
|
|
![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)
Installshield really sucks. What do other people use?
By chance, does a demo project of a simple installation package exist anywhere? I would really like to create an intallation package, but i don't want to start from scratch. I am hoping to adjust and modify other code to make it work for my project.
Please, any repsonse any one can give me will be greatly appreciated.
My email address is brinasas@yahoo.com
Sincerely,
Danielle
|
|
|
|
|
We use Setup Factory and it rules. It's cheap and it's simple to use.
Christian
#include "std_disclaimer.h"
People who love sausage and respect the law should never watch either one being made.
The things that come to those who wait are usually the things left by those who got there first.
|
|
|
|
|
Perhaps you could be more specific then "Installshield really sucks". I've usually found that comment from people who don't understand how to use it. What version are you using? What don't you like about? What problems are you having?
|
|
|
|
|
But it DOES really suck! Here's why:
1) Each installation requires a large tree of folders, each with uncountable binary files. Just try checking that into a source control system. Well-designed installers, such as Wise, use a single file.
2) It is ridiculously hard to learn. Again, compare to Wise.
3) It is buggy as hell. Need I repeat myself here?
4) The stupid progress control it sets up in the lower right corner of the screen. Ugly and uninformative. Yes, I know it can be disabled, that's why this is #4 instead of #1.
|
|
|
|
|
We have managed to overcome these deficiencies and Installshield works well for our case. You don't seem to understand it and think it is something it is not.
Once you take the time to learn it properly and try to work within it's limits, not the way you think it should work, you may have more constructive feedback than "it sucks"
If you think Installshield is difficult stay away from Windows Installer.
|
|
|
|
|
Customizing dialogs etc. can be a major pain in the arse.
It leaves files in your temp directory. I've seen people unable to install a program because they exceeded the file limit for that directory. It was full of install shield temp direcotries.
If the scripting language doesn't meet your needs then you're kinda screwed.
Supporting multiple languages is costly.
I'm not a big fan of install shield either.
Todd
|
|
|
|
|
Customizing dialog is not very difficult if know what your doing.
Leaves temp files. Yes, but I have seen that behavior from many other applications also.
If the scripting language doesn't meet your needs extend it with a custom dll. Can't get much better than that.
Yes they charge large fees for additional languages.
|
|
|
|
|
Wise, DanYell. www.wisesolutions.com
|
|
|
|
|
I would like my program to remember the state of a few check boxes and radio buttons from the previous time it was run. How can I accomplish this?
Also I would like the program to open in the same position as it was closed from the previous run.
|
|
|
|
|
The registry or an ini file. I'd go registry, but some people prefer to put the data in a local file. My reasoning is that this is what the registry is for, and I like my state information to by hidden from the majority of users. The other side reasons ( quite reasonably ) that too much junk goes into the registry. So the choice is yours.
Christian
#include "std_disclaimer.h"
People who love sausage and respect the law should never watch either one being made.
The things that come to those who wait are usually the things left by those who got there first.
|
|
|
|
|
The registry is good for that - as long as you don't put too much in it. Usually you'll see code in InitInstance (after the call to SetRegistryKey) that calls GetProfileInt (or whatever) to retrieve settings (which can then be set to the dialogs members), and WriteProfileInt calls in ExitInstance that store tham back.
Or you could use an .ini file, or persist to file. There may be religious opinions about this! 
|
|
|
|
|
I also store simple state data in the registry even though I do not like the way MS implemented the registry. (Concept is good, implementation is bad). The most important thing to consider when storing data to the registry is the probability that the user may want or need to edit that data. It is generally a VERY bad idea to store user configurable data in the registry. If they accidentally edit/delete the wrong thing they will hate you forever. Use an ini file for user editable configuration data.
|
|
|
|
|
John
the following code works if you are using a dialog based application, place the SetWindowPos() function in OnInitDialog() and GetWindowRect() function in OnOK or another function that gets called before the dialog closes. You would then need to read/write the values to the registry or ini file.
CRect rect;
GetWindowRect(&rect);
int nLeft = rect.left;
int nTop = rect.top;
SetWindowPos(&wndTop, nLeft, nTop, 0, 0, SWP_NOSIZE | SWP_NOZORDER);
Michael Martin
Pegasystems Pty Ltd
Australia
martm@pegasystems.com
+61 413-004-018
|
|
|
|
|
I have a doc / view project with a container. I load a word object (I use automation for msword9.dll).
whenever escape is pressed the object disappears.
I searched in the msdn and found nothing,
so I implemented a WH_KEYBOARD_LL hook, that catches all VK_ESCAPE messages,
the problem is that this kind of hook can be only globally set, so I can't use it anywhere else.
anyone has an idea?
Omri W.
|
|
|
|
|
I have an application that is a system service (Windows 2000). Among other things, I want it to set a system hook to trap WH_KEYBOARD_LL messages. However, my message handler does not seem to get called. The same code works fine when it is not running as a system service. Is it impossible for a service to set such hooks?
Any help is greatly appreciated!
|
|
|
|
|
Is your service logging in as the system account? If so, change it to log in as you and see if it then works. If that fixes it, then the reason you're not getting called when logged in as the system is a security restriction.
--Mike--
http://home.inreach.com/mdunn/
Sometimes, arming yourself with a big pointy stake just won't do you any good.
|
|
|
|
|
Hi,
I am trying to link to a dll at runtime. My DLL is definitely okay, it has a functon :
_declspec(dllexport) int increment(int val)
The client to the DLL executes the following code:
typedef int(*lpf_increment)(int);
HINSTANCE plugin;
plugin = LoadLibrary("c:\\plugin.dll");
if (plugin != NULL)
{
lpf_increment testcall;
testcall = (lpf_increment) GetProcAddress(plugin, _T("increment"));
int val=99;
int res = (testcall)(val);
char dump[60];
wsprintf(dump,"%i",res);
MessageBox("dump");
}
The GetProcAddress returns null, anyone any clues what's wrong?
Cheers
Richard
|
|
|
|
|
Run Dependency Viewer on your DLL - chances are the exported function is name-mangled, and not actually exported as "increment".
--Mike--
http://home.inreach.com/mdunn/
Sometimes, arming yourself with a big pointy stake just won't do you any good.
|
|
|
|
|
make sure that the function is being export correctly.
if it is C++ the export name will be name-mangaled
to view the exports from any dll use the dumpbin or depends utility from VC++
dumpbin /exports mydll.dll | more
When you build your DLL put this in the header file
this assumes that your Function/method to be exported is called int foo(int);
// exporting dll header file
#ifdef __cplusplus
#define EXTERN_C extern "C"
#else
#define EXTERN_C
#endif
EXTERN_C int foo(int);
|
|
|
|
|
make sure that the function is being export correctly.
if it is C++ the export name will be name-mangaled
to view the exports from any dll use the dumpbin or depends utility from VC++
dumpbin /exports mydll.dll | more
When you build your DLL put this in the header file
this assumes that your Function/method to be exported is called int foo(int);
// exporting dll header file
#ifdef __cplusplus
#define EXTERN_C extern "C"
#else
#define EXTERN_C
#endif
EXTERN_C __declspec(dllexport) int foo(int);
|
|
|
|
|
Thanks That Was Really Appreciated! Everythings clear now.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
