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 solution with 4 projects, 3 in C# and 1 in VB, and while Visual Studio 2010 catches basic syntax errors in real time, many other errors do not disappear once they are fixed, but until I rebuild the solution.
With pure VB solutions I had never seen this behaviour.
Your insight is appreciated.
I’m using Visual Studio 2008 But I’ve worked with 2010.
Syntax errors are a lot easier to catch and this is done in not only 2010, but 2008 as well. If you’re missing a semicolon or a bracket, the text EDITOR is pointing it out for you. The error list is something that the compiler is telling you to fix. Unfortunately, the compiler doesn’t have real-time capabilities. (that’d be too cool.)
The editor is taking care of basic syntax errors (which is do-able in real time) but logical errors or implicit casts cannot be detected until you go through it with the compiler. It’s not really much of a reason of why you need to rebuild to update the list, you always rebuild. It’s the only way you know for sure that you’ve fixed the error or not. I find myself habitually pressing: ctrl+s, f6, f5.
I hope this answers your question a bit, there is nowhere that explicitly says why you need to rebuild to update the error list, but that’s just the way it is. ^^
Happy coding!