Is it normal when R# reports an error but VS 2012 doesn't? The error shows up during runtime

I came across an issue where R#7.1.1 reported an error but the app compiles fine.The app is an MVC asp.net. The controller returns a model of type iQueryable but the view is casting it to iPagedList. iPagedList extends IEnumerable. Library is at https://github.com/TroyGoode/PagedList
View: @model IPagedList<SomeType>

There's a mismatch which R# reported as an error but VS didn't but the mismatch was reported during runtime.

It's beneficial that R# reported the issue early on but I was wondering if this was the intended action from R# or it's a bug if VS didn't report it? I mean is it OK for R# to do more than VS?

3 comments
Comment actions Permalink

Sounds fairly standard to me. If R# didn't do more than VS, there wouldn't be much point in buying it!

0
Comment actions Permalink

I am talking about flagging errors when VS doesn't. I have been using R# for years and this doesn't standard to me.

Of course R# does more in other areas!

0
Comment actions Permalink

R# does a lot more analysis of your code than VS, so it's not surprising that it finds more problems. That's a large part of R#'s appeal!

0

Please sign in to leave a comment.