Notcie the first occurances of any "key/group" are removed in the result list. These entries are removed: (1, "foo1"), (2, "bar1") and (3, "baz")
I have no clue how to do this. I have tried to create a solution, but I don't know how to find the first entry of a group and remove it using LINQ. The .Distinct() and .First() methods seems needed in someway, but I cannot figure it out. I'm sure I can hack something ugly with foreach loops and new lists, but I would prefer a solution with LINQ.
Stick the user control in a WPF Window; then you can "show" it. Hide the window's "chrome" if that's a problem. Same result.
The Master said, 'Am I indeed possessed of knowledge? I am not knowing. But if a mean person, who appears quite empty-like, ask anything of me, I set it forth from one end to the other, and exhaust it.'
― Confucian Analects
I am running a Windows Service that executes successfully every 10 minutes. It instantiates an in house dll file and calls a method to do some process. This dll file logs everything throughout the process. Now the problem is I have no clue where this log file is anymore!!
Normally when we use this dll file and call its methods, it will create a folder called "Custom" inside the application path with log files.
I do not see any Custom folder anymore even tho my code runs and I see the results.
Thanks for your reply. The registry key only holds the path for the service executable file. And I already know where my service has been installed. I can also see the dell files in there. But I do not see the custom folder and log files that the dll file is generating. They are not in that path.
to make sure what file operations are executed, use Process Monitor[^] as Dave already suggested.
My best guess is this: as a service, your code is using C:\Windows\system32 as its default directory; and it won't have sufficient privileges to create a folder or file there, so nothing gets created, and the exceptions got caught and swallowed (which is always a bad idea). If correct, I suggest you set another default path before calling your DLL, using a location that is not full of system files.