Time for a small recipe of what I needed to do, to get a SQL-Server Express 2014 instance, running on Windows 2012R2, accessible from a remote machine.
Wouldn’t it be awesome if Microsoft and JetBrains could come to an agreement, so that EVERYTHING needed to build an Asp.Net solution, could be resolved from within TeamCity so that we wouldn’t have to make separate installs of msbuild tools and .Net frameworks and, most ANNOYINGLY, the web application targets that so many applies the “manual copy workaround” for.
Recently I had the need to write some tests against a web API returning JSON. I found FrisbyJS which worked really well, and thought: “Why not put together this in C# and .Net?”. So this is what
Requester is. It’s a small lib, that assists you with making HTTP-requests against web APIs and then helps you validates the responses. E.g. validation of JSON-schema etc. Read along and I’ll give you some short intro on how to use it. Please be advised though. It’s an early release.
When it comes to having a GUI for MongoDB on Windows, my previous, preferred software of choice has been Robomongo. Unfortunately (as of current writing) it does not seem to support MongoDB 3.0+ and WiredTiger. Looks like there’s a really good alternative, which I didn’t know about before. Meet: MongoChef.
My never ending quest for finding a build script solution that satisfies my requirements for facilitating builds within .NET might just have come to an end. I’ve gone from Albacore and Rake, to Phantom with Boo syntax, to psake and now finally GulpJS. I’ve glanced at Nant and others and none of the technologies has really “failed“, but there has been drawbacks. Now, I put my faith in GulpJS, which works great for e.g. compiling, minifying and bundling Less resources, but as it turns out, it also works great for managing builds within .NET.
This week has been a bit of a surprise. First I got some questions about NHibernate, which I realized I have been blessed from using since around 2011, then today I got into a small discussion about stored procedures and that it’s viable to let it contain logic. I’m well aware that this is a religious question and that you probably find your self in on camp or the other. Me, I’m more in the camp of no business logic in SPs, but I can see an use-case for it as well. But then again, I’m flexible and try to look at each situation objectively.