BCL Team Blog - All Comments

re: Microsoft.Bcl.Async is Now Stable

Richard — Tue, 21 May 2013 08:43:35 GMT

Hi guys,

Is there a reason that Microsoft.Threading.Tasks required System.Core 2.0.5 rather than 4.0? I just had to remove all asynchronous code from an application because production didn't have the assembly available.

Is there a recommended way to get System.Core, 2.0.5 deployed with an application?

Richard

re: Microsoft.Bcl.Async is Now Stable

Immo Landwerth [MSFT] — Mon, 13 May 2013 16:34:24 GMT

@Mark: Thanks, we are looking into it.

@Fog.Gene: Thanks for reporting this issue. I can reproduce it and filed a bug. We'll fix it in the next update.

re: Microsoft.Bcl.Async is Now Stable

Fog.Gene — Mon, 13 May 2013 02:56:04 GMT

I was having problems loading the solution when adding this package if my project was installed in a folder that contains the # (sharp) symbol (e.g. C# Projects\ProjectName\...). It could not find the correct path to the package.

Also, as somebody mentioned before, I had to manually add a reference to System.Net 4.0.0.0 for the package to correctly install in the project.

I thought I'd report this stuff.

re: Microsoft.Bcl.Async is Now Stable

Mark — Wed, 08 May 2013 16:53:32 GMT

I have a multi-assembly VB.NET application (VS2012, .NET 4.0), and I've added the three Microsoft.Bcl(.Async, .Build) NuGet packages to all projects in the solution. I am trying to use ClickOnce to deploy the executable, but System.Runtime.dll and System.Threading.Tasks.dll are not being included in the ClickOnce deployment. They are not even listed in the "Application Files..." dialog, even though they are referenced by the project and "Copy Local" is true. Any ideas why they aren't being included? Is there some way to add them manually?

re: Microsoft.Bcl.Async is Now Stable

Immo Landwerth [MSFT] — Fri, 03 May 2013 00:48:39 GMT

@Jernej Kavka and Amenti: Thanks for the kind words -- we are glad you are as excited as we are!

@NW: This looks like you are building on a .NET 4 machine. Although we do support targeting .NET 4, we require the .NET 4.5 tools. This would also be required, if, for example, you try to use the new async/await keywords.

re: Microsoft.Bcl.Async is Now Stable

NW — Thu, 02 May 2013 18:56:38 GMT

I get the following error when trying to build on the MSBuild server for a couple of my projects. It builds fine on my machine. What could I be missing up there?

...\Sources\packages\Microsoft.Bcl.Build.1.0.5\tools\Microsoft.Bcl.Build.targets (74): The "EnsureBindingRedirects" task failed unexpectedly. System.MissingMethodException: Method not found: 'System.String System.Reflection.AssemblyName.get_CultureName()'. at Roxel.BuildTasks.EnsureBindingRedirects.MergeBindingRedirectsForReferences() at Roxel.BuildTasks.EnsureBindingRedirects.Execute() at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask, Boolean& taskResult)

It's strange. Due to a dependency we took with a project we needed to add async to around 40 other projects in the solution (out of the 110). Only a couple of the projects flag with the error above when building on TFS/MSBuild server.

The other issue I'm running into is now my SlowCheetah transforms no longer work at run time. I have to comment out the bcl.targets import in the csproj project file of the exe project as a work around. Which isn't a long term solution.

Thanks!

Neil

re: Microsoft.Bcl.Async is Now Stable

Amenti — Thu, 02 May 2013 06:25:50 GMT

@Immo: Issue with non-AnyCPU configurations. we've updated our version of Microsoft.Bcl.Build. Updating that package should solve this issue.

It works great now. Thanks a lot. :)

re: Microsoft.Bcl.Async is Now Stable

Jernej Kavka — Wed, 01 May 2013 17:24:15 GMT

Microsoft.Bcl.Async is just awsome. :)

I'm making number of presentations in Slovenia presenting this for PCL. :)

re: Microsoft.Bcl.Async is Now Stable

Immo Landwerth [MSFT] — Sat, 27 Apr 2013 02:10:51 GMT

Vagif Abilov: Issues with package Restore. Please see Issue 5 in our known issues list:

blogs.msdn.com/.../asynctargetingpackkb.aspx

@Amenti, Haacked and @Nguy?n: Issue with non-AnyCPU configurations. we've updated our version of Microsoft.Bcl.Build. Updating that package should solve this issue.

@Richard Szalay: You can send me an email under immol at microsoft dot com. Thanks!

@Wolfgang Fuerst: We're looking into it. At first glance it seems like a unification issue in the VS static code analysis feature (FxCop). We've contacted the owners of it. Unfortunately, I don't think there is a workaround other than disabling code analysis for those projects :-(

@Kent Boogaart: Thanks for reporting it. The root cause is that our infrastructure packages (such as Microsoft.Bcl.Build) require Visual Studio 2012/.NET 4.5. We've could probably recompile those packages against .NET 4 but in order to use the async/await keywords you need it to compile your code with .NET 4.5 build & compiler anyways, so this wouldn't help your particular case.

@Werner: Which platform are you targeting? Could be that your application project is missing a reference to Microsoft.Bcl.Async?

re: Microsoft.Bcl.Async is Now Stable

Werner — Fri, 26 Apr 2013 15:53:52 GMT

I had the same problem as described in forums.lhotka.net/.../11927.aspx. The only thing that worked for me was going back to the old async targeting pack.