#251 App won't load after new install

v1.2.0.114_SP1
closed
Dare Obasanjo
5
2012-09-23
2004-08-31
Don Kitchen
No

After installing 1.2.0.114 SP1 over my 1.2.0.114 version,
the application won't start.
A "System.IO.FileLoadException" occurs in RssBandit.exe.

When I attempt to debug via VS.NET the additional
information is as follows:

"The located assembly's manifest definition with the
name "SandBar" does not match the assembly reference.

After that, I'm dead in the water. I think I'm going to
try to roll back to an earlier version.

Discussion

  • Don Kitchen
    Don Kitchen
    2004-08-31

    Logged In: YES
    user_id=1113905

    Update: After removing the old installation and trying again
    (this time making it available for "Just me" rather
    than "everyone") it seems to work.

    I'm not sure if simply removing and re-installing was the trick
    or choosing "just me" this time did it. Either way, it works
    now.

    Hope this helps!

     
  • Dare Obasanjo
    Dare Obasanjo
    2004-08-31

    Logged In: YES
    user_id=24549

    What is the version number of Sandbar.dll in the C:\Program
    Files\RssBandit folder? Is it 1.0.12.2 ?

     
  • Logged In: NO

    Uninstall of old version and reinstall fixed this for me,
    with available to everyone selected both times.

     
  • Don Kitchen
    Don Kitchen
    2004-08-31

    Logged In: YES
    user_id=1113905

    The version that I have is 1.0.12.2. Again, the app is
    working for me now, so I can't say what version may have
    been there when I was in a non-working state.

     
  • Mike Green
    Mike Green
    2004-08-31

    Logged In: YES
    user_id=1108842

    I recall seeing somewhere a general problem described with
    installation packages created with Visual Studio related to
    upgrades where the first installation was done
    with "Everyone" selected and the upgrade was done
    with "Just Me" selected or vice-versa. If the selected options
    were the same between the first installation and the upgrade
    then the problem didn't occur. I can't locate a full description
    of the problem in a Knowledge Base now but if someone is
    going to try recreating this problem then I suggest testing
    with this scenario.

    One solution to this problem, that we have adopted in our
    help desk product, is to remove the "Just Me"/"Everyone"
    options via Orca (see MS Knowledge Base Article 835460). An
    even better solution is to replace the Visual Studio building of
    the installer package with an installation package built with
    WiX (available on SourceForge), again without the "Just
    Me"/"Everyone" options.

     
  • Dare Obasanjo
    Dare Obasanjo
    2004-09-03

    Logged In: YES
    user_id=24549

    Fixed by v1.2.0.117