7

I have a solution where the file name and line number of the error isn't displaying in the Error List, unless I have the file open.

I have another solution where just three errors show up when I build the solution, and they do display the line number and file. If I open the file with the error, another 3 errors pop up, but when I close the file, all the errors disappear until I rebuild again.

The only issue I've seen from googling is that the path is too long or too weird, but I don't think this is an issue. Path is C:\TFS\Apps\Rel_2013.7.1\S3\CrmSvcUtil Extensions for the solution that is partially working and C:\TFS\Apps\Rel_2013.7.1\S3 for the one that doesn't work at all.

Edit 1

Just to make it clear what I'm seeing: I have multiple projects in my solution but one of them doesn't show the file or line number of the error unless the file is open.

In this screen shot I've added two dumb errors, each in a different project, and have built the solution. The Test Project displays the file and line number as expected. The Common project isn't displaying the file or line number error even though it should and does when I actually open the file with the error in it. The Warning isn't displaying the file because it is a project level warning, not a file level warning, this makes sense.

Example Error

When I open the file with the error the file name and the line number do show up, but on a different error:

Error displays along other error

If I change the int to a string, only the line numbered error is removed. I actually have to build in order for the error to be removed.

Improve this question

4 Answers 4

Reset to default
4

I had the same issue on projects that are using legacy Workflow framework V3. Interesting to note, that if project has only compiler warnings, the file and line are shown correctly, but error causing all warnings and errors refer to file C:\Windows\Microsoft.NET\Framework\v4.0.30319\Workflow.Targets(121,5):

The nasty workaround that I found is

  1. Unload the project
  2. Comment out at the bottom of the .csproj file the line
<Import Project="$(MSBuildToolsPath)\Workflow.Targets" />
  1. Reload the project and compile it. Compiler errors will be shown with correct file name and line numbers.
  2. Fix compiler errors
  3. Again unload the project, restore Workflow.Targets import and reload the project.

The similar solution was reported to MS https://connect.microsoft.com/VisualStudio/feedback/details/797056/state-machine-workflow-projects-using-vs-2012

If you forget to restore Workflow.Targets import, there will be run-time errors like 

System.Workflow.ComponentModel.Compiler.WorkflowValidationFailedException: The workflow failed validation.
   at System.Workflow.Runtime.WorkflowDefinitionDispenser.ValidateDefinition(Activity root, Boolean isNewType, ITypeProvider typeProvider)
   at System.Workflow.Runtime.WorkflowDefinitionDispenser.LoadRootActivity
Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

1

Certain errors such as schema errors are reported but don't affect the final build. Depending on the file you may/may not see errors unless the file is open. Here are some things to try

  1. Build in debug/release mode and see if that changes things for either build.
  2. Change the MSBuild Project Build Output Verbosity (Tools-> Projects & Solutions -> Build and Run) to see if that has an effect. I surmise that will only add to the output but not affect on the Error List Window.
  3. Does this happen in VS2013? That might provide a clue.

It is not unusual there to be differences between output builds and intellisense errors as reported.

Improve this answer

2 Comments

Step 1 didn't do anything... Step 2 did something weird. It was set as minimal, and I changed it to normal. The error showed line 121, column 5 (the actual error should have been line 20, col 55), but the file was C:\Windows\Microsoft.NET\Framework\v4.0.30319\Workflow.Targets Warnings also showed up for the file as well The element 'ItemGroup' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003' has invalid child element 'WFCompilationOptions' as well as 8 other similar errors just different child element names...
Have you found any workarounds? I also have no file and lines shown in error list and output shows reference to Workflow.Targets 5>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Workflow.Targets(121,5): error : An object reference is required for the non-static field, method, or property
1

Sounds to me like you are just looking at errors that are generated by the IntelliSense parser. Which only looks at open files. When you close the file then those IS errors will be removed from the list again. Seeing the error list change after you've built and open a file is similarly explained, the IS parser takes over again.

This is all by design, get ahead by just fixing the errors.

Improve this answer

3 Comments

Nice thought NoBugz. :-)
It is the same error, it can't be merged because the original didn't have the file+line info. There's no hint whatsoever in your question that could explain why that's missing. If you get warnings from a .targets file then you need to document them.
Nearly a full year later, I finally have the answer for this question! Thanks for your suggestion though...
0

Michaels solution didn't work for us in May, 2018.

Visual Studio 2017 + .NET 4.7.2, and C# 7.2, old Workflow service.

It was inline variable declerations added: int.TryParse(s, out int queueId);

Went back to pre-defining variables and it compiled successfully.

int queueId = 0;
int.TryParse(s, out queueId);

I would ascertain Microsoft has a bug.

Sample Errors:

 C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Workflow.targets(121,5): error : Invalid expression term 'int'
 C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Workflow.targets(121,5): error : ; expected
 C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Workflow.targets(121,5): error : Invalid expression term ')'
Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.