Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 828141
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T03:40:58+00:00 2026-05-15T03:40:58+00:00

It seems that XAML files should have corresponding .cs files in a C# project.

  • 0

It seems that XAML files should have corresponding .cs files in a C# project. I know Visual Studio does all the things for us. I’m just curious how they are linked together? I mean, are they specified in the project file, or just because they have the same names? And also, App.xaml file specifies the startup file, but how does the compiler know? Is it possible to appoint another file other than App.xaml to do the same things as App.xaml does?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-15T03:40:59+00:00Added an answer on May 15, 2026 at 3:40 am

    There’s no magic happening in WPF. All what happen is written some where. It’s VS which generates some of the code.

    The xaml code is linked with a class.

    <Window x:Class="YourNameSpace.MainWindow" ...
    

    VS generates for you a MainWindow.cs file which has a class named MainWindow of Window type. The type is important here. If you use another type the compiler won’t link it to your MainWindow.xaml even if it’s the right class name.
    Eventually, for a UserControl you will have the xaml tag <UserControl instead of a Window tag.

    One more thing, the compiler also generates at compile time a file called MainWindow.g.cs in the obj folder where you can also find a MainWindow.baml the compiled version of the xaml file.
    This file will contain a partial class MainWindow with all the controls declared that you use in the XAML. That’s a behind the scene job that the compiler does which is unrelated to the association between the XAML and the relative class.

    The application is the same, only that the class type changes. This is to link XAML with the class.
    For the StartUp Window, it’s specified in the XAML file by default to a class. However, you can customize the .cs file and do yo own logic in the ApplicationStartUp event.

    Same for the Shutdown event. By default it’s when all your windows are closed but you can change it to when the MainWindow is closed or an explicit shutdown.

    The csproj (in the case of c#) tells the compiler which class is the application.

    <ApplicationDefinition Include="App.xaml">
      <Generator>MSBuild:Compile</Generator>
      <SubType>Designer</SubType>
    </ApplicationDefinition>
    

    Not only the XAML tag like others have stated. The tag only defines the type of the class and don’t make your program start with this specific class.

    Application overview
    (source: microsoft.com)

    You can read further here :
    MSDN – Building WPF application

    MSDN – Code-Behind and XAML in WPF

    MSDN – Application Management Overview

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

It seems that anyone can snoop on incoming/outgoing .NET web service SOAP messages just
Seems that requirements on safety do not seem to like systems that use AI
It seems that a List object cannot be stored in a List variable in
It seems that it is impossible to capture the keyboard event normally used for
It seems that Silverlight/WPF are the long term future for user interface development with
It seems that most of the installers for Perl are centered around installing Perl
It seems that C# 3 hit me without me even noticing, could you guys
It seems that when I use a tool (such as winmerge) to update my
It seems that in some cases, if you end up with nested modalPopups wrapped
It seems that the System.Diagnostics.Debug , and System.Diagnostics.Trace are largely the same, with the

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.