Rider 2019.1.3 "cannot resolve View" when path is in subfolder

Answered


 

As shown in the screenshot, this is the original clone of nopcommerce https://github.com/nopSolutions/nopCommerce 

the view exists as shown on the left(highlighted file) but rider says cannot "cannot resolve view xxx". The project can be successfully built.

Any idea on this? Thanks! 

11 comments
Comment actions Permalink

I have this same problem.  Must be a bug.  Should a ticket be opened for this?

1
Comment actions Permalink

Hi all!

Could you please try to update Rider and then disable this inspection once or change its severity? Please let me know if it helps.

0
Comment actions Permalink

That seems to work.  Thanks!

Edit:  Since I disabled the error, the error won't show up even if the path string truly is wrong, but this is good for now.

0
Comment actions Permalink

I'm having sort of the same issue

It doesn't happen in VS

0
Comment actions Permalink

Hi Chr4000

Thank you for contacting us.  Have you tried to disable inspection as it described above? 

0
Comment actions Permalink

Hello. Yes I have. And it works. 

But why is it an error with inspection enabled? Shouldn't it work, when it works fine i visual studio?

0
Comment actions Permalink

I'm not sure that your error has the same cause than the first one. 

We could analyze this situation but in this case, I need more details about it: 

 - what is your OS, version of RIder and type of project? 

 - could you reproduce this issue in a new project or it is specific? 

- is it possible for you to share your solution with us for analyzing it? 

Thank you in advance for answers. 

0
Comment actions Permalink

I'm using windows 10 64 bit (version 1909), and rider is 2019.3 EAP4 (was also present in 2019.2). The project is a .net core 3 MVC project.

I've seen it in a couple of solutions. but this one: https://github.com/skoruba/IdentityServer4.Admin/tree/dev shows the issue. 

0
Comment actions Permalink

Hi! 

I wasn't able to reproduce this on the mentioned solution, and I don't have any errors.

- Could you please try the latest EAP 6? 

- Have you added missing references? 

- What is your version of .net Core? 

Also, I couldn't find any .net Core 3.0 projects in the solution. Have you changed the target framework manually? 

 

0
Comment actions Permalink

The newest EAP seems to have fixed the issue with MVC atleast.

Blazor still fails. It says I have 18 errors, even though it works fine in VS

 

Anyway. The project I linked has to be the DEV branch. Then the project is a .net core 3 app (but it is not blazor, only MVC).

0
Comment actions Permalink

Hi, 

Thank you for your clarification. This is a known issue RSRP-473924 that has not been fixed yet. Feel free to follow it and vote to raise its priority. 

0

Please sign in to leave a comment.