Suggestions

[MichaelNesmith]

Hi Treoxx,

Ah, I understand - you wish to enumerate registry keys...that is a good recommendation, thank you. Maybe in the short term you could write a DLL or EXE and call that from your setup?

About Copy/Move Local Files, you are correct. However you can just use Call DLL Function with the CopyFileA Win32 API in kernel32.dll to easily handle this.

Also thanks for the convert path unix style recommendation!

[tymberwyld]

Ok, coming from an InstallShield background (please don't throw anything ) one of the nice features was that Assemblies could be installed into the GAC per Component. In my case, I need to distribute Interop Assemblies for MS Office. I have 2 components "Office10" and "Office11". Depending on which of these components is selected (which needs to be done in the script not by user interaction) the install copies those assemblies to the GAC.

While we're speaking on the GAC. I agree that there should be an option (a properties dialog?) to be able to optionally choose to uninstall an assembly from the GAC.

[tymberwyld]

One thing that is really annoying is that the Script editor is not...well...editable? What is the point of the command "Copy as Text" if I can't "Paste Text"? My point is, I can see the syntax, let me type it. I don't like pop-up dialogs .

I'm a developer, I'm used to coding, so why can't the scripting just be something similar to what coders are used to? One of the things that takes so long in developing a setup is that one has to learn each 3rd party installer syntax. With InstallShield it was something like C++, with another it's like VB, with InstallAware...I don't even know what it is but it takes forever to wrap your head around it . If you guys can interpret your own coding functions as MSI scripts, then why couldn't the functions be easier?

Example:
Instead of:

Code: Select all

Get Component Core Selection State into Variable SELECTED

it could be:

Code: Select all

bool myVar = GetComponentState("Core")
if (myVar = TRUE)
end
myVar = GetComponentState("Core\\SubComponent1")
if (myVar = TRUE)
end


Does anyone else find the functions really...confusing?

[bradak]

It would very much be appreciated if you supported relative file paths. ie (..\\..\\foo.dll).

Many of our files that we distribute are located at nearby projects that are always in the same relative location.

Also, we work as a team under source-control (svn). Each team member checks out their project to their own location and builds it.

Yes I know about $PROJDIR$, and have hacked a bunch of custom steps into visual studio to copy the files to a central location. It would be much cleaner if I could specify where the files are located.

Thanks,
Brad Kremer