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


What is new in RavenDB 3.0: Indexing backend

AddThis Social Bookmark Button
RavenDB indexes are one of the things that make is more than a simple key/value store. They are incredibly important for us. And like many other pieces in 3.0, they have had a lot of work done, and now they are sparkling & shiny. In this post I’m going to talk about a lot of the backend changes that were made to indexing, making them faster, more reliable and better all around. In the next post, I’ll discuss the actual user visible features we added. Indexing to memory. Time and time again we have seen that actually hitting the disk
is a good way of saying “Sayonara, perf”. In 2.5, we introduced the notion of building new indexes in RAM only, to speed up the I/O for new index creation. With 3.0, we have taken this further and indexes no longer go to disk as often. Instead, we index to an in memory buffer, and only write to disk once we hit a size/time/work limit. At that point, we’ll flush those indexes to disk, and continue to buffer in memory. The idea is to reduce the amount of disk I/O that we do, as well as batch it to reduce the...(Read whole news on source site)

#1,159 – Managing using Directives, part II

AddThis Social Bookmark Button
You can add missing using directives by using the Resolve command.  You can also clean up the current list of using directives in a file, removing the ones that are no longer needed. You can remove unneeded using directives by clicking anywhere within a file and selecting Organize Usings | Remove Unused Usings. In the example below, we start out with 20 using directives at […]

Error saving Galileo Wiring App in Visual Studio

AddThis Social Bookmark Button
Last week I received my Intel Galileo board (from and I started playing with developing for it yesterday. I created a first test project, but it didn’t run. Visual Studio couldn’t find the Arduino header file, which was probably due to a missing NuGet package (the Galileo C++ SDK). I tried to save the project, because you need to before you can manage NuGet packages, but to no avail. Visual Studio served me a ‘The operation could not be completed’ error without any additional information. A while ago I posted about some handy settings in Visual Studio like Zero-impact
projects & Cutting/copying empty lines. Turns out that the Windows for IoT project template does some extra things upon creation. And with the ‘Save new projects when created’ checkbox unchecked, it’s not able to do that. Rendering the project unsaveable…   The solution It’s as easy as it is ugly to have to do this: simply check the checkbox in ‘Save new projects when created’ before creating your Windows for IoT project. Then you’re good to go…! Hope this helps...(Read whole news on source site)

The Morning Brew #1695

AddThis Social Bookmark Button
Information Internal or public? – Eric Lippert discusses access modifiers on members within internal classes, what they actually mean, and where there is debate over the access modifier to use. C# 6.0 Features Part 3: Declaration Expressions – K.Scott Allen continues his series looking at the new features of C#6, exploring declaration expressions which allow […]

APress Deal of the Day 16/September/2014 - Windows 8 and Windows Phone 8 Game Development

AddThis Social Bookmark Button
Originally posted on:’s $10 Deal of the Day from APress at is Windows 8 and Windows Phone 8 Game Development. “Windows 8 and Windows Phone 8 Game Development gives you everything you need to maximize your creativity and produce fantastic games that will run on any Windows 8 device. ”

Demystifying SP2013 Workflow AppStep

AddThis Social Bookmark Button
  A SharePoint 2013 workflow essentially can run as two different accounts.  The current user, or AppStep (which runs the action as the Workflow App account). You will need to activate this feature. But this is not where these notes end.   SP2013 AppStep is not the same as SP2010 Impersonation Step   In SP2010, when you use impersonation step, you gain additional activities, and because SP2010 doesn't have the concept of different permissions impersonations - essentially those activities lets you perform the action with elevated privileges in the code.
  In SP2013, everything is an App.  That includes workflows.  So, when you activate this feature, you gain: Ability to have App Step in your workflow designer (SharePoint Designer or Visual Studio .NET) App Step runs the actions inside with App Permissions, and this is important: the App only has Read and Write.  It does not have full control or manage or any other fancy pants abilities. When App Step updates the list item, you get a nice message on the list item that says Updated by Workflow...(Read whole news on source site)