0.2.0 clobbers ncrunch

[petemounce]

I had a problem with ncrunch in that it would only be available to me on first-VS-load-after-installation. I reported it here, and we found that the issue could be solved by disabling ExtensionSync.

My extension details are in the forum thread; I was running ExtensionSync 0.2.0 until I disabled it via extension manager.

I'd like ExtensionSync to not clobber ncrunch, please :-)

[latish]

@petemounce I looked at the issue and was able to replicate it today.
ExtensionSync works like this
On VS shutdown, it stores the list of installed extensions in a settings file.
On VS startup, it looks for any extensions installed that might not be present in the settings file, and uninstalls them. To avoid uninstalling extensions that might have been installed since VS was last opened (like NCrunch via an msi installer in this case), it compares the last modified date of the settings file and install date of an extension. If an extension was installed after the settings file was last modified, that extension is not uninstalled. The next time VS is shut down, it'll be added to the settings file.
This logic has been working pretty good so far except with what you reported with NCrunch. For some reason, the last installed date of NCrunch is showing up as Dec 18, 2011 (even though I installed it today Jan 21, 2012). That's why it is removed on VS startup. I am not sure if this is a NCrunch issue, or a VS bug.

[petemounce]

I've posted a theory at http://forum.ncrunch.net/yaf_postsm932_No-NCrunch-menu-item-in-VS2010.aspx#post932 for ncrunch's developer to have a surmise over.