Bug 5121 - Should MD log path include version number?
Summary: Should MD log path include version number?
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 3.0.x
Hardware: PC All
: --- enhancement
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-05-16 09:32 UTC by PJ
Modified: 2012-05-16 15:26 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NOT_ON_ROADMAP

Description PJ 2012-05-16 09:32:16 UTC
The current path for MD log files is something like:

C:\Users\<User_Name>\AppData\Local\MonoDevelop-3.0\Logs

Is there a reason we have the 3.0 in the folder name? The logs should have more detailed version info anyways (bug 5120)
Comment 1 Mikayla Hutchinson [MSFT] 2012-05-16 15:26:47 UTC
The data directories are versioned between major MD versions to prevent different versions of MD interfering with each other, when data formats change. It's not unheard of for users to have multiple versions of MD, or to downgrade, etc.

You could argue that log directory should be exempt from versioning, but it's probably more trouble than it's worth, and the inconsistency might be confusing...

I'll WONTFIX this for now, but it's certainly something we could reconsider.