>>Thus, it does come down to the fact that if the project does not have Debug Info checked, the line numbers are not included. And this is what I thought at the top of the thread.
>>
>>I don't include the Debug info not because I am concerned about someone getting the source. I don't care. But the size of the EXE will be much greater. Currently (without the debug info) the exe is about 13.5 MB (13,5 for euro). I think I tested once including the debug info and the size almost doubled. Many of my users keep the exe on the server and load it from the desktop shortcut. Therefore, their load time will be doubled. Many ppl won't be happy.
>
>So what... I routinely churn out executables of 35+ megabytes, and the launch speed is not an issue. It's more a matter of what gets loaded up front - how heavy are your global objects, how much of it is created immediately and how much is instantiated on first use, how much SQL traffic does it involve, how many trips to server etc etc. I was surprised with how much time can some of these things take, and which things influence the time. The team in general spent lots of time profiling, and the speed improved a lot from the time when the exe was just 20M.
>
>That being said, the exe is copied to %temp% (whenever missing or older than one in app root) and run from there - that's the job of the launcher. That's the most influencing speed factor.

For now, just because I am troubleshooting this problem, I won't change the app to include debugging code. I will see how and where to "insert" a try/catch instead.