Visual studio feeds

All Visual Studio blogs in one place


Enter your email address:

Delivered by FeedBurner

Increase your website traffic with



Anti-spam: How many eyes has a typical person?

Follow us on FB


The Morning Brew #2080

AddThis Social Bookmark Button
Software Heads up: TFS 2015.2.1 coming – Brian Harry highlights the planned release of a minor update to TFS 2015 Update 2, being called TFS 2015.2.1 which addresses some of the reported bugs in Update 2 HLSL Tools for Visual Studio v1.0 released – Tim Jones announces the 1.0 release of the HLSL Tools for […]

Azure Service Bus - Purging Queues

AddThis Social Bookmark Button
Testing code that involves queues always has some utility code that is responsible for test cleanup. The cleanup is often implemented as a queue purge operation. For example, MSMQ allows to delete all messages in a queue by calling a Purge() command on a queue. MessageQueue queue = new MessageQueue(".\\exampleQueue"); queue.Purge(); Simple. Convenient. Not possible with Azure Service Bus. There are a few options to handle situations when the purge operation is needed. None of those options is perfect, but is a workable solution until native implementation is provided (vote for the suggestion on UserVoice). Drain messages Draining messages is receiving all of the messages
found. Execution time will depend on a number of messages found in a queue. To make if faster, multiple message receivers can be used. To make it less chatty, receiving mode should be set to ReceiveAndDelete rather than to PeekLock. This will reduce the latency and number of operations. Receive in batches Batching will help with getting as many messages as possible in a single operation. It will be subject to the quotas imposed by the service tier being used. Use async Not need to explain that async operations are much more preferred with IO-based operations. When receiving messages in batches, make sure...(Read whole news on source site)

The Practical Problems of Determining Equality and Equivalence in SQL

AddThis Social Bookmark Button
In theory, it is easy to determine whether data is equal to, greater than or lesser than a value. Real-world data types can be surprisingly tricky, even for gauging data equivalence. Because SQL cannot remain aloof from any application's data types, you need to be aware of the ways and pitfalls of individual datatypes and how you can test for equality, equivalence, similarity, identity and all that jazz. Joe Celko discusses.

Implementing Missing Features in Entity Framework Core – Part 3

AddThis Social Bookmark Button
Back after a few weeks. For those who don’t know, this series of posts is dedicated to bringing some of the futures that existed in Entity Framework but were dropped in Core. You can find the first post here and the second here. This time, an often forgotten feature that didn’t made it to Core: … Continue reading Implementing Missing Features in Entity Framework Core – Part 3

Building strongly typed application configuration utility with Roslyn

AddThis Social Bookmark Button
In this post we will have a look at how, with just several lines of Roslyn code, you can build an extremely cool and powerful utility – a library allowing you to provide configuration for your application as a strongly typed C# script file. This post was inspired by the ConfigR library, which provides this […]

Behavior for view model driven animated popups in Xamarin Forms

AddThis Social Bookmark Button
Preface In my previous post I showed the basics for animation behaviors in Xamarin Forms. Here’s another one I made, that in conjunction with some nifty element binding makes for a pretty fluid popup appearing from the middle. Of course, you can use the native alert box but I’d rather want to see is something as displayed to the right, especially with a nice animation. The advantage of such a custom made popup is that is looks much more consistent across platforms, which is a huge win especially for LOB apps. You can see the behavior in
action below: ... and all there is to it... The actual code is pretty small now all the heavy lifting has been done by the base classes from the previous post:using Wortell.XamarinForms.Behaviors.Base; using Xamarin.Forms; namespace Wortell.XamarinForms.Behaviors { public class AnimateScaleBehavior : AnimateFoldBehaviorBase { protected override void Init(bool newValue) { if (newValue) { FoldOutPosition = 1; FoldInPosition = 0; AssociatedObject.Scale = FoldInPosition; ...(Read whole news on source site)