R# 4.0.747 not merging .aspx with code-behind?

If I turn on solution-wide analysis I get lots of errors that are caused
by R# not picking up properties declared in code-behind files. The code
itself compiles without errors.

In case it might be relevant to the cause, this is with an MVC (preview
2) project.

I should also mention that R# detects lots of issues that the C#
compiler itself misses - very impressive. It'd be great if these errors
could make it into the Task List window too. See
http://www.mertner.com/morten/?p=29 for details on this.

Yours,
Morten


2 comments
Comment actions Permalink

Hello,

It'd be great if these
errors could make it into the Task List window too.


Errors and tasks are very different in their handling, so is it really a
good idea to mix them up?

If you're working without Solution-Wide Analysis, then the errors are listed
on the Error Stripe, to the right of the text editor, and the overall status
of the file is highlighted in the top-right corner. In this mode, R# has
no information about the errors in other files, so there's no shared list.

With Solution-Wide Analysis turned on, you have the full list of all the
errors found in the current solution.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0
Comment actions Permalink


>> It'd be great if these
>> errors could make it into the Task List window too.


Errors and tasks are very different in their handling, so is it really a
good idea to mix them up?


I'd like to have them show up in the task list window where all the
compiler errors and warnings get listed, although preferably on a
tab of their own rather than mixed in with what the compiler produces.

If you're working without Solution-Wide Analysis, then the errors are
listed on the Error Stripe, to the right of the text editor, and the
overall status of the file is highlighted in the top-right corner. In
this mode, R# has no information about the errors in other files, so
there's no shared list.


Note that in this case the compile worked but the solution produced a
run-time error. As such it is something that must be fixed and it'd be
great if this was highlighted somehow.

With Solution-Wide Analysis turned on, you have the full list of all the
errors found in the current solution.


For performance reasons I tend not to turn this on.

Yours,
Morten

0

Please sign in to leave a comment.