On my PC which have installed SQL Windows 6.3, I have no problem with chart both in development and in runtime.
But my colleagues who have not installed SQL Windows do not get chart. No error message, nothing happens.
Ufcchart63.dll is part of the runtime library.
Someone who knows what missing ?
- do you and your collegues have different operating systems?
- which .net version?
- how about the Chart Sample (C:\Program Files (x86)\Gupta\Team Developer 6.3\Samples\62Features\Chart)?
- maybe PCMonitor/PC-Explorer can help
it seems .net 4.0 is also needed
Now it work for my colleague. Our cmd script was messing it up.
But we're getting a huge problem when we're going to release to production for 5000 users. Do you know if it is possible to launch Deploy63.exe with parameter that specifies the path and what to be installed.
It seems that Deploy63.exe must be run. I have tried without and Set
I can see that the script is working, but this is not enough.
that looks like a bunch of work. As I wrote, only copying the deploy-dir is not enough. The install-wizard copies files to the GAC and other windows-directories and registers them. I tried it once to figure out the registry entries, but that was so time consuming, that I stopped it (in 6.1 it was easier).
You can start the deploy setup with command line parameters. (I haven't tried it yet).
It records all of your choices and places them in the silent.ini file (or any file name you choose).
To install at the client side use: Deploy6x.exe /s /f1"silent.ini"
I have made it a prerequisite for my InstallShield installation (as well as some MSC++ redistributables) so it is automatically started if needed before the installation of my app.
The only "problem" I have with this is that the user cannot change the installation path later for my install as the deploy files are installed in my app folder, but for me it's not such a big deal.
Since this is only required for those who use charts. We create a shortcut to install Deploy63.exe.
Most of our users have LocalAdmin.
Igor you wrote "so it is automatically started if needed" what trigger "needed".
Because if you start it for the second time, it will uninstall.
I am checking the existance and the version of cdlli7x.dll in the InstallShield setup script, so the deploy isn't started if the dll is found in the install folder.
Who is online
Users browsing this forum: Ccbot [Crawler] and 0 guests