Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a WinForm app. I compile it, double-click on it. Predictably, csc.exe kicks in, then goes away, and the application comes up.
I am assuming that at this point the application has been jitted, so no reason for csc.exe to kick in ever again.
I then quit the app and start it again. I see csc.exe kick in again.
What’s going on?
Are you using serialization at all? I believe that will build a temporary assembly in some cases. Anything similar in your app?
Note that the JIT compiler is unrelated to csc, so that shouldn’t be anything to do with it.