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


SQL SERVER – Computed Column and Conditions with Case Statement

AddThis Social Bookmark Button
When I do not find anything on my blog, I write a blog post about it, so next time I do not have to recreate the scripts from the beginning. Just another day, I was doing performance tuning for an organization, I had to create a computed column with CASE statement and I suddenly realize that I do not have such a script on my blog so I decided to write a blog post on this subject. The post SQL SERVER – Computed Column and Conditions with Case Statement appeared first on Journey to SQL Authority with

Hosting a custom application inside of a CMS is a terrible idea

AddThis Social Bookmark Button
Building applications inside of a content management system is now a failed experiment. A new style of api-first, headless content management systems inverts the relationship and provides a pleasant and productive development process. The Benefits of App-In-CMS The appeal of building an application inside of a CMS is that you get stuff for free. We greedy software developers cannot resist pre-built authentication, security, widgets and of course content management. For very simple, short-lived applications where control over the output or quality engineering are not important then app-in-cms may be OK. Hosting a custom application inside of a CMS is a terrible
idea The old idea about how to merge user editable content into custom applications was to build applications inside of content management systems. Early productivity advantages (such as built-in user management and authentication) are soon overtaken by compromises required to stay within the CMS framework and challenges related to versioning and deployment. Architectural and functional compromises soon leak out and affect the user. It is common to get three months into a CMS-based application development project only to realise that it should have been a standalone application and that the CMS framework is now a liability. When designing and building software...(Read whole news on source site)

Thoughts from a Windows 10 user

AddThis Social Bookmark Button
There’s a lot of speculation at the moment, mostly I think from the tech press, that there’s no future for Windows 10 Mobile (aka Windows Phone). To the point that Terry Myerson apparently released a statement to clarify that Microsoft is committed to mobile for many years. Over the past couple years I’ve been increasingly critical of Microsoft’s mobile strategy as well – it is hard not to be when the platform has such low market share, there’s been a lack of flagship devices released, and there’s still a major issue with apps (that don’t exist or that are quite poor compared to iPhone/Android versions). So at
the beginning of this year I “threw in the towel” and switched to the iPhone. This was after talking to a lot of people in person and via twitter about whether to go iPhone or Android. The overwhelming advice was that if you live in the US you should go iPhone, so I did exactly that. After a couple weeks with the iPhone I wrote a comparison between Windows 10 Mobile and the iPhone – from my perspective. I’m selfish – I’m looking for a good answer for me, so my blog post was about me and my personal experience. After a couple more months...(Read whole news on source site)

The Latest of Microsoft Office Developer Tools: Office Add-in Commands and SharePoint 2016 Support

AddThis Social Bookmark Button
Office’s message at Build was loud and clear: Office is an open market for developers who want to reinvent productivity, backed by a consumer base of 1.2 billion users. Qi Lu welcomed developers to the Office ecosystem in his Build keynote, and showcased new robust extensibility features that enable you to create custom experiences in... Read more

The design of RavenDB 4.0: Voron takes flight

AddThis Social Bookmark Button
RavenDB has been using the low level Esent as our storage engine from day 1. We toyed with building our own storage engine in Munin, but it was only in 2013 that we started pay serious attention to that. A large part of that was the realization that Esent is great, but it isn’t without its own issues and bugs (it is relatively easy to get it into referencing invalid memory, for example, if you run multiple defrag operations), that we have to work around. But two major reasons were behind our decision to invest a lot of time and
effort into building Voron. When a customer has an issue, they don’t care that this is some separate component that is causing it, we need to be able to provide them with an answer, fast. And escalating to Microsoft works, but it is cumbersome and in many cases result in a game of telephone. This can be amusing when you see kids do it, but not so much fun when it is an irate customer with a serious problem on the phone. The second reason is that Esent was not designed for our workload. It has done great by...(Read whole news on source site)

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)