[Monodevelop-devel] Feedback wanted: Settings and data storage locations
ck at carlo-kok.com
Fri Jan 22 09:40:07 EST 2010
On 1/22/2010 3:11 PM, Rafael Teixeira wrote:
> Just a comment on supportting mutliple versions of MD.
> In Windows it is very common to have many versions of VisualStudio, as
> they've made it hard to compile old solutions in a really compatible
> way (they are changing the look of things with VS2010 that, as newer
> versions of MD, can compile targetting different versions of the
> framework), but I still have 4 versions of VisualStudio in my
> workstation (2003, 2005, 2008 and 2010 beta) and 3 on our build
> servers (no 2010 beta), and they open correctly their respective
> solutions/projects and don't interfere with each other (In truth .sln
> files are associated with a helper VisualStudio-Version auto-selector
> Said that, I don't think MD needs to support multiple released
> versions installed side-by-side, but it would be nice if a development
> (or preview/beta release), could be installed to another prefix and
> could take it in account to keep per-user data in a separate root:
> For instance a development build installed to \usr\local prefix could
> use \usr\local\home\$User\ or perhaps \home\$User\.local\
> in linux. Or perhaps, all your suggested paths would use
> MonoDevelopPreview instead of MonoDevelop, for non-release builds.
> That would allow to also concoct tests for configuration migration
> between versions of MD and of independently released addins, even
> after your proposed wholesale migration.
One easy way to do this would be like Firefox and even Visual Studio
does it, is a "profile". You can start it with --profile "profilename"
and it uses a different directory store the settings (and plugin cache).
The Infrastructure Company
More information about the Monodevelop-devel-list