Jérôme Laban

@Zerachiel01 this issue is related to [this VS issue](https://developercommunity.visualstudio.com/t/Building-a-cross-targeted-project-with-m/651372), and while this is a problem, with the latest changes we pushed a few days ago, you can get around testing...

You mentioned that those projects may not be default anymore, that's why I opened that issue ;) If it's building properly, we can close that issue.

I agree. It's causing more trouble than the readability it improves.

## Note for contributors Adding AOT support varies between platforms: - Wasm generally requires to have [profiled AOT enabled](https://platform.uno/docs/articles/external/uno.wasm.bootstrap/doc/runtime-execution-modes.html#profile-guided-aot) to avoid very long build time - Windows does not support...

Interesting. In this particular context, the global.json in the folder should be enough, as the issue reported for `visualStudioSdkWorkaround` should only be valid for VS and 8.0.100. Does restore work...

Thanks. Which version of visual studio are you running, and which version of the dotnet sdk are you using?

Thanks. This is very curious that VS is also showing this error. Could you show it in the context of VS? Also, do you have any custom feed that requires...

Thanks. Can you also post the generated folder in a zip here?

Yes, we're likely missing the Lottie dependency that only comes from material, but should always be added when extensions are select.

It is likely that when toolkit is selected, we should be including lottie as well. We cannot have it as a transitive dependency from the toolkit because of platform constraints....