The answer seems so obvious that I'm thinking I'm not understanding your problem. You evidently have a form (Windows Forms?), within which you call a compiler.I would think that you would await the result of the compilation to see how the form should react - whether it's successful or resulted in an error. Can you explain a bit more clearly?
Okay - thank you for clarifying. I think perhaps now I see what you mean.
In general, for a problem like this I try to structure it as simply as possible. Here is what I'm envisioning, for your scenario: When you click the button that starts the build, you have a method that sets up a callback delegate or event (that the build process will use to notify you when it is done), and then spins off a distinct process to do the building (compiling, linking, whatever) asynchronously. After the build Task is done (whether it succeeded, or aborted), it should notify your application with the results.
Once your application starts that method, it would immediately return to waiting for user interactions. The build process carries on asynchronously.
If you wanted to get fancier, you could structure the build as a task for each module, with dependencies respected by having it invoke the build of module B only after module A is successfully built, if B depends upon A, otherwise start the builds of A and B in parallel. And with each build task, perhaps it could send an Event back to your user-interface code to advise the user of it's progress.
The callback method (or whichever technique you decide to use for the build process to give it's results back to you) would include a parameter for it to indicate whether it was successful, or failed. If failed, it needs to say what failed. An alternative method would be to simply have a different callback (or event) for success, and for failure.
So, the real metal of your code is in how you call your build tools and get the results back. Obviously, it is essential that you get a result back that tells you if it failed, and what that failure was.
To get into more detail, you'd need to provide me with detail on what compiler you're calling, and how you're calling it and getting it's results back. As far as how to structure your C# code -- there're multiple ways depending upon which code techniques you want to use. The Task library, for example, has a very nice API for creating Tasks that run sequentially, in parallel, provide feedback, etc.
Otherwise, I hope this helps you a bit - best of wishes,
JH
Submit an article or tip