I was reading the book "Apress Pro LINQ: Language Integrated Query in C#" and I came across partial methods, but I really don't understand what is the need for them.
I think the examples in the book (properties before and after change) can be implemented using events. So any explanation?
They are not "needed", but desired for large scale applications. Extensive use of events leads to the Smart UI anti-pattern where the business logic is tightly coupled with the user interface, whereas partial functions allow you to better separate your concerns.
Here is a link to the MSDN C# programming guide on partial methods as well. http://msdn.microsoft.com/en-us/library/wa80x488.aspx
Yes, you could achieve a similar effect with events as you can with partial methods. Partial methods are really just a way of letting code generators, primarily designers, to generate hooks for the non-generated code. Events could fill this role.
However there are advantages to partial methods over events in particular
The compiler will remove calls to partial methods if there are no implementations. With the alternative of events, listeners would have to be checked at runtime (they would also need to be stored, etc). This allows partial methods to be more performant, especially when there are many of potential "events" and only a few have "listeners" registered.
Partial methods are defined at compile time, events at runtime. So they are different things.
Partial methods were brought to the picture to extend existing classes that you have no control over (part of the framework or auto-generated)
Hope this helps