February 6, 2023, 5:19pm
When exporting the help file “Overview 3D Primitives” when VL.Stride is referenced as source package the following build errors happen:
Mostly unresolvable dependencies. This might be helpful:
04:45PM - 23 Jun 17 UTC
12:07AM - 20 Dec 17 UTC
VS 2017 Update 3 preview
I'm getting similar errors all the time inside Visua
… l Studio. There is obviously a problem somewhere, to the point where nuget seems to be unusable...
Unable to satisfy conflicting requests for 'Company.Module': externalProject/Company.Module (>= 220.127.116.11) (via project/Company.Testing.Framework 0.1.0), Company.Module (>= 18.104.22.168) (via project/Company.Framework 0.1.0-alpha), Company.Module (>= 22.214.171.124) (via project/Company.Framework.Services 1.0.0) Framework: (.NETCoreApp,Version=v2.0)
Unable to satisfy conflicting requests for 'Company.Contracts': externalProject/Company.Contracts (>= 126.96.36.199) (via project/Company.Testing.Framework 0.1.0), Company.Contracts (>= 188.8.131.52) (via project/Company.Framework 0.1.0-alpha), Company.Contracts (>= 184.108.40.206) (via project/Company.Module 220.127.116.11), Company.Contracts (>= 18.104.22.168) (via project/Company.Framework.Services 1.0.0), Company.Contracts (>= 22.214.171.124) (via project/Company.Contracts.Framework 126.96.36.199) Framework: (.NETCoreApp,Version=v2.0)
In the first case, it's says it's conflicting because everyone has the same >= 188.8.131.52 dependency
In the second case, >= 184.108.40.206
I'm no expert, but I think it's a bug when nuget reports that there is a conflict because everyone is asking the same version...
I don't have a repro for this as it's custom code, however, I did make sure that everyone is targeting .net standard 2.0 libraries to at least remove that as a potential conflict.
Please help... I'm noticing there is a very high number of open issues. I'm still crossing my fingers that this can be somehow solved.
It happens when a project and a nuget of the same dependency are referenced, but that is just a guess. Unfortunately, this issue is high urgency and currently blocking a project.
Any idea when or how quickly this might be resolved? We need to be able to build a .exe quite soon and are too far into switching to the new 2022.5 to go back to 2021.
Is it realistic to get someone to take a look till the end of this week or early next week?
Thank you, devvvvs!
February 7, 2023, 9:11pm
@seltzdesign for inquiries that require the commercial fast lane, please get in touch via email@example.com or hit me up on the chat to work something out.
February 8, 2023, 4:29pm
This works in the latest preview-573, thanks for fixing it so quickly.
Two issues remain, however. When starting VL.Stride.sln from visual studio and trying to export, a file access violation happens. It looks like the build process wants to copy the vvvv binaries that are currently in use:
But you can then close vvvv and open the solution in visual studio. It will display some errors for linked shader, if in use, but you can ignore them.
The only issue then is that the file geometry3sharp.dll is missing and there are some errors related to that. This can be fixed by copy&pasting one line in the file VL.Stride.vl.csproj and make it into:
<Reference Include="vvvv.geometry3sharp" HintPath="C:\SomePathToBinary\vvvv_gamma\vvvv.geometry3sharp.dll" />