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)?
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.
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)?
On Monday, September 10, 2012 2:15:13 PM UTC-6, deedee wrote:
> 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)?
On Monday, September 10, 2012 2:38:34 PM UTC-6, deedee wrote:
> Surprisingly, that does not work :(
> On Monday, September 10, 2012 2:15:13 PM UTC-6, deedee wrote:
>> 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)?
On Monday, September 10, 2012 2:38:34 PM UTC-6, deedee wrote:
> Surprisingly, that does not work :(
> On Monday, September 10, 2012 2:15:13 PM UTC-6, deedee wrote:
>> 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)?
