Jump to content

dconnet

Ex Employees
  • Posts

    655
  • Joined

  • Last visited

  • Days Won

    14

Posts posted by dconnet

  1. On 4/3/2018 at 10:58 AM, EdH said:

    To get this to work as you want, I think you will need to uninstall, delete your Evernote database, then reinstall, and as soon as you log in, to to Tools|Options|Sync and enable Sync on demand.

    Simpler - Change the setting in Options, completely close EN, delete the database (assuming no local notebooks), restart. No need to uninstall/install.

  2. Resetting the first account is easy - you can do it in the Options dialog. When you do this with the 2nd instance, it will have an issue because the database is already there - for that, you'll need to directly edit the registry and change the HKEY_CURRENT_USER\Software\Evernote\Evernote6\EvernotePath setting (before running EN).

    • Like 2
  3. On 5/23/2017 at 2:17 PM, scottp said:

     

    I am unable to turn off the setting in the Windows app.  I have the latest Evernote version. 

     

    Huh. It looks like the Options dialog does not work on XP. (We are currently reworking the Options dialog, but that won't be done for a while) While we haven't killed support for XP, I would in no way say we actually support it. We're not likely to fix any XP-only bugs.

  4. On 9/27/2016 at 6:30 PM, jefito said:

    But can you still tell it where to find the database in its custom location?

    Well - kind of - but it will want to move the current database there, not use the one that is already there. The only way to do that in the past was to hack the registry. But StoreApps make that impossible. What you could try would be to do a complete backup of the custom location, point the StoreApp to the existing custom. Tell EN 'yeahyeahyeah'. Then after it finished, close EN (completely) and restore your backup.

    This is no different then having a custom location on a new computer - EN has never had the ability to forget the current database and use a different one (except, as noted, by hacking the registry)

    • Like 1
  5. 5 hours ago, MigdalorGuy said:

    Just installing the WinStore version will replace my existing desktop version, utilizing same file locations, etc, so there's no clean-up necessary and no duplicated files?

    Not quite. It will not touch the existing install. As long as you're running a current version (6.x - post database move), it will utilize the existing database files. If you have moved the database to a custom location, it won't find it (no access to normal-desktop registry). Both versions will not run at the same time (we have never allowed multiple instances for the EXE), so that's not an issue. But you might easily get confused which one is running. Uninstalling the desktop version will not affect the store version. And uninstalling the store version will not affect the desktop one.

  6. The 2 versions use the same (exact) binary. But there are some runtime differences

    - WinStore can do tiles and notifications
    - enscript does not work with WinStore version
    - WinStore is easier to update - no MSI installer
    - Some options that make no sense in the Store have been removed - for instance check-for-updates.

    Other than that, I'm not aware of any other differences. (And I'm who storified it)

    • Like 2
  7. Oh, so I guess 90% of software developers are in the wrong then? The whole Adobe Creative Suite, Thunderbird, Firefox, Chrome, virtually any program except Evernote and iTunes manage to keep the icon pinned. And no, there's no need to uninstall the old version for those programs either.

     

    You misunderstand. When you upgrade an existing installation, the old version is uninstalled (I'm not talking about an explicit uninstall by the user). That is the phase during which the shortcut is cleaned up. That's how msiexec works. The programs you mention may very well be scheduling the removal after the install. Or they may be doing "bad" things.

     

    Unless we can figure out how to safely to an upgrade where we first install and then uninstall, this behavior will not change. We have no plans to reverse engineer how MS stores the shortcuts (yes, I know where they live) and perform undocumented/unsupported actions that are sure to cause issues in future versions of Windows.

×
×
  • Create New...