|
May
16 |
|
asked | ThreadAbortException suddenly appears after godaddy changed servers |
|
May
1 |
|
awarded | Enlightened |
|
May
1 |
|
awarded | Nice Answer |
|
Apr
17 |
|
comment |
InstallShield LE (with Visual Studio 2012) completely fails to detect dependencies On top of THAT, I've built a setup project for a web app twice in a row and had two different .msi files come out - one was correct, the other put all the dlls in the root folder instead of the /bin.. shoddy is giving ISLE too much credit |
|
Apr
17 |
|
comment |
InstallShield LE (with Visual Studio 2012) completely fails to detect dependencies The only thing that has ever worked for me is to manually include the outputs for projects that aren't coming across. The strangest thing to me is, it started out just fine, worked for months, then without changing the installer, suddenly an it's including old dlls, so I fixed it by including the project output. Then it works for a while, then another project's dlls start showing up outdated... Installer never changed. |
|
Apr
16 |
|
awarded | Popular Question |
|
Feb
28 |
|
awarded | Popular Question |
|
Feb
20 |
|
awarded | Nice Answer |
|
Jan
26 |
|
awarded | Yearling |
|
Jan
21 |
|
comment |
SQL 2008 - Getting around cyclical foreign key errors when trying to generate insert data scripts Doing a demo data dump to a local server before a conference and the interface had changed and suddenly it wasn't working (I guess I updated SSMS or something)... this worked and saved my butt, Thanks! |
|
Jan
4 |
|
awarded | Necromancer |
|
Dec
22 |
|
awarded | Yearling |
|
Nov
28 |
|
comment |
type or namespace name does not exist Good lord that damn Client Profile strikes again! Thanks Nathan, you you saved me a hair pulling session, and I like my hair :) |
|
Nov
23 |
|
awarded | Benefactor |
|
Nov
23 |
|
accepted | When using InstallShield LE, the msi contains an outdated version of one assembly, but current versions of others |
|
Nov
23 |
|
comment |
When using InstallShield LE, the msi contains an outdated version of one assembly, but current versions of others Got the logging worked out, there's a command line switch for the installshield LE setup exe that allows you to pass the logging parameters on to the msi. Looked at the log and didn't actually see my assembly getting installed. Now I'm wondering if there's some assembly cache that it searched through when the installer didn't have the file... At any rate, I modified my installer to explicitly include the offending project's primary output instead of relying on it to be picked up as a dependency and voila it worked. I'm marking yours as the answer because the logging was just what I needed! |
|
Nov
23 |
|
comment |
When using InstallShield LE, the msi contains an outdated version of one assembly, but current versions of others I've been thinking about making this transition for some time. The learning curve always steered me away in favor of something I could throw together more quickly. However, after years of frustration with the limitations of Setup Projects and now InstallShield LE, I can't imagine the total cost of a WiX implementation to be any higher. |
|
Nov
23 |
|
comment |
When using InstallShield LE, the msi contains an outdated version of one assembly, but current versions of others All my references for the assemblies that have problems are 'project references'. As part of my sanity check, I did go through and verify each of the references. Additionally, in the actual Bin folders, the correct version is present. It is only in the installer that the file gets reverted to an old version. |
|
Nov
16 |
|
comment |
When using InstallShield LE, the msi contains an outdated version of one assembly, but current versions of others I'm using InstallShield LE, I'm not sure if the "key file of its own component" is something I can manipulate - if so please give me more details on how. Similarly, I'm not sure how to get a more verbose log than what is displayed in the output window during the build, please do tell. |
|
Nov
16 |
|
awarded | Promoter |
