v2581 - Microsoft.CompilerServices.AsyncTargetingPack.Net4

[Kijana Woodard]

I just downloaded Server 2581 from the ravendb.net and Client was was updated to 2581 using myget feed. Ran into "Could not load file or assembly 'Microsoft.CompilerServices.AsyncTargetingPack.Net4" when using BulkInsert.  

Project is .net 4.5 console app.

Build issue similar to https://groups.google.com/forum/?fromgroups#!topic/ravendb/XCAnh0NyJpk?

[Fitzchak Yitzchaki]

Yes, we have an open issue for that. We need to provide a compiled dlls against .NET 4.5, which won't compile with the Microsoft.CompilerServices.AsyncTargetingPack.Net4.dll.

We are currently experimenting with the Microsoft Bcl Async package, which is now stable http://blogs.msdn.com/b/bclteam/archive/2013/04/17/microsoft-bcl-async-is-now-stable.aspx.

The downside of the Microsoft Bcl Async package is that anyone that reference the RavenDB.Client package will have to also reference the Microsoft Bcl Async on his project, if they're using the .NET 4.0 of SL 5.0. The good thing is that this will probably won't be required when using .NET 4.5, but we are still looking into that.

[Fitzchak Yitzchaki]

This should be fixed in the next build (#2583). Please test it out.

We are not using Microsoft Bcl Async for 2.5, since we are in the process to stabilize the product. If needed, it will be used in the vnext (3.0). 

[Kijana Woodard]

Works. :-D

--
You received this message because you are subscribed to the Google Groups "ravendb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Simon Bartlett]

It works, but...
Now that you've changed the names of the assemblies (suffixing them with "-4.5") - I am having lots of problems using bundles or other libraries cause they all expect the old assembly names.

Any possibility of keeping the old names?

[Oren Eini (Ayende Rahien)]

How would we do that?

[Simon Bartlett]

I haven't looked at the build scripts that you're using, so I don't know right now.

As it currently is - it causes IMO a lot of pain. After installing the latest NuGet packages into a .NET 4.5 project, I had to choose between the following two options:

1. Unreference all the .NET 4.5 assemblies, and add references to all the .NET 4.0 assemblies
   
2. Download all the sources for the bundles/plugins I am using and recompile them against the 4.5 assemblies

This is all due to the fact that all the third-party libraries/bundles were compiled against RavenDB assemblies that were named Raven.***.dll - NOT Raven.***-4.5.dll

[Oren Eini (Ayende Rahien)]

They won't work compiled against that either. you would have to have spearate compilation for everything

[Simon Bartlett]

I'm probably wrong, but I thought as long as the Assembly name (not the file name), and maybe the public key are the same - there shouldn't be any problem. I might test this on my local computer.

[Oren Eini (Ayende Rahien)]

It isn't that that is going to cause the problems. Those assemblies where compiled against different versions of the framework, and are using different libraries.