146

I am a beginner when it comes to programming but I was sure that one of the universal rules was that a program starts with Main(). I do not see one when I create a WPF project. Is Main() simply named something differently in WPF?

HireThisMarine
  • 241
  • 5
  • 12
Juice
  • 2,860
  • 4
  • 22
  • 20
  • 15
    You can get the equivalent functionality by overriding OnStartup in App.xaml.cs. StartupEventArgs.Args contains the commandline arguments. – Foole Apr 23 '10 at 05:14
  • 2
    @Foole, no, you can not, see [this](http://stackoverflow.com/q/22460116/1997232) question. – Sinatr Mar 24 '14 at 08:21

8 Answers8

153

The Main() method is created automatically. If you want to provide your own you have to (tested in VS2013, VS2017 and VS2019):

  • Right-click App.xaml in the solution explorer, select Properties
  • Change 'Build Action' to 'Page' (initial value is 'ApplicationDefinition')

Then just add a Main() method to App.xaml.cs. It could be like this:

[STAThread]
public static void Main()
{
    var application = new App();
    application.InitializeComponent();
    application.Run();
}
Andreas Kahler
  • 2,283
  • 1
  • 17
  • 17
  • 3
    [STAThread] sets the COM threading model for your application. Usually you just set it to STA and don't have to worry what it does exactly. In case you are interested, check out https://msdn.microsoft.com/de-de/library/system.stathreadattribute(v=vs.110).aspx – Andreas Kahler Mar 16 '17 at 13:04
  • 2
    Don't do this! This will permanently break StaticResources defined in App.xaml in Styles in the Designer for the whole project. – Himbeer Jul 06 '20 at 17:20
  • 2
    App.xaml disappears after trying to click Page in Build Action – user3625699 May 29 '21 at 21:49
  • What IDE and project type are you using @user3625699? – Andreas Kahler May 30 '21 at 09:31
  • 1
    @AndreasKahler An error has occurred while saving the edited properties listed below: Build Action One or more values are invalid. Cannot add 'App.xaml' to the project, because the path is explicitly excluded from the project (C:\Program Files\dotnet\sdk\6.0.100-preview.4.21255.9\Sdks\Microsoft.NET.Sdk.WindowsDesktop\targets\Microsoft.NET.Sdk.WindowsDesktop.targets (88,5)). And then App.xaml disappears. I am using casual WPF application template on .NET 6 preview 4 and Visual Studio 16.11 preview 1 – user3625699 Jun 01 '21 at 23:53
  • @user3625699 You are not the only one with this problem. google for "because the path is explicitly excluded from the project". Not sure if there is an easy solution though. Please let us know if you find one! Thx – Andreas Kahler Jun 02 '21 at 08:16
  • 3
    @AndreasKahler yes there is a solution for having Program.cs as startup object in a WPF application. 1. add `Program.cs` class 2. add the code in this answer to `Program.cs` 3. in project properties, choose `ProjectName.Program` as `Startup object` – user3625699 Jun 03 '21 at 15:13
80

It is generated during build, but you can provide your own (disambiguating it in project-properties as necessary). Look in obj/debug for an app file; I have (courtesy of "C# 2010 Express") App.g.i.cs with:

namespace WpfApplication1 {


    /// <summary>
    /// App
    /// </summary>
    [System.CodeDom.Compiler.GeneratedCodeAttribute("PresentationBuildTasks", "4.0.0.0")]
    public partial class App : System.Windows.Application {

        /// <summary>
        /// InitializeComponent
        /// </summary>
        [System.Diagnostics.DebuggerNonUserCodeAttribute()]
        public void InitializeComponent() {

            #line 4 "..\..\..\App.xaml"
            this.StartupUri = new System.Uri("MainWindow.xaml", System.UriKind.Relative);

            #line default
            #line hidden
        }

        /// <summary>
        /// Application Entry Point.
        /// </summary>
        [System.STAThreadAttribute()]
        [System.Diagnostics.DebuggerNonUserCodeAttribute()]
        public static void Main() {
            WpfApplication1.App app = new WpfApplication1.App();
            app.InitializeComponent();
            app.Run();
        }
    }
}
Marc Gravell
  • 1,026,079
  • 266
  • 2,566
  • 2,900
  • 1
    The same thing exists in `App.g.cs`, as well. But I tried to add to `Main()` and every time I would rebuild my project, it would revert to what you have, here. Tried to create my own in another class, but Project Properties only finds MyProject.App, not the other class, so can't redirect it. – vapcguy Jun 08 '16 at 19:14
  • 2
    Alternatively, open `App.xaml.cs` in visual studio. Use the navigation bar > Method drop down list > select `Main` (greyed out). This takes you to `App.g.i.cs`. – P.Brian.Mackey Apr 06 '18 at 15:58
16

Main() is automatically provided by the CLR and the WPF.

The C# compiler takes a command-line switch /m which specifies the type that contains the implementation of Main(). By convention, if no startup object is explicitly specified, the CLR will lookup any class that has a static Main() method and will call it. (As @Marc Gravel pointed out in his comment)

In the case of WPF, the Main() is automatically generated when App.xaml is built and the /m switch is specified to make the C# compiler use that class as entry point. If you look at the project properties however, you'll find there's a setting for you to choose the startup object. So if you want, you can provide your own class that implements Main().

Note that this will put the responsibility on you to create the Application instance and call its Run() method to ensure that the WPF infrastructure is started properly.

Franci Penov
  • 74,861
  • 18
  • 132
  • 169
  • Actually, without `/m` it doesn't *care* what the type is called; if you aren't explicit it just tries to find **any** suitable `Main` method, and complains if it finds 0 or more than one. As an example, the "Hello World" sample in the language spec (§1.1) uses `Hello` as the type name. – Marc Gravell Apr 22 '10 at 21:53
  • 3
    To be pedantic: it's not really accurate to say that `main()` is provided by the CLR (the runtime), it's really the compiler that generates it. – Hank Feb 17 '15 at 14:27
  • 1
    Added my +1 for reminding the audience they will have to add in their own Application instance (i.e. `MyApp.App app = new MyApp.App();`) and call `.Run()` on it, like the previous `Main()` would have. Good call. Also, would have to add `app.InitializeComponent();` before `app.Run()`, and fortunately for us, the original `InitializeComponent()` method is still there (seen in App.g.cs, so no need to add that one back!). – vapcguy Jun 08 '16 at 20:03
10

Main() is generated during compilation. You can find it in App.g.cs (in obj/{Debug,Release} folder).

Vlad
  • 35,022
  • 6
  • 77
  • 199
6

main() is a standard entry point for an application, but all applications are structured that way. In a XAML project, the App.XAML file specifies the entry point where it says StartupUri="MainWindow.xaml".

As it is stated by others, the actual main function is generated based on the contents of the XAML files in the project.

Annath
  • 1,262
  • 10
  • 20
3

In case you removed default App.xaml and MinWindow.xaml, better to edit .csproj After adding App.xaml manually, your .csproj will be:

<Page Include ="App.xaml">
       <DependentUpon>MSBuild:Compile</DependentUpon>
       <SubType>Code</SubType>
</Page>

Change this to:

<ApplicationDefinition Include="App.xaml">
    <Generator>MSBuild:Compile</Generator>
    <SubType>Designer</SubType>
</ApplicationDefinition>
  • In my case a .NET Framework 4.8 that gets data from an ancient Outlook .pst file; on top of this I want to display this data with a WPF UI; so, I had to add System.Xaml, PresentationCore and PresentationFramework and delete Program.cs; the error message "CS5001 Program does not contain a static 'Main' method suitable for an entry point" appeared after. Your advice solved. Exactly what I needed! Thanks a lot. – Marcelo Scofano Diniz May 13 '22 at 14:42
1

I copied files that wouldn't load in another project that was without a mainwindow into a new one and got this error.

For me it took doing the opposite approach to Andreas Kahler to fix:

After making a window file and setting the startup uri to this file i switched Page to ApplicationDefinition of App.xaml 'Build Action' property.

Declan Taylor
  • 408
  • 6
  • 8
0
To Clear this is Error Do the following Step 
Right Click on App.Xaml
Properties>Change Buld Action
From Page to > ApplicationDefinition
Build the soulution and Run 
It Will Work Fine[enter image description here][1]

Refer this image also [1]: https://i.stack.imgur.com/zYFPU.png

Anandu
  • 1
  • 2