Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
Rider extension fails to recognize referenced projects with åäö
Options
Previous Topic Next Topic
Peter Osterdahl
#1 Posted : Friday, August 22, 2025 9:23:24 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 1/13/2025(UTC)
Posts: 4
Location: Sweden

Was thanked: 1 time(s) in 1 post(s)
Hi,
I use Rider 2025.1 with ncrunch 5.16.0.5

One project "DomainApi" references another with:
Code:
<ProjectReference Include="..\DomainApi.Försäkring\DomainApi.Försäkring.csproj" />

in Ncrunch.DomainApi_AnalysisBuild.xml this looks like:
Code:
<ProjectReference Include="..\DomainApi.F??rs??kring\DomainApi.F??rs??kring.csproj" />

and the build fails with
Quote:
The type or namespace name 'Försäkring' does not exist in the namespace 'Fuse.Features.DomainApi' (are you missing an assembly reference?)


This does not happen if I run in Visual Studio.
The project builds fine in all other pipelines, Rider, visual studio, dotnet build.

Any suggestions?
//Peter
Back to top
Remco
#2 Posted : Saturday, August 23, 2025 12:17:23 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,380

Thanks: 997 times
Was thanked: 1343 time(s) in 1246 post(s)
Hi, thanks for sharing this issue.

The localization issue here looks like a red herring. The Ncrunch.DomainApi_AnalysisBuild.xml file is created when the 'Write build log' setting is enabled, and it looks like this file is defaulting to ASCII encoding for some reason (it shouldn't), but this issue doesn't seem to be related to the build problem you've encountered.

I've tried setting up a local test project referencing another project with the same name, and it's working fine on my side. I think there's something else about this project reference that's causing this problem. Are you able to reproduce it with a small sample solution you can share with me?
Back to top
Peter Osterdahl
#3 Posted : Saturday, August 23, 2025 8:58:47 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 1/13/2025(UTC)
Posts: 4
Location: Sweden

Was thanked: 1 time(s) in 1 post(s)
Thanks for quick response!
I will try to create one on monday.
Back to top
Peter Osterdahl
#4 Posted : Friday, September 5, 2025 8:00:26 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 1/13/2025(UTC)
Posts: 4
Location: Sweden

Was thanked: 1 time(s) in 1 post(s)
Hi, sorry for slow reply.
I have tried to replicate this in a new solution but there it works fine. In my old solution it still fails and as I said it works in all other pipelines and even tunning Ncrunch in visual studio.
Back to top
Peter Osterdahl
#5 Posted : Friday, September 5, 2025 8:22:58 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 1/13/2025(UTC)
Posts: 4
Location: Sweden

Was thanked: 1 time(s) in 1 post(s)
Hi again!
The weirdest thing happened. I compared my test project settings to the big solution and noted that the only difference was that in my solution I had Use build configuration set to Debug. I did set this for the test project and it failed to build with the same error as in my big solutiion. Then I restarted Rider for the test project but then it built anyway...
So I removed the Use build configuration in my solution, rebuilt in ncrunch and everything was ok. Then I set it back to Debug and solution still builds in ncrunch...

So something must have been cached somewhere.
Cheers
Peter
Back to top
1 user thanked Peter Osterdahl for this useful post.
Remco on 9/5/2025(UTC)
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.030 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download