Application export of patch that uses .csproj then replaced by .dll

vvvv gamma bug
1

Hi, I came across something that is possible a bug:

  1. Create a VL.File.vl create VL.File.csproj`
  2. Add csproj as dependency, add some static method
  3. Save
  4. Remove csproj, and add .dll
  5. Export app

see:

 Found multiple publish output files with the same relative path:  
   - obj\Release\Avalonia\VL.Avalonia.dll  
   - D:\VVVV\__avalonia\VL.Avalonia\src\VL.Avalonia\lib\Debug\net8.0\VL.Avalonia.dll

In patch i found such traces:

<p:NodeReference LastCategoryFullName="VL.Avalonia.AppBuilderExtensions" LastDependency="VL.Avalonia.csproj">
  <Choice Kind="NodeFlag" Name="Node" Fixed="true" />
  <CategoryReference Kind="AssemblyCategory" Name="AppBuilderExtensions" NeedsToBeDirectParent="true" />
  <Choice Kind="OperationCallFlag" Name="CreateDefault" />
</p:NodeReference>

Witch leads to:

Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "VL.Avalonia", "VL.Avalonia\VL.Avalonia.csproj", "F4B04E9C-0E68-F4DC-0072-0CAE742772C4"
EndProject
Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "VL.Avalonia", "D:\VVVV\__avalonia\VL.Avalonia\src\VL.Avalonia\src\VL.Avalonia.csproj", "B1EF32BA-E778-90CE-27D9-AC710CB53E9F"
EndProject

in .sln

P.S. seems it’s something deeper since replacing .csproj vs .dll did’t help
P.S.S. adding whole thing to new vl file as deps resolved error

2

are you saying the .csproj or .dll has the same name as your .vl file? that would lead to naming collisions because the .vl file will also be translated to a .dll of that name then. is that what you ran into?

3

I suspect yes, but in context that I have same name of VL.Patch as I’m exporting. If I add that VL.Patch to another Patch everything seems in order

So collision happens if export VL.Patch.vl witch has VL.Patch.dll as a dependency…