Album Art Downloader XUI
Reply #482 – 2008-08-27 01:40:23
I believe csc.exe is called to perform dynamic compilation to assist with XmlSerializer, and XmlSerializer is used to read and write configuration settings. That would explain why it is being called at loading and closing. I don't know why version 2 is being called, this is not something that is under my direct control. Is it causing a problem? No problems. But remember when I PM'd you about the slow startup of XUI when run for the first time after reboot? I just realized (thou not 100% sure) that part of the slowdown is because the csc.exe is searched from the HD. Why it settles for the "version" (not really versions which makes this even odder) 2 csc.exe, no idea. In fact, I renamed the csc.exe in "v2.0.50727" dir and ran XUI; errorlog.txt pops up:... App version: 0.18.0.0, running on Microsoft Windows NT 5.1.2600 Service Pack 2 System.ArgumentException: The property 'SearchPathPatternHistory' could not be created from it's default value. Error message: Compiler executable file c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\csc.exe cannot be found. ... So it seems that the .NET 2.0 is also required... or does the installer of 3.5 add the "2.0" if it does not exist? The csc.exe of v1.1 and v3.5 is not accepted (again it's the "not versions even if they're named as versions..?). I also noticed that, when running these test in VPC, that the csc.exe runs cvtres.exe (Microsoft® Resource File To COFF Object Conversion Utility) from the same directory. Is the "property 'SearchPathPatternHistory'" relating straight to your code? I mean, I just wondered if you could try to avoid running the csc.exe (&cvtres.exe) automatically.. maybe not possible at all but doesn't hurt to ask you. Though this is quite clearly related to the ".net provides a ready built configuration file system" you wrote, right? And thus nothing can be done about it. And could it be possible to speed up the process by "telling" in your code where the 2.0 csc.exe is? I tried to add the directory to the PATH and rebooted but that had no effect at all.. so it may be that the csc.exe isn't searched after all and it's something else that slows down the startup.. Oh, almost forgot; would it be possible to keep the settings (window size, "MaximumResults", etc.) when upgrading? This should already be happening. If the upgrade isn't working properly, I'll look into it, but it is definitely supposed to keep existing settings. I tested by installing 0.18, changed some things, installed 0.21 over (and finally also 0.22) = all changes (I made, to the options, group by, sort by & maximum results) were kept, except window size. So it's not so big of a deal.. P.S. I saved my testbed in VPC, so if you like me to test something out relating to these conversations..