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


Excerpts from the RavenDB Performance team report: Optimizing Memory Comparisons

AddThis Social Bookmark Button
Note, this post was written by Federico. Where I had notes or stuff to extend, I explicitly marked it as such. In the previous post after inspecting the decompiled source using ILSpy  we were able to uncover potential things we could do. Getting rid of unwanted type conversion may seem as an small cost, but let’s make an example. Let’s say we are comparing 2 memory arrays of 16 bytes and they are equal (our worst case scenario). Just for the sake of simplification from the 3 potential causes the memory is aligned so there is
no need to the first 2 unwanted conversions. That leaves us with the main body as the only source of unwanted conversions. Now this loops moves our pointer 4 bytes each time and causes 2 conversions. Therefore for a 16 bytes array (a pretty average size) we are performing 8 conversions, that is grand total of 8 conversions. Assuming our idealized processor, at 0.33 ns per conversion instruction we have 2.64 ns or roughly 3% of the total time per average call. Getting rid of that is easy, as the size of an unsigned int is...(Read whole news on source site)


AddThis Social Bookmark Button
December 9th, 2012., was my first day at JetBrains, after being in consultancy for a good 7 years. Hadi Hariri, my new boss, showed the world how new employees are treated. If you know Hadi, that was obviously just for laughs. Not one day have I considered him as a boss, yet as a friend who worked with me on great things. I had a great time in the past two years working with him and the many awesome people at JetBrains. I have traveled a lot, written many blog posts and tutorials (less on my own
blog, I admit) and much, much more. Thanks, JetBrains, thanks, community I have worked with, and thanks, Hadi, for making this an awesome time! It’s been a great opportunity and a great adventure. As a moonlighting project, Xavier Decoster and I have been working on MyGet, a software-as-a-service. It started as a simple prototype, which evolved into a service that hosts thousands of feeds and provides a solution for many developers, OSS projects and companies worldwide. You can find us in the Azure Store, we became VSO Launch partners at TechEd, and we even host nightly builds for...(Read whole news on source site)

The Morning Brew #1786

AddThis Social Bookmark Button
Another Links Only edition today as I’m hoping to make an early escape from work to pick up my (newly unbroken – I hope) car tonight Software Visual Studio 2013 Update 5 CTP 2 Released – John Montgomery Introducing Aurelia – Rob Eisenberg Information Web Reflection: JavaScript and the living ECMAScript Standard – Andrea Giammarchi […]

Entity Framework, Enums, and TINYINT

AddThis Social Bookmark Button
Entity Framework supports Enum properties on your model, but there’s one little gotcha that’s bitten me on more than one occasion now.  In your database, you may be tempted to save space by configuring the backing column to use an integer value that takes up less space than a normal int, such as a TINYINT (byte) or SMALLINT (short).  If you do though, you may get an error like the following: System.InvalidOperationException : The 'State' property on 'Issue' could not be set to a 'System.Byte' value. You must set this property to a non-null value of
type 'IssueState'. It sounds like EF is trying to assign the raw Byte value to the property rather than converting it to an Enum member, and indeed that’s what it’s doing.  Fortunately, the fix is easy: just change the base type of your enum!  By default, enums derive from System.Int32, but you can change that: public enum IssueState : byte { New = 0, InProgress = 1, ReadyForQA = 2, Deferred = 10, Closed = 20 } Now EF will hydrate your entity with...(Read whole news on source site)

On Occam’s Razor and Refactoring

AddThis Social Bookmark Button
Continuing on with my ramblings from last time: refactoring is a powerful tool that can help you transition your application (solution) from the complex end of the spectrum towards the simpler end. Let’s consider our simple problem again: “Given an integer X, find the next integer larger than X.”   And our overly-complex solution: f(x) = (x^2/x) + 1.  Thanks to a little thing called “math,” we can reduce this solution back to its simplest form, our so-called perfect solution, f(x) = x + 1.  I believe this same process holds true in software. 
We can simplify a complex solution we’ve created to arrive at a simpler, more-maintainable one.  One of the best tools we have for making this transition is refactoring.  As we refactor code, we’d like to move up this triangle.  If refactoring doesn’t move us in that direction, then we should consider whether the refactoring is actually beneficial. One thing to keep in mind is that there isn’t a way to simplify every solution.  Sometimes there is no path leading further up the triangle from where you’re at.  If that’s true, it can mean only...(Read whole news on source site)

New Article Published on How to Build a Task App using Swift

AddThis Social Bookmark Button
I have a new in-depth article published online today called, “Creating a Task Application for iOS using Swift”. See below for more information and a link to the online article. Article Introduction In this tutorial, I’ll walk you through building a tasks application for iOS using Swift. This app will allow you to quickly enter and delete tasks like going to the grocery store, etc. It will also lay the foundation needed in order to build native apps with Swift in the future. The Full Article The full article is hosted
on the TDN website and you can access it by clicking here. Don’t forget to rate it and leave comments if you have any problems.
...(Read whole news on source site)

Announcing PostSharp 4.1 Preview 4: Xamarin Support, and More

AddThis Social Bookmark Button
Today we’re excited to announce the release of PostSharp 4.1 Preview 4, available for download on our website and as pre-release packages on our NuGet feeds. We silently released two other previews since our last announcement. PostSharp 4.1 is all about supported new platforms and it is now feature-complete. Let’s see what’s new in the box:Support for XamarinWindows Phone and Windows Visual Studio 2015Conservative NuGet VersioningLocalizable Code ContractsPostSharp Explorer ImprovementsXamarinIt made the top of our UserVoice wish list for a long time: Xamarin is now supported as a first-class member of the .NET family. All features of PostSharp,
including thread safety patterns, INotifyPropertyChanged and undo/redo, are now available for Xamarin through portable class libraries (PCL).How to use PostSharp with a Xamarin project? Just as it works with other projects. Use the smart tag or the light bulb to add a PostSharp aspect, or install the PostSharp NuGet package. It’s that simple.More about Xamarin integration in a later post.Windows Phone and Windows StoreYou could already use create your own PostSharp aspects or use the built-in INotifyPropertyChanged and undo/redo aspects with Windows Phone and WinRT. With PostSharp 4.1, you can now use PostSharp Threading Pattern Library to create truly cross-platform...(Read whole news on source site)