A group blog from members of the VB team
If you’ve held off trying Visual Studio 11 Beta because your .NET 4 or Silverlight 5 app uses the Async CTP, your wait is over!
Today we’ve published the Async Targeting Pack for Visual Studio 11, a NuGet package that lets your Visual Studio 11 projects target .NET 4 and Silverlight 5 while taking advantage of VB11's new Await keyword. While Visual Studio 11 provides built-in support for Await in projects that target .NET 4.5 or .NET for Metro style apps, this targeting pack provides the API support to expand the set of target platforms to include .NET 4 and Silverlight 5 as well.
Check out our release notes for more details on how to install NuGet and add the package reference in Visual Studio 11 Beta, and read Lucian Wischik's blog post for more details.
At this point I'd be tickled pink to know what's going to happen to Silverlight. Too many blog posts out there saying it's dead and I want to start a new app in it next month.
Its too bad this doesnt get picked up as a dependency when using tools like SmartAssembly. i have to ship the DLL manually along side the main, integrated EXE which isnt as clean. Still, the Async stuff is amazing!
I have seen fantastic blogs and I have seen not so fantastic blogs. This blog is very informative in many ways and certainloy ranks in the former category. Really appreciate the information your providing use avid readers!<a href="celabrightreviews.com/.../a>
Nice post! Really a nice discussion is presented by you. I agree everything with you say but one common tools is creating a problem named as Silverlight. Can it works on the runtime also. So i will try it .
<a href="ecommercesoftwarereviewss.com/">ecommerce reviews</a>
Thanks for sharing the information .
It would be excellent to see a broader support for async in SL5 as described in: visualstudio.uservoice.com/.../2939486-enable-add-reference-with-option-generate-asynchr
Async targeting pack is a great move by Microsoft. I was working on a Silverlight project in which I made a lot of asynchronous calls and it was really painful to handle all those callbacks, specially when they depended on each other! When I started using async CTP I realized that it only supported methods with the form of "Begin..." and "End..." naming convention. However most of the service proxies use the "...Async" and "...Completed" convention. So I wrote a simple wrapper library for async CTP (http://slasync.codeplex.com) to make async calls event easier. (You know programmers are always looking for ways to do it even easier!). I am wondering if my wrapper library is still useful?