PostSharp

[ddignam]

Hi Folks,

Is there any way for me to turn the following warning into an error so that things don't build. This will cause my aspects to not behave correctly. The asepct is being added by way of a compoundAspect

Code: Select all

postsharp warning PS0069: PostSharp: Cannot weave the initialization of the field AddValue.m_result, because it is initialized outside the constructor. The weaving of this field initialization will be ignored, but other field assignments will be woven.

--
Dan

[gfraiteur]

No, it is not possible.

But you can submit a feature request in the issue tracker so that it will get considered for future versions.

Gael

[ddignam]

Thanks Gael,

I'll submit feature request, and tell the guys to keep an eye open (and check the build logs )

--
Dan

[ddignam]

I actually realized when I woke up in the middle of the night that I can hook the constructor and get the intial state of the fields there. This stuff is great

It might still be a good idea to have a change warnings into errors (in much the same way you can for the C# compiler on the project page)

--
Dan

[ddignam]

Interestingly adding the OnMethodInvocation aspect removes the warning, and causes a field set to be generated ..... ?

--
Dan

[gfraiteur]

No idea. If you think there is a bug, please file a bug report with a repro case.

Thanks,

Gael

[ddignam]

Hi Gael,

I've submitted issue 209 with an example solution. I must admit I like the behaviour. However, if adding an OnMethodInvocationAspect to a constructor allows the field to be woven, the PS0069 warning would appear to be fixable ?

--
Dan