4

Does it apply to any aspect? Is that it?

If I use a multicast attribute it will apply randomly to the first 10 matches only?

I'm not sure if I got this restriction right. Do you mind elaborating it a little? Examples would be well welcome'd.

hugo00
  • 117
  • 1
  • 9

1 Answers1

5

Starting from PostSharp 4.3, this limitation applies to any aspect. The build will fail if you apply aspects to more than 10 targets (with Multicast or not). So no randomness happens.

If PostSharp 4.3 detects that your project would have been built successfully with PostSharp 4.2 or prior, then the backward-compatibility mode is enabled and the project will be built by PostSharp 4.3 without error. Please refer to PostSharp 4.2 API documentation to check if an API used to be available in PostSharp Express.

Gael Fraiteur
  • 6,759
  • 2
  • 24
  • 31
  • Oh I see, that clears things out. Just didn't get about the backward-compatibility. Does it mean that it still will apply aspects to more than 10 classes as before if it detects this compatility? – hugo00 Aug 09 '16 at 15:48
  • Which case would it fail to build with PostSharp 4.2? I'm having a little trouble finding the PostSharp 4.2 API docs. Sorry to bother. – hugo00 Aug 09 '16 at 15:56
  • The backward-compatibility mode has been disabled in PostSharp 5.0. – Gael Fraiteur Sep 08 '17 at 08:26