Ashkan Mobayen Khiabani Ashkan Mobayen Khiabani - 3 months ago 35
ASP.NET (C#) Question

The name '__o' does not exist in the current context

I just installed Visual Studio 2015 and opened my asp .net project that I was working on. I'm receiving many errors (all exactly the same) as below:


Error CS0103 The name '__o' does not exist in the current context


Well actually I don't have any variables named __o and the code works like a charm (error is invalid) but what bothers me is that I'm not able to see when my code really has a error as it goes somewhere in this list and I should check the whole list.

enter image description here

Answer

I found out that if I choose Build Only instead of Build + IntelliSense the errors (that are related to intellisense) will go away.

enter image description here

Update 1: The Reason

The reason that this is happening is that for codes like this:

<% if (true) { %>
    <%=1%>
<% } %>
<%=2%>

In order to provide intellisense in <%= %> blocks at design time, ASP.NET generates assignment to a temporary __o variable and language (VB or C#) then provide the intellisense for the variable. That is done when page compiler sees the first <%= ... %> block. But here, the block is inside the if, so after the if closes, the variable goes out of scope. We end up generating something like this:

if (true) { 
    object @__o;
    @__o = 1;
}
@__o = 2;

The workaround is to add a dummy expression early in the page. E.g. <%="" %>. This will not render anything, and it will make sure that __o is declared top level in the Render method, before any potential if (or other scoping) statement.

Update 2: Getting rid of this error without loosing other intelliSense errors

Click on the filter button on the top left corner of the error list panel and uncheck the CS0103 which the error code for the: The name '__o' does not exist in the current context and these errors will not be shown anymore and you can still have other intelliSense errors and warnings:

enter image description here

Comments