Reply to thread

Message

<blockquote data-quote="jeoffh" data-source="post: 284707" data-attributes="member: 79668">just got MediaPortal to compile in my VS2005 (pro) environment - fairly easy to do. I wanted to tinker with the Configuration app so I set the MediaPortal.Configuration project as the &quot;StartUp Project&quot;. When I run in debug mode I was getting &quot;DirectoryNotFoundException&quot; during the launch. It ends up the app couldn't find my &quot;language&quot; folder, the &quot;Music DSP&quot; dll, etc. Long story short, the lookup routines for &quot;language&quot; LocalisationProvider.GetAvailableLangauges searches for the &quot;language&quot; folder in my &quot;bin\Debug&quot; (where the exe is running from as opposed to my &quot;current working directory&quot;. The folder for searching for &quot;language&quot; is set via &quot;Config.GetFolder(Config.Dir.Language);&quot; which is initialized with &quot;AppDomain.CurrentDomain.BaseDirectory&quot; (which is my bin\Debug) folder.Next, my hack: change AppDomain.CurrentDomain.BaseDirectory to &quot;Directory.GetCurrentDirectory()&quot; in “Config.cs”. In fact, as I look around in the source there are a variety of ways that directory/paths are initialized all over the place: MusicDSP for example, uses “Application.StartupPath”, which is similar to&nbsp; AppDomain.CurrentDomain.BaseDirectory. I changed a few of these (where I was getting exceptions) to “Directory.GetCurrentDirectory()” and everything is working in Debug Mode (F5) as long as I set my Debug setting “Working Directory:” (project settings) to be “&lt;MyBasePath&gt;\trunk\mediaportal\MediaPortal.Base\”So... Instead of using my hack, how am I supposed to be running Configuration.exe in debug mode then? I usually just hit &quot;F5&quot; in the IDE and start debugging, as is my habit. But this cannot work unless the config EXE is moved into the folder where all the required files are – it seems that&nbsp; MediaPortal.Base is the place. How are you guys debugging this beast?</blockquote>

[QUOTE="jeoffh, post: 284707, member: 79668"] just got MediaPortal to compile in my VS2005 (pro) environment - fairly easy to do. I wanted to tinker with the Configuration app so I set the MediaPortal.Configuration project as the "StartUp Project". When I run in debug mode I was getting "DirectoryNotFoundException" during the launch. It ends up the app couldn't find my "language" folder, the "Music DSP" dll, etc. Long story short, the lookup routines for "language" LocalisationProvider.GetAvailableLangauges searches for the "language" folder in my "bin\Debug" (where the exe is running from as opposed to my "current working directory". The folder for searching for "language" is set via "Config.GetFolder(Config.Dir.Language);" which is initialized with "AppDomain.CurrentDomain.BaseDirectory" (which is my bin\Debug) folder. Next, my hack: change AppDomain.CurrentDomain.BaseDirectory to "Directory.GetCurrentDirectory()" in “Config.cs”. In fact, as I look around in the source there are a variety of ways that directory/paths are initialized all over the place: MusicDSP for example, uses “Application.StartupPath”, which is similar to AppDomain.CurrentDomain.BaseDirectory. I changed a few of these (where I was getting exceptions) to “Directory.GetCurrentDirectory()” and everything is working in Debug Mode (F5) as long as I set my Debug setting “Working Directory:” (project settings) to be “<MyBasePath>\trunk\mediaportal\MediaPortal.Base\” So... Instead of using my hack, how am I supposed to be running Configuration.exe in debug mode then? I usually just hit "F5" in the IDE and start debugging, as is my habit. But this cannot work unless the config EXE is moved into the folder where all the required files are – it seems that MediaPortal.Base is the place. How are you guys debugging this beast? [/QUOTE]

Verification