Well, I am experiencing a truly random error, and I cannot find a reason why this will happen. I have an application that I am updating that was developed MANY years ago. I am working on a large development team whose sole responsibility is to manage this application, and we have agreed that the project is a bit of a franken-code project. We are just modest developers among many generations of developers who have inherited this project. (It will be important to know later.)
There is a part of our application that, deep in the initialization process, calls the following code:
string strPath = System.IO.Path.GetDirectoryName(System.Reflection.Assembly.GetExecutingAssembly().CodeBase);
string strFile = strPath.Substring(6) + "\\" + FILE_NAME;
Here's the deal. My fellow members and I myself were able to change and build sections of our solution at a higher level, UI and DB for eternity. I, no one else, changed the code above or any code in the same code file (or the project as part of the solution, for that matter.)
However, today, working in a completely different section of my application, I began to get some really strange "out of memory" errors. I'm not sure if this is due to my problem, but I felt it worth mentioning that after rebooting my machine and restarting the VS solution, I now get the following exception when I try to run the debugger test, when the initialization process tries to execute the above code fragment:
: "System.ArgumentException" mscorlib.dll : URI .
, , . , , , , , , , , , .
, , , . , , . , , , , . , .
- , , "" ? , , UI, , , .
- . , , .
- AnkhSVN, , , , , .
- .
- , , . , . , , - / - , , .
. . , , , - .