Before the Cloud, there was a lot of focus on deployment, as if deployment was success. Once you shipped the project, it was time to move on to the next project. And project success was measured in terms of “on time” and “on budget.” If you could deploy things quickly, you were a super shipper. Of course, what we learned was that if you simply throw things over the wall and hope they stick, it’s not very successful. "If you build it" ... users don't always come. It was easy to confuse shipping projects on
time and on budget with business impact
. But let's compound the problem. The Development Hump The big hump of software development was the hump in the middle—A big development hump. And that hump was followed by a big deployment hump (installing software, fixing issues, dealing with deployment hassles, etc.) So not only were development cycles long, but deployment was tough, too. Because development cycles were long, and deployment was so tough, it was easy to confuse effort for value
. Cloud Changes the Hump Now, let's turn it around. With the...(Read whole news on source site)
Many developers prefer to strong name sign their assemblies. The reason for this is to establish trust with the consumers of their applications: the signature proves that the code was built by the person who claims to be the author, and can be verified using a certificate. Signing code also means that the dependencies that are consumed must be signed. Not all third-party dependencies are signed, though, for example when consuming packages from NuGet
. Some are signed, some are unsigned, and the only way to know is when at compile time when we see this:
a signed assembly cannot consume an unsigned one. Now what if we really need that dependency but don’t want to lose the fact that we can easily update it usign NuGet… Turns out there is a NuGet package for that! The Assembly Strong Naming Toolkit
can be installed into our project, after which we can use the NuGet Package Manager Console to sign referenced assemblies. There is also the .NET Assembly Strong-Name Signer
by Werner van Deventer, which provides us with a nice UI as well. The problem is that the above tools only sign the assemblies once...(Read whole news on source site)
I was in London speaking at the inaugural “Native Summit” event yesterday; hosted at the really excellent Genesis Cinema; this was an all-platforms “native app” event with a great line up of speakers; and I put together a talk with a slightly tongue-in-cheek...(read more
If you have been following this blog at all, you must have heard quite a lot about Voron. If you haven’t been paying attention, you can watch my talk about it at length, or you can get the executive summary below.
The executive summary is that Voron is a high performance low level transactional storage engine, which was written from scratch by Hibernating Rhinos with the intent to move most / all of our infrastructure to it. RavenDB 3.0 can run on either Voron or Esent, and show comparable performance using either one.
More importantly, because Voron was created by us, this
means that we can do more with it, optimize it exactly to our own needs and requirements. And yes, one of those would be running on Linux machines.
But more important, having Voron also allows us to create dedicated database solutions much more easily. One of those is RavenFS, obviously, but we have additional offering that are just waiting to get out and blow you minds away....(Read whole news on source site)
Using the earlier custom pie shape control as a base, we can now create a custom control that serves as a circular progress indicator. Here’s the code for the circular progress control: Here’s an example of using this control in XAML. The example also includes a traditional progress bar, so that we can compare them. Finally, here’s […]
Leaving Plitvice behind us
, we crossed the country heading for the sea. We didn't need to cover a lot of distance, to discover how diverse the Croatian landscape and climate is. In only two hours we went from the cold, foggy lakes and waterfalls to green meadows to dusty mountains to sunbathing coasts.
We followed the coastline for a little while, strolling through old coast towns, eating seafood, drinking something cold. Driving up North and more inland, we spent two days in Motovun, a picturesque town high on a mountain.
We'll be continuing up North, slowly making our way home.
...(Read whole news on source site)
This blog post shows an implementation of Conway’s Game of Life using functional techniques in Swift. This results in code which is a clear and concise representation of the game’s logic. I also take a closer look at ranges, intervals, the pattern match operator, ~= and how local functions help...
This post was motivated by a conversation with Salvador Gascon
). Might even go to the pitfalls section
… Anyway, the problem is: how many ways there are to delete an entity in NHibernate? And what are the advantages/disadvantages of each?First, we have the classic one, using ISession.Delete()
, which all NHibernate developers should be familiar with:
left; color: black; line-height: 12pt; overflow: visible; font-family: "Courier New", courier, monospace; font-size: 8pt; direction: ltr; background-color: rgb(244, 244, 244);">
1: var product = session.Get(id); 2:
“I don’t know, why are you asking me such hard questions? It is new, it is better, go away and let me play with the fun stuff, I think that I got the distributed commit to work faster now. Don’t you have a real job to do?”
That, more or less, was my response when I was told asked that we really do need a “What has changed” list for RavenDB. And after some kicking and screaming, I agreed that this is indeed something that is probably not going to be optional. While I would love to just put a sticker
saying “It is better, buy it!”, I don’t think that RavenDB is targeting that target demographic.
There is a reason why I didn’t want to compile such a list. Work on RavenDB 3.0 actually started before 2.5 was even out, and currently it encompass 1,270 resolved issues and 21,710 commits. The team size (as in people actually paid to work on this on this full time, excluding any outside contributions) grew to just over 20. And we had close to two years of work. In other words, this release represent a lot of work.
The small list that I had compiled contained...(Read whole news on source site)
Software September 2014 .NET Security Updates – The .NET Framework Team announce the latest round of patches fro the .NET Framework released as a part of the ‘patch Tuesday’ release cycle September 2014 updates for Internet Explorer – Gege Wang of the Internet Explorer team also highlights their contribution to the Patch Tuesday releases with […]