johnludlow
11-05-2002, 06:24 AM
Hi,
I'm currently evaluating Installshield, comparing it against Wise. I like Installshield better because of Installscript, but I'm worried about its .NET support.
In Wise, if I say the installation contains .NET components, I can add a .NET file and it will automatically detect attributes, dependencies, etc.
I think Installshield does this as well, I'm just not sure how. I added a .NET file, just the same as in Wise, expecting to be asked about the control it depends on, but I wasn't. I checked the help file, and it said "add the file as a component key, and set the .NET Scan At Build property." I checked that the file was a key, and that the property was set, and all seemed ok.
I figured that it might include the required file during the build process, so I built the project, which made no difference - the assembly info had not been added, and the required file had not been included.
What am I doing wrong?
Many thanks
John
I'm currently evaluating Installshield, comparing it against Wise. I like Installshield better because of Installscript, but I'm worried about its .NET support.
In Wise, if I say the installation contains .NET components, I can add a .NET file and it will automatically detect attributes, dependencies, etc.
I think Installshield does this as well, I'm just not sure how. I added a .NET file, just the same as in Wise, expecting to be asked about the control it depends on, but I wasn't. I checked the help file, and it said "add the file as a component key, and set the .NET Scan At Build property." I checked that the file was a key, and that the property was set, and all seemed ok.
I figured that it might include the required file during the build process, so I built the project, which made no difference - the assembly info had not been added, and the required file had not been included.
What am I doing wrong?
Many thanks
John