Teddy's Aspect Weaver Version 0.3 with Great Updating and Fixing, Especially the Implementing of Getting Runtime Method Context
2005-09-27 10:44
671 查看
[More about Teddy's Aspect Weaver]
Teddy's Aspect Weaver Version 0.3 [Updated: 2005/09/27]
Changes:
- Add the geting context info and getting context arguments ability
- Fix some internal XPath bugs
- Fix BeforeConstructorCall/BeforeMethodCall bugs
- Fix the ILML Library parsing method parameter name bug
- Add the object instance in aspect local stack ability, which means you can new any object in aspect code only if the type of you object is defined or can be referenced in the base assembly
- Move assembly AspectWeaver.Attributes code to assembly AspectWeaver.Aspects
Sample of Getting Runtime Method Context Info and Method Arguments
Configuration
<?xml version="1.0" encoding="utf-8" ?>
<Configuration logFile="LogWeaving.xml" cleanTempFiles="false">
<BaseAssembly>../TestLib/bin/Debug/TestLib.dll</BaseAssembly>
<OutputAssembly>../TestLib/bin/Debug/TestLib_output.dll</OutputAssembly>
<AspectAssemblies>
<AspectAssembly uniqueName="TestAspectLib.dll" path="bin/Debug/TestAspectLib.dll" />
</AspectAssemblies>
<AdviceFiles>
<AdviceFile>Advice-Test.xml</AdviceFile>
</AdviceFiles>
</Configuration>
TestClass.cs
using System;
namespace TestLib
{
public class TestClass
{
public void MethodToBeTestedGetContextInfoAndGetArgumments(object p1, string p2, int p3)
{
}
public void MethodToTestGetContextInfoAndGetArgumments()
{
MethodToBeTestedGetContextInfoAndGetArgumments("p1", "p2", 3);
}
}
}
TestAspectClass.cs
using System;
using System.Reflection;
using AspectWeaver.Aspects;
namespace TestAspectLib
{
public class TestAspectClass : Aspect
{
[InlineAtStart("//Method[@name='MethodToBeTestedGetContextInfoAndGetArgumments']")]
public void CodeToTestGetContextInfoAndGetArgumments()
{
MethodBase contextInfo = GetContextInfo();
Console.Write(contextInfo.ReflectedType.FullName + "::" + contextInfo.Name + "/n/n");
object[] args = GetArguments();
Console.Write(string.Format("Arguments: {0}, {1}, {2}/n/n", args));
}
}
}
After Weaving Code (decompiled)
public class TestClass
{
public void MethodToBeTestedGetContextInfoAndGetArgumments(object p1, string p2, int p3)
{
MethodBase methodBase = base.GetType().GetMethod("MethodToBeTestedGetContextInfoAndGetArgumments");
Console.Write(String.Concat(methodBase.ReflectedType.FullName, "::", methodBase.Name, "/n/n"));
object[] locals = new object[]
{p1, p2, p3};
Console.Write(String.Format("Arguments: {0}, {1}, {2}/n/n", locals));
}
public void MethodToTestGetContextInfoAndGetArgumments()
{
MethodToBeTestedGetContextInfoAndGetArgumments("p1", "p2", 3);
}
}
Description
In the sample, we can see, if you call the GetContextInfo() and GetArguments() from aspect classes which inherited from AspectWeaver.Aspects.Aspect which defined the two methods, the weaved code be translated to local reflection code, no additional dependence. But it is interesting that in fact, there are not any code in the two methods' body at all. Do you know why? :^)
Download Source Code
AspectWeaver0.5.zip
Teddy's Aspect Weaver Version 0.3 [Updated: 2005/09/27]
Changes:
- Add the geting context info and getting context arguments ability
- Fix some internal XPath bugs
- Fix BeforeConstructorCall/BeforeMethodCall bugs
- Fix the ILML Library parsing method parameter name bug
- Add the object instance in aspect local stack ability, which means you can new any object in aspect code only if the type of you object is defined or can be referenced in the base assembly
- Move assembly AspectWeaver.Attributes code to assembly AspectWeaver.Aspects
Sample of Getting Runtime Method Context Info and Method Arguments
Configuration
<?xml version="1.0" encoding="utf-8" ?>
<Configuration logFile="LogWeaving.xml" cleanTempFiles="false">
<BaseAssembly>../TestLib/bin/Debug/TestLib.dll</BaseAssembly>
<OutputAssembly>../TestLib/bin/Debug/TestLib_output.dll</OutputAssembly>
<AspectAssemblies>
<AspectAssembly uniqueName="TestAspectLib.dll" path="bin/Debug/TestAspectLib.dll" />
</AspectAssemblies>
<AdviceFiles>
<AdviceFile>Advice-Test.xml</AdviceFile>
</AdviceFiles>
</Configuration>
TestClass.cs
using System;
namespace TestLib
{
public class TestClass
{
public void MethodToBeTestedGetContextInfoAndGetArgumments(object p1, string p2, int p3)
{
}
public void MethodToTestGetContextInfoAndGetArgumments()
{
MethodToBeTestedGetContextInfoAndGetArgumments("p1", "p2", 3);
}
}
}
TestAspectClass.cs
using System;
using System.Reflection;
using AspectWeaver.Aspects;
namespace TestAspectLib
{
public class TestAspectClass : Aspect
{
[InlineAtStart("//Method[@name='MethodToBeTestedGetContextInfoAndGetArgumments']")]
public void CodeToTestGetContextInfoAndGetArgumments()
{
MethodBase contextInfo = GetContextInfo();
Console.Write(contextInfo.ReflectedType.FullName + "::" + contextInfo.Name + "/n/n");
object[] args = GetArguments();
Console.Write(string.Format("Arguments: {0}, {1}, {2}/n/n", args));
}
}
}
After Weaving Code (decompiled)
public class TestClass
{
public void MethodToBeTestedGetContextInfoAndGetArgumments(object p1, string p2, int p3)
{
MethodBase methodBase = base.GetType().GetMethod("MethodToBeTestedGetContextInfoAndGetArgumments");
Console.Write(String.Concat(methodBase.ReflectedType.FullName, "::", methodBase.Name, "/n/n"));
object[] locals = new object[]
{p1, p2, p3};
Console.Write(String.Format("Arguments: {0}, {1}, {2}/n/n", locals));
}
public void MethodToTestGetContextInfoAndGetArgumments()
{
MethodToBeTestedGetContextInfoAndGetArgumments("p1", "p2", 3);
}
}
Description
In the sample, we can see, if you call the GetContextInfo() and GetArguments() from aspect classes which inherited from AspectWeaver.Aspects.Aspect which defined the two methods, the weaved code be translated to local reflection code, no additional dependence. But it is interesting that in fact, there are not any code in the two methods' body at all. Do you know why? :^)
Download Source Code
AspectWeaver0.5.zip
相关文章推荐
- Teddy's Aspect Weaver Version 0.3 with Great Updating and Fixing, Especially the Implementing of Getting Runtime Method Context Info and Method Arguments in MSIL Level
- “System.IO.FileLoadException: Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 错误
- Teddy's Aspect Weaver Version 0.2 with Additional Custom Attribute Way Configuration
- Teddy's Aspect Weaver Version 0.2 with Additional Custom Attribute Way Configuration
- Mixed mode assembly is built against version 'v1.1.4322' of the runtime and...问题——C# DirectXSound
- Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration info
- Mixed mode assembly is built against version 'v1.1.4322' of the runtime and...问题——C# DirectXSound
- Installation failed with message...It is possible that this issue is resolved by uninstalling an existing version of the apk if it is present, and then re-installing.
- Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additio
- You are using version 6.4.1 of the AdMob SDK which is non-compliant with the Google Play Ad Policy
- Apple is not currently accepting applications built with this version of the SDK Xcode 1091
- The ups and downs of life with Linus
- You are attempting to build with the incorrect version of java.
- this version of Android Studio is incompatible with the Gradle Plugin used. try disabling Instant Ru
- Improve the Design and Flexibility of Your Project with Extreme Programming Techniques(Reship)
- This version of android studio is incompatible with the gradle version used.
- Error running app: This version of Android Studio is incompatible with the Gradle Plugin used. Try
- Teddy's Aspect Weaver Version 0.5
- Test-Driven C#: Improve the Design and Flexibility of Your Project with Extreme Programming Techniques
- 使用JavaScript展开/折叠TreeView中所有节点(Expand and Collapse All Nodes of asp.net Treeview on the client with javascript)