Closed Luk164 closed 1 year ago
Thanks for the report!
A few questions:
<UnoUIUseRoslynSourceGenerators>false</UnoUIUseRoslynSourceGenerators>
?@jeromelaban
Thanks for the update.
For 1.
, are you still getting the error of #5468 even with Uno 3.7 ?
For the errors you're seeing in 2.
, the only way to get rid of those is to build all projects once, close visual studio and open it again. It's a Visual Studio issue we have no control over, but we expect that .NET 6 will reduce the errors significantly.
@jeromelaban
Screenshots are worth a 1000 words right?
They seem to have persisted with restarts but disappeared when I manually wiped the cache. Also unrelated but ReSharper seems to get a stroke anytime I use UNO. Support ticket exists but it does not look like they are putting much effort into it. Did anyone think about creating a 3rd party plugin for resharper?
Thanks for the update.
dotnet new
? If so can you run dotnet build /bl
and post the msbuild.binlog
file ?@jeromelaban The resharper builder was already disabled, I only use it rarely anyway. I am not very experienced with dotnet CLI so just to make sure I do not mess up can you please post full commands for me to try out?
Regarding the ReSharper, should I add a feature ticket, or is it too expensive to even consider?
Apologies for the command line mistake I fixed it above, but basically, using a command prompt:
cd myApp\myApp.Wasm
dotnet build /bl
This will create a msbuild.binlog
file that you can post here (zipped).
@jeromelaban Here are the logs, 0 errors for both WASM and GTK. 2 errors for GTK with that property group commented out. logs.zip
Thanks for the reports. I've found the issue here, and it's unfortunately related to this Roslyn issue https://github.com/dotnet/roslyn/issues/44596, and is caused by the folder name of your solution (it contains C#
in the path). https://github.com/unoplatform/uno/pull/5978 will work around it in Uno, but it will prevent hotreload from working properly until the path keeps containing a #
.
@jeromelaban Ok, for now I just renamed my projects folder to CSharp, hopefully that will break only some of my projects... Maybe I will add a C# folder with a symlink to CSharp.
@jeromelaban I don't think we can do anything here. Should we close?
Indeed, we cannot do anything we'll have to wait for roslyn updates.
Current behavior
I am getting a LOT of errors and warnings, even though solutions compile and run just fine.
Expected behavior
No errors/warnings.
How to reproduce it (as minimally and precisely as possible)
This is my main layout:
This is my test layout:
Log:
Environment
Nuget Package:
Affected platform(s):
IDE:
Relevant plugins:
Anything else we need to know?
I disabled solution wide analysis on ReSharper. It is a bit frustrating because I really love the idea of the UNO platform, but at the same time it is incredibly difficult to just get an empty template that does not throw warnings and errors at every step, with or without ReSharper.