Custom web application and bin folder... Yes, but...

As you can see on the Best Practice of the CRM SDK (http://msdn.microsoft.com/en-us/library/dd548493.aspx), since rollup 2, you can put your custom assembly to your own web application bin folder instead of using the bin folder of the CRM web application.

Since a while, I didn't understand why this practice seemed to work for everybody except me...

The answer is simple: The assembly name can't contain any dot if you want it to work... It is a known bug by Microsoft.

As I was used to name my assemblies like .Crm.Web, it couldn't work...

I hope this will help some of you, guys!

Comments

Ramon said…
ouuuu, very interesting Tanguy, thanks!
November 12, 2009 at 9:46 AM
Anonymous said…
I found that out the hard way as well. However when I was working with MS on the issue, they did not admit to it being an issue. They seemed completely caught off guard by the whole thing!
November 17, 2009 at 5:12 PM
Tanguy said…
In fact, I get this response from a technical consultant from MS, not the support.

But the guy told me it will be corrected... we don't know yat when...
November 17, 2009 at 7:03 PM
Post a Comment

Popular posts from this blog

Use feature flags in your plugins

Lately, there was a discussion on Twitter about the best practice to handle plugins: One class per plugin? One project per plugin? or anything else? On my side, I'm using one project for all the plugins for the same customer. This is what I answered on Twitter. Then came a question : How do I handle the fact that some plugins may have not been tested or completed yet and I need to release the plugins assembly. The answer was : Feature flag! What is a feature flag? It's a concept that will allow to enable/disable some features or portion of code depending on a configuration. Let's take an example where a plugin must execute two features : Feature A and Feature B public class MyPlugin : IPlugin { public void Execute(IServiceProvider serviceProvider) { var service = new MyCustomService(); service.ExecuteFeatureA(); service.ExecuteFeatureB(); } } We need to find a way to execute conditionally these methods, let's say because feature B
Read more

New XrmToolBox plugin : Import/Export NN relationships

Image
Two plugins in one day! wow! This one was, in fact, developed a couple of months ago. One of my colleague was using a solution from my fellow MVP Andrii Butenko which allows to import/export NN relationships in a silverlight web resource. This was nice but my colleague was using other attributes than primary key to do the mapping and Andrii’s solution does not support this. So he asked me to develop a XrmToolBox’s plugin that could do this. And, here it is! You can select entities and relationships and moreover, choose mapping attributes on both enitities. I only let text and number attributes selectable as other does not really make sense for mapping purposes. Then you can import or export NN relationships! Here is a preview As usual, this plugin, among other, is available with XrmToolBox on CodePlex
Read more

Searchable Propery Attribute Updater

Image
Hi, The previous post was not the last one... :) You can find in this post the first tool that will make your life easier: Just remember when you customer asked you to remove all these unused attributes form the attribute list of the advanced find form... You navigated through all attrbutes form to modify the Searchable property of each attributes for hours... (maybe am I exaggerating a bit...) The program I give you allows you to update all attributes in a single winform application! Yes it can be! Do not hesitate to give me your comments about this program if you think improvements can be done... Download:
Read more