Issue to Initialize compoment

Question

Issue to Initialize compoment

Peter Liang 3,286

Hi,

How to resolve it below?

Viorel 126.8K Reputation points

2026-04-08T07:34:39.35+00:00

At least rebuild the solution or undo the actions that led to this problem.

Answer accepted by question author

1 additional answer

Your answer

Viorel 126.8K Reputation points

2026-04-08T07:34:39.35+00:00

At least rebuild the solution or undo the actions that led to this problem.

Answer 1

Jack Dang (WICLOUD CORPORATION) 16,115 Microsoft External Staff Moderator

Hi @Peter Liang ,

Thanks for reaching out.

From the screenshot, this looks like a .NET MAUI app rather than an ASP.NET app. The key clues are the App : Application class, the CreateWindow(...) override, and the project target showing something like net10.0-android. In MAUI, InitializeComponent() is generated from the matching XAML file, so this error usually means that link was not created correctly.

To resolve it, please check the following:

Make sure you have an App.xaml file in the project.
In App.xaml, confirm that the x:Class value exactly matches the namespace and class name in App.xaml.cs. For example, if your code-behind is namespace MauiApp10; public partial class App : Application, then App.xaml should have: xml x:Class="MauiApp10.App"
Make sure App.xaml.cs is declared as partial.
Verify that the build action for App.xaml is set to MauiXaml.
Clean the solution, delete the bin and obj folders, then rebuild the project.

If your project is truly ASP.NET or ASP.NET Core, then this App.xaml.cs / InitializeComponent() pattern does not belong there, and the application should instead be configured through Program.cs. In that case, the fix would be to remove this MAUI/XAML-based code from the web project.

Based on the screenshot though, the most likely fix is to restore or correct the App.xaml to App.xaml.cs mapping, then rebuild.

Hope this helps! If my answer was helpful, I would greatly appreciate it if you could follow the instructions here so others with the same problem can benefit as well.

Peter Liang 3,286 Reputation points

2026-04-08T09:26:27.8233333+00:00

I got issue like

The name 'DownloadAndShareFileAsync' does not exist in the current context

due to this call

DownloadAndShareFileAsync("https://abc.com:443/Share_file/download", "Myfile.txt");

while DownloadAndShareFileAsync is existing on cs file below.
Jack Dang (WICLOUD CORPORATION) 16,115 Reputation points Microsoft External Staff Moderator

2026-04-08T10:02:25.6133333+00:00

This error means the method is not visible from the place where it is being called.

Even if DownloadAndShareFileAsync exists in another .cs file, it can only be called directly if it is in the same class, or in another file that belongs to the same partial class.

If the method is in a different class, then it needs to be called through that class or through an instance of it. Also, if it returns Task, make sure it is called with await from an async method.

If you moved DownloadAndShareFileAsync into Code1.cs as a separate class, that would explain the error. In that case, please verify that the namespace and class scope are correct, or call the method through the class where it is actually defined.
AgaveJoe 31,266 Reputation points

2026-04-08T10:33:19.2066667+00:00
It is difficult to provide a solution because the community is currently lacking the necessary context. Peter, to resolve this quickly, please provide the full source code for the file where these errors are occurring.

Specifically, we need to clarify two things:

Was the original InitializeComponent() error resolved, or are you now facing a second, separate error with DownloadAndShareFileAsync()?

The current issue likely stems from a missing using statement or an attempt to call a method without instantiating the class first.

In a previous thread which you marked as solved, the community provided clear instructions on how to instantiate Class1. To avoid a long back-and-forth here, please provide the complete code for both Class1 and the calling file so we can see how you are implementing those instructions.
Peter Liang 3,286 Reputation points

2026-04-09T03:42:52.46+00:00

Thanks. Will revert
Peter Liang 3,286 Reputation points

2026-04-09T06:43:34.2833333+00:00

It is not a success to build the project. Any reason from the following?
Jack Dang (WICLOUD CORPORATION) 16,115 Reputation points Microsoft External Staff Moderator

2026-04-09T08:50:38.4866667+00:00
The new build error about DownloadAndShareFileAsync appears to be a different issue from the original InitializeComponent() question.

InitializeComponent() is related to XAML/code-behind generation, while DownloadAndShareFileAsync is a user-defined method and this new error is usually caused by class scope, namespace, or method visibility. For example, the method may be declared in a different class, outside the expected braces, or not accessible from the place where it is being called.

To keep the discussion clear and make it easier for others to find the right solution, I would recommend opening a new thread for this new error and including:

the full error message

the code where DownloadAndShareFileAsync(...) is called

the code where DownloadAndShareFileAsync is declared

the surrounding class definition

If my answer to your current issue was helpful, I would greatly appreciate it if you could follow the instructions here so others with the same problem can benefit as well.
AgaveJoe 31,266 Reputation points

2026-04-09T09:57:04.6866667+00:00

It is baffling that you would ask for the cause of a compiler warning while simultaneously hiding that warning from the forum. The information needed to help you is right there on your screen, yet you’ve obscured it.

Based on what is visible, you appear to be ignoring the standard requirements for asynchronous programming. The warning likely exists because the code is missing an await, meaning it will run synchronously. Additionally, your method returns a Task without a result, which doesn't seem to align with your goal of sharing a file location.

If you want a solution, you must stop "throwing code over the fence" and expecting the community to guess the context. Please provide all relevant source code in text format and include the full text of the compiler warnings. Without this, we are just wasting everyone's time.

Answer 2

The error occurs because InitializeComponent() is not defined for the App class in the generated partial class, so the compiler cannot find that method name in the current context.

InitializeComponent() is a method generated by the XAML build for UI components (for example, windows, pages, or controls) that implement System.Windows.Markup.IComponentConnector. In the referenced APIs, InitializeComponent() is exposed on WPF-related classes such as ErrorWindow and SessionOverview:

public void InitializeComponent();

If the class does not have a generated XAML partial with that method, calling InitializeComponent() will fail with exactly the error shown.

To resolve the issue:

Remove the InitializeComponent(); call from the App constructor if App.xaml is not meant to have generated UI initialization.
Or, if App is supposed to have XAML-generated content, ensure that:
- There is a corresponding App.xaml file with x:Class matching the namespace and class name of App.
- The project builds XAML correctly so that the partial class containing InitializeComponent() is generated.

In most .NET MAUI templates, the App class does not call InitializeComponent(); only visual elements like MainPage, AppShell, or other XAML pages do. Keeping App as a simple class that sets MainPage (or returns a Window in CreateWindow) without InitializeComponent() is the typical fix.

References:

Share via

Issue to Initialize compoment

1 additional answer

Your answer