Message from discussion
Separating xaml from xaml.cs
Received: by 10.66.76.38 with SMTP id h6mr2426077paw.15.1347308114355;
Mon, 10 Sep 2012 13:15:14 -0700 (PDT)
X-BeenThere: mono-cecil@googlegroups.com
Received: by 10.68.136.233 with SMTP id qd9ls5595907pbb.4.gmail; Mon, 10 Sep
2012 13:15:14 -0700 (PDT)
Received: by 10.68.212.99 with SMTP id nj3mr792277pbc.20.1347308113966;
Mon, 10 Sep 2012 13:15:13 -0700 (PDT)
Date: Mon, 10 Sep 2012 13:15:13 -0700 (PDT)
From: deedee <imvidi...@gmail.com>
To: mono-cecil@googlegroups.com
Message-Id: <85374d91-41ea-4434-88b2-273906e74944@googlegroups.com>
In-Reply-To: <e8fb8762-5d40-4481-a748-8489be883093@googlegroups.com>
References: <e8fb8762-5d40-4481-a748-8489be883093@googlegroups.com>
Subject: Re: Separating xaml from xaml.cs
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_851_14040642.1347308113607"
------=_Part_851_14040642.1347308113607
Content-Type: multipart/alternative;
boundary="----=_Part_852_26316197.1347308113607"
------=_Part_852_26316197.1347308113607
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Oh well. I guess I can exclude the InitializeComponent method -- that
should take care of it, because all of the xaml instructions must be in
that method only.
But any other ideas are welcome!
Thanks again :)
On Monday, September 10, 2012 2:05:35 PM UTC-6, deedee wrote:
>
> Hi,
>
> In the dll, I noticed that all the xaml classes have a '
> System.CodeDom.Compiler.GeneratedCodeAttribute' with
> "PresentationBuildTasks" as it's argument. This applies to even the
> code-behind partial class which contains our code (in the xaml.cs file).
>
> Is there a property or a flag somewhere that will distinguish the method
> instructions coming from a xaml vs code behind class? (eg. an event handler
> attached from within the xaml vs in the xaml.cs)?
>
> Thanks :)
>
------=_Part_852_26316197.1347308113607
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
Oh well. I guess I can exclude the InitializeComponent method -- that should take care of it, because all of the xaml instructions must be in that method only.<br><br>But any other ideas are welcome! <br><br>Thanks again :)<br><br>On Monday, September 10, 2012 2:05:35 PM UTC-6, deedee wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">Hi,<br><br>In the dll, I noticed that all the xaml classes have a '<span style="color:#a31515"> <span style="color:rgb(0,0,0)">System.CodeDom.Compiler.<wbr>GeneratedCodeAttribute</span></span>' with "PresentationBuildTasks" as it's argument. This applies to even the code-behind partial class which contains our code (in the xaml.cs file). <br><br>Is there a property or a flag somewhere that will distinguish the method instructions coming from a xaml vs code behind class? (eg. an event handler attached from within the xaml vs in the xaml.cs)?<br><br>Thanks :)<br></blockquote>
------=_Part_852_26316197.1347308113607--
------=_Part_851_14040642.1347308113607--