Missing plugin checks added

There are kind of registration errors that really hard to debug. Usually they appear in error logs as Plug-in assembly does not contain the required types or assembly content cannot be updated.

Reasons causing the error could be different:

• Plugin get removed;
• Plugin get renamed;
• Plugin's access level modificator has changed.

But result is always the same: assembly could not be registered, since required plugin type is missing due to one of caused mentioned above.

Now this errors detected in PluginRegistration automatically. The code checks plugins listed in given assembly and in the CRM organization and in case of mismatch shows user list of plugins that causes the problem.

Workflow isolation fixed

Plugin was referencing old version of WWF assemblies, and explicitly was making them as not supporting isolation. Which is not correct. This was fixed in most recent version.

Introducing "Early-Bound Magic Cast"!

Release Notes

Painful and long lasting issue #1 was finally solved by introducing new Transformation.Magic class that casts late-bound entities and early-bound entities automatically resolved to classes in another assembly to correct early-bound assemblies in Xrm.Sdk.PluginResistration assembly.

This does not fix XrmToolBox isolation issue, but at least lets operate this the plugins without any obstacles.

Some NUnit tests was added during Magic development. They will grow up in number with time, along with refactoring.

There was a lots of changes in code styling. It was pushed from a-la .NET 2.0 towards .NET 4.0 like.

NuGet maintenance release

NuGet dependency was updated to proper value, to fix Plugin Registration shown as incompatible in XrmToolBox.

First NuGet release

• Proper handling of AppDomain isolation for loaded assemblies;
• Binary name change to comply with others' plugins names;
• Minor code clean up.

v3.0-beta.4

• Added support for XrmToolBox February release;
• Sending basic progress notes to XrmToolBox status bar;
• Minor code clean-up.

v3.0-beta.3

Added support for XrmToolBox February release.

v3.0-beta.2

Added support for XrmToolBox July release.

3.0-beta.1

• All main operations are working;
• Azure-related code was stripped away;
• Early binding types was mostly stripped away (application size was reduced by 6 times).