Community Forums
Results 1 to 3 of 3

Thread: Yes Projects, no output - Installshield X useless...

  1. #1
    Join Date
    Jan 2002
    Posts
    33

    Yes Projects, no output - Installshield X useless...

    Just trying out an evail of the new version in VS.NET

    IO install the eval, hotfix it, open a nice solution with 25 projects, add a vs.net output thing.

    Try addining project outputs - nothing. Nada. Nihil. Zero. No project has an output. The projects show, but (on the solution) "refresh" kills them, they disappear.

    Well done.

    But anyhow, there is an error log:

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\SourceTree.cpp 1288: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\SourceTree.cpp 1288: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\SourceTree.cpp 1288: Invalid index.

    file://C:\Program Files\InstallShield X\Program\0409\ISGCompAdvancedContents.htm 23: Typen unverträglich
    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.

    D:\BldRoot\source\src\IsWsAppFiles\IsWsAppFilesView.cpp 627: Invalid index.


    Looks terribly like some really sloppy programming in IsWsAppFiledView.cpp.

  2. #2
    Join Date
    Nov 2002
    Posts
    31
    It seems like InstallShield pushes their developers to crank out releases, and if the product isn't ready by the deadline, release it anyway and fix defects with hotfixes later on. Some of the stuff that gets through quality control is rediculous, and a lot of the workarounds are just stupid. I've been using IS since Dev 7, and I cannot count the number of times I have had to refer to the KB for workarounds. I hope that in the future they focus more on creating a robust product rather than continuously making shoddy IDEs that crash and try to get us to pay license fees to upgrade. They aren't under much pressure with a big name that is synonymous to Install and basically one competitor, Wise.

    For example: When you add a SQL connection to an InstallScript MSI project an InstallWelcome dialog automatically gets created in your project. To make things worse, your project doesn't compile because the dialog is corrupt. How does this defect make it through the test cycles?

  3. #3
    Join Date
    Jan 2002
    Posts
    33
    I hope that in the future they focus more on creating a robust product rather than continuously making shoddy IDEs that crash and try to get us to pay license fees to upgrade.
    Why do you think I do not buy their product and do not pay for it? I try them out every new release, and they have never so far managed to survive the first half hour, and ALWAYS on the level of not doing what they are supposed to do.

    This is just the end of the circle for me - I installed the X eval, tried to set up an installer in one of the existing projects here and was a little stumbled that - it does simply not work.

    Let's see whether an answer on this comes out. And no, workaround are not something I would even look at. This is way too critical and basic to not work.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •