Quantcast
Channel: CSLA .NET
Viewing all articles
Browse latest Browse all 764

CSLA and Microsoft Application Insight incompatibility

$
0
0

Hoping someone could offer some insight as I've been battling with this for some time.

I have a long term CSLA (4.5.6) web project that I'm trying to add the latest version of Application Insights. This was a simple process however it did not work. The site worked as usualt but nothing was posted to Application Insights, i.e there was an error in the HTTP Module added by AI, with no source I couldn't track this down.

After a long process of trial and error I narrowed it down to some binding redirect in the config file..

<dependentAssembly>        <assemblyIdentity name="System.Runtime" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />        <bindingRedirect oldVersion="0.0.0.0-2.5.19.0" newVersion="2.5.19.0" />      </dependentAssembly>      <dependentAssembly>        <assemblyIdentity name="System.Threading.Tasks" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />        <bindingRedirect oldVersion="0.0.0.0-2.5.19.0" newVersion="2.5.19.0" />      </dependentAssembly>

Commenting this out resulted in Application Insights working however the site crashed completely. It seems Ai has a dependancy on the Microsoft.Bcl libraries (which incidently I didn't think were needed for 4.5) and adds the Microsoft.Threading.Tasks.*.dll's which kills CSLA.

Looking at CSLA source these are also referenced but never copied to bin folders.

Can anyone advise on the compatibility of the older .Net 4.0 async libs (ie Microsoft.Blc etc) and the CSLA. If I remove those dll;'s the app works again but Application Insights doesn't.

I don't think this is a CSLA issue but it would be nice to know what's going on. :(


Viewing all articles
Browse latest Browse all 764

Trending Articles