Our Application has many DLLs and one exe File. It is completely written in C#. We do not want to deploy anything into the GAC, but we are just putting all assemblies into our application folder.
What exactly is the difference between "Install Files" and "Install Assemblies" Command ?
We want ngen.exe to compile our files at installation time. How is this done?
Why can only .dll files be added into the Assemblies List ? Doesn't it make sense to allow .exe Files, too ?
In the Files dialog, I can select the feature which the user must select to install the files which are shown int the list. Why does the Assembly List lack such a feature selection DropDownList above the list ?
Kind Regards
Matthias
Install Assembly vs Install Files
If you are not deploying anything into the GAC, it is probably best if you stick with the Install Files command. The Install Assembly command registers the installed assemblies on the system and from what you say it sounds like you don't want this behavior.
You can run ngen.exe after the Apply Install command executes using the Run Program command. You can also hide the ngen.exe window, so no command line windows pop up and distract the user.
I apologize about the limitations in the assembly visual view. However, you can always go directly down to the script level and customize exactly which files you are installing, and as part of which features. When you switch back to the visual view, it will display your latest changes.
You can run ngen.exe after the Apply Install command executes using the Run Program command. You can also hide the ngen.exe window, so no command line windows pop up and distract the user.
I apologize about the limitations in the assembly visual view. However, you can always go directly down to the script level and customize exactly which files you are installing, and as part of which features. When you switch back to the visual view, it will display your latest changes.
Who is online
Users browsing this forum: No registered users and 41 guests