![]() ![]() But since we are essentially running a command line application, error checking is not the best and its impossible to troubleshoot what goes wrong at the end-user side. Right now, we run regasm.exe either from the \Framework or \Framework64 directories depending on whether a 32-bit or 64-bit application is being installed, and run it from either the 2.x or 4.x directories. ![]() Doing the registration in the actual installation is going to be a lot more error-prone, so that is not a solution. But this seems to be a hit-or-miss in terms of working. dll directly in our application, in the background. I was hoping that the InstallShield interface now directly supports the registration process instead of having to manually doing it. I found this topic, which is essentially the same issue: NET assembly (.dll) from an InstallScript-based installation. I wanted to see if there were any changed to InstallShield that address how to registry a. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |