PropertyChanged VS JustDecompile Engine

Add [AddINotifyPropertyChangedInterface] attribute to the class for change notification.

All the weaving libraries (also called weavers or addin) using Fody need to have the .Fody suffix, so it's quite easy to recognize them. As an example, if you ever had to implement INotifyPropertyChanged manually in a class with dozens of properties you would probably welcome weaving (and Fody) with open arms. By creating all the plumbing code directly in IL, libraries like PropertyChanged.Fody allows to inject the necessary notification code without the need to modify anything in the original source code.

You can rewrite auto-props (as used this this lib https://github.com/Fody/PropertyChanged) with Fody.

If you're not familiar with Fody and specifically the PropertyChanged weaver, I highly recommend checking it out: https://github.com/Fody/PropertyChanged

Now the ugly part - you need to implement INotifyPropertyChanged. It can be done either manually, or automated with this or this

https://github.com/Fody/PropertyChanged and Android background makes WPF pretty easy. At least the surface level stuff.

If you really don't want to deal with it ever again, just add this Fody - PropertyChanged NuGet package. Any class that inherits from INotifyPropertyChanged will be updated at compile time to inject in the boilerplate code for handling the property change and you never even need to think about it again. All you need to do is just add plain old properties. The only downside that some people see is that it is not immediately transparent as the change notification code is injected in during compile and is not in source code.

And GitHub is the place where employees of billion dollar companies pester unpaid maintainers because they won’t support a 12 year old version of .NET

https://github.com/Fody/PropertyChanged/issues/270#issuecomm...

If you need more info, check the docs https://github.com/Fody/PropertyChanged

As you can see IL code is not exactly human readable, and it's also quite verbose. If you want to have an idea of how your code looks like in IL you can use a decompiler tool such as JustDecompile or ILSpy.

I've been using JustDecompile and dnSpy. Remember that if it's programmed in, let's say, c++ or c, it's not that simple to reverse engineer. Simple C# .NET programs should be fairly easy to reverse engineer.

It's .NET code, so you can disassemble it or view it with a tool like Telerik's JustDecompile.

Looks like it hasn't been updated for years (at least according to their GitHub repo): https://github.com/telerik/justdecompileengine