Search This Blog

Thursday, April 28, 2016

Welcome to the XrmToolBox Plugins Store

Wow! It's been a long time since I did not write an article on my blog!

Today, I'm releasing the April 2016 version of XrmToolBox. This new version comes with an integrated plugins store. So, what does it mean?

It means each and every developer can share his/her XrmToolBox plugins without the need to ask me permissions or help to distribute the plugins across the world.

Here is what the Plugins Store looks like



As you can see, Jonas Rapp and Daryl Labar already shared their plugins through this new channel. To install their plugins, just select them and click on "Install selected packages" button and you are good to go!

The Plugins store is also capable to detect that a new version of an installed plugin is available and let syou update it.

The Plugins store is launched automatically after XrmToolBox startup but you can disable this in the store form itself or in XrmToolBox options. The Plugins Store is also available from the main application toolbar.

So, what do you need to do if you want to share your XrmToolBox plugin? Just follow this procedure on XrmToolBox wiki

Finally, you can download this new version on the XrmToolBox website, as usual. Or maybe you installed March version and if everything goes as expected (crossing fingers), you should be able to update your XrmToolBox application automatically thanks to the XrmToolBox auto updater released in previous version.

3 comments:

Ben said...

I'm getting this error any time the Plugins Store tries to load, or I click the Reload plugins from NuGet button:
"Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information."

Going to try a reinstall later, but any ideas how to troubleshoot this?

Noah Davis said...

I love the XRM Toolbox.

Just one question: the update screen shows me which updates are available, but when I click to update them, certain plugins never update. (I currently have 7 that won't update.) The newer versions are sitting in the Nuget Plugins folder, but nothing happens.

Thoughts? Ideas? Did I install the tool (which I did months ago) incorrectly? (Though 99% of the other plugins have updated flawlessly.)

Thanks.

Tanguy said...

The problem comes from these plugins that have an invalid nuget package. The package states a version number but the file inside the package still has the old number. So the Plugins store always show an update available.
Nothing to do except contacting plugins developers to make them fix their package.
A new version of plugins store will be available soon and will validate plugins first. I hope that developers will then review their package or their plugins won't be available anymore