error : Member modifier 'static' must precede the member type and name UnoApp1 (net8.0-desktop)

[blackholeearth]

Current behavior

i created new project. Edit Proj File ->
disabled everyplatform except --desktop (which i assume is wpf) ..

i only want it to work on wpf ... its not running...

i see this error

Error (active)	
CS1585	
Member modifier 'static' must precede the member type and name	UnoApp1 (net8.0-desktop)	

D:\..........\UnoApp1\UnoApp1\obj\Debug\net8.0-desktop\Uno.Extensions.Markup.Analyzers\Uno.Extensions.Markup.Analyzers.Generators.HotReloadModuleInitializerGenerator\UnoApp1.MarkupModuleInitializer.g.cs	13	

question?
does this work for only wpf ,,,, witout installing maui workload..

currently i only installed desktop workload.
win11 latest sdk

edit
i have installed maui .. i am still getting error..

i think this is related to generators.. its generating buggy code..

Expected behavior

it should work..

How to reproduce it (as minimally and precisely as possible)

create a uno porject > press f5

Environment

windows 11

NuGet package version(s)

Affected platforms

Skia (WPF)

IDE

vs 2022 - v17.11.5

Relevant plugins

No response

Anything else we need to know?

No response

[DevTKSS]

did you run uno-check successfully?

[blackholeearth]

the point is .. i dont wanna download maui or android sdk s which i will not use ....
i want to start lean just with desktop platform wpf ...... with LESS GB downloads to waste...

if i like uno platform... i might go ALL in... Download those big SDK Files,,, LATER..

---

did you run uno-check successfully?

https://platform.uno/docs/articles/external/uno.check/doc/using-uno-check.html?tabs=windows#command-line-arguments

cmd:: uno-check target skiawpf

result:: it says all good.. but i cant run??????

build result:: F5

[blackholeearth]

i think this is full command which i dont need... but here you go...

cmd:: uno-check

yes it finds missing things .

[DevTKSS]

Dont know if this is even possible to not do, but could you update your visual studio at least (e.g. from its installer) and install the uno extension from the vs marketplace? this could maybe add the needed uno sdk, which seems to also be skipped
if this not works, someone of the uno team might have a look on your case, dont know if it is possible to do what you want

[DevTKSS]

Just read "winforms" somewhere in your text...
Dont know if you read this already in docs or similar, uno is mostly building on top of winui and wpf is supported via skia as far as i know (no .net Framework, check uno docs for that). I am normally building to desktop target instead of directly windows, but the main difference beside the targets themselves you should look into is the markup for ui you want to use (in my own opinion xaml has more resources so far) which is xaml or c# and the application structure you might want to use. For the structure, you can also choose codebehind, but very less guides are doing so and the mvvm might be a good start. Then you will have to choose your ui styles library which is material 3 (google made) or fluent, but as far as i did see, you have more options when choosing material because of the theme resources you can define more freely

[DevTKSS]

@blackholeearth would you mind to maybe add comments to your issue here instead of changing its title every few hours/every day? What you are described later is not at all matching the title so maybe you should update this and also add the issue you are confronted with at latest state here as comment for possible uno team members to better& more quickly see whats up to this issue, so they can help you at best they can

[blackholeearth]

issue is unrelated to wpf ... ,, i still see that error , even if i create new uno App from Scratch... i think its about nuget dll version mismatch.....

uno cant understand that...

i just gave up this. wont use ... :((

trying to learn maui CS markup. from james monte-magno from youtube... ...

can close this if you want...

[jeromelaban]

@blackholeearth It looks like you're having some sort of .NET version mismatch when building. We're currently upgrading our experience to make uno-check more specialized to the solution you're building, but could you try running this:

uno-check --tfm net9.0-desktop

This will run only for the desktop and not install everything else. The "wpf" target you've been using has been deprecated in Uno 5.3, but our documentation is lagging a bit.

Once you've run it, can you try to run the following in the folder that contains the csproj:

dotnet build /bl

Then post the msbuild.binlog file as a zip file here?

Thanks!

[blackholeearth]

msbuild.zip

[jeromelaban]

Thanks for the update!

It looks like there's something in the environment that causes this issue to happen, and could you go there:

And post the contents of the file that opens when you double click on it?

Thanks!

[blackholeearth]

//------------------------------------------------------------------------------
// <auto-generated>
//     This code was generated.
//
//     Changes to this file may cause incorrect behavior and will be lost if
//     the code is regenerated.
// </auto-generated>
//------------------------------------------------------------------------------

namespace UnoApp1
{
    [global::System.ComponentModel.EditorBrowsableAttribute(global::System.ComponentModel.EditorBrowsableState.Never)]
    ınternal static partial class __MarkupModuleInitializer
    {
        [global::System.Runtime.CompilerServices.ModuleInitializer]
        public static void Initialize()
        {
            #if !IS_HOT_RELOAD_DISABLED && (DEBUG || IS_HOT_RELOAD_ENABLED)
	var isHotReloadEnabled = true;
#else
	var isHotReloadEnabled = false;
#endif
	global::Uno.Extensions.Markup.Internals.ModuleConfiguration.Configure("UnoApp1", isHotReloadEnabled);        }
    }
}

photo

[jeromelaban]

This is a very interesting bug! I'm guessing that you're on a Turkish system, which may explain why there's the ınternal instead of internal.

It should be easy to fix, we'll take a look and push a new update to our Uno 5.5.

Thanks for the troubleshooting!

[blackholeearth]

so should i wait new vs2022 uno extension update??

or just wait it in the nuget packages??

[jeromelaban]

It will be an uno.sdk package update.