🚧 Add check for VM to test for Longpath#255
Conversation
|
@Arlodotexe I'm more confused now, looks like long paths are already enabled... @jeromelaban any ideas on what's going on with the DirectoryNotFound long path for the Xamarin generator?
|
Yes, this is generally cause by the fact that Xamarin projects use Uno.SourceGenerationTasks because of their supported C# version (7.3, in general). Given VS 2022 is used, you can switch it to use Roslyn's embedded generation by adding this to the csproj files: <PropertyGroup>
<UnoUIUseRoslynSourceGenerators>true</UnoUIUseRoslynSourceGenerators>
</PropertyGroup>Note that |
|
@Arlodotexe I know you were tinkering with updating Uno to the latest version as well. Did you try this <PropertyGroup>
<UnoUIUseRoslynSourceGenerators>true</UnoUIUseRoslynSourceGenerators>
</PropertyGroup>I know we had some concerns on overlapping source generators between Uno and Labs, eh? |
|
Closing this as we now know the VMs already have long-path support enabled, so that's not the issue. Trying some things out in the #211 PR now. |
Doing a test to see if windows latest vm has long path enabled already, see actions/runner-images#1052