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

Notification

Icon
Error

Project cannot be built
Dirk Maegh
#1 Posted : Thursday, July 11, 2024 12:58:00 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/30/2016(UTC)
Posts: 53
Location: Belgium

Thanks: 7 times
Was thanked: 7 time(s) in 7 post(s)
Hi, I have a solution where NCrunch cannot build my Graphql client project.
Also the unittests project does not reference that project, but NCrunch does not attempt to build it.

Where could I provide the sample project please ?

Thx,
Dirk
Remco
#2 Posted : Thursday, July 11, 2024 1:09:19 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 955 times
Was thanked: 1283 time(s) in 1190 post(s)
Hi Dirk,

We've done no work to support this kind of project type.

You can submit small samples in ZIP form through the NCrunch contact form.
Dirk Maegh
#3 Posted : Thursday, July 11, 2024 3:37:22 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/30/2016(UTC)
Posts: 53
Location: Belgium

Thanks: 7 times
Was thanked: 7 time(s) in 7 post(s)
Sample submitted.

It's a regular project, with a regular nuget library.
Remco
#4 Posted : Thursday, July 11, 2024 11:15:02 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 955 times
Was thanked: 1283 time(s) in 1190 post(s)
Thanks for sharing this sample.

The problem is caused by a missing dependency. In the project file, some of the Graphql files are explicitly removed from the project:
<ItemGroup>
<None Remove="GetAllOthersV1.graphql" />
<None Remove="GetOneContractVersionV1.graphql" />
</ItemGroup>

As a result, NCrunch doesn't copy them to the workspace when building the project. This causes the build to fail with a very obscure error.

You'll either need to avoid removing these files, or add them to NCrunch's 'Additional files to include' setting.
Dirk Maegh
#5 Posted : Monday, July 15, 2024 5:34:23 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/30/2016(UTC)
Posts: 53
Location: Belgium

Thanks: 7 times
Was thanked: 7 time(s) in 7 post(s)
Thanks. That was the culprit. I would have never known that from the current ncrunch output. I had to contact you through this forum to find out. Maybe something that could be improved ? (It's an excellent product and delivers great quality - don't misunderstand me ;)
Remco
#6 Posted : Monday, July 15, 2024 6:43:46 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 955 times
Was thanked: 1283 time(s) in 1190 post(s)
Where we can, we do try to get NCrunch giving useful error messages.

In this particular case, the error was coming from a nuget package - not from NCrunch. The only way for us to improve on this error would be to introduce special handling for just this Nuget package. Given that there are a lot of Nuget packages out there, you can probably understand our limitations. If it hits this forum a lot, then we may end up doing just that.
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.034 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download