Visual studio feeds

All Visual Studio blogs in one place

Subscribe

Enter your email address:

Delivered by FeedBurner

Increase your website traffic with Attracta.com

Google+

Contact

Email:
Subject:
Message:
Anti-spam: How many eyes has a typical person?

Follow us on FB

Search

Why are there no “solved problems” in software development?

AddThis Social Bookmark Button
I’ve been on both sides of the stick in software development.  I’ve been a developer, trying to crank out a feature, and thinking “Geeze, I should be able to do this faster…” and “Wait, you mean this API doesn’t do this for me already??”  I’ve also been a product owner, wondering, “Why in the world is this taking so long?  It’s just a form!”  The sad truth is that even a seemingly-simple problem in software development can turn out to be a serious can of worms.  Why is that?  Well, because the devil is in the details, and there is
no such thing as a “solved problem” in software development. Allow me to explain what I mean by a “solved problem.”  By this, I mean a problem that, when confronted by it, we can immediately say, without any hesitation, consideration, or qualification, “Oh, you use X to solve that.”  Can we truly say that for anything in our industry? Most applications have the same fundamental needs: a UI, data storage, and (probably) communication.  If I say, “I need to allow users to enter enter logs about widgets,” can you immediately say “the...(Read whole news on source site)

Review: Chicago Coder Conference

AddThis Social Bookmark Button
Originally posted on: http://geekswithblogs.net/tmurphy/archive/2015/05/19/review-chicago-coder-conference.aspx On May 14th and 15th, 2015 the Chicago Coder Conference was held at the UBS building in downtown Chicago.  PSC Group was a sponsor of the event and had a fair sized contingency in attendance.  This post will review the good, the bad and the ugly of the conference. Let’s start with the bad and the ugly so that we can end on a high note.  The overall organization of the conference was really bad.  It started with the keynote.  They had a venture
capitalist talk about how the funding process works.  Given that most of the people there were employed by a company that sent them there I thought it was a poor choice.  Add to that the fact they timed the sessions without any time built into the schedule to clear rooms and the next speaker to setup and didn’t well publicize the Wi-Fi availability (which was poor) and it didn’t make for a good experience. The best part of the conference was the number of quality presenters from not just Chicago, but around the region.  Unfortunately Chris Woodruff got sick...(Read whole news on source site)

AngularJS Project Essentials

AddThis Social Bookmark Button
You’ve read the tutorials, watched the online demos and wrote the to-do list app in Angular. Now you’ve been assigned your first real world project. You create the project, hook in Angular, and start coding away. “Now what?” After over three years of writing Angular enterprise apps, I’ve found there are a few elements I almost always pull in. I hesitate to call these “best practices” because they are common but not universal, and they are too small to really justify releasing as part of a stand-alone module, so I’ve gathered them here in a single blog post
to share with you. An ng-View to... [[ This is a content summary only. Visit my website for full links, other content, and more! ]]
...(Read whole news on source site)

Integration testing ASP.NET 5 and ASP.NET MVC 6 applications

AddThis Social Bookmark Button
The other day I ran into a post by Alex Zeitler, who blogged about integration testing of ASP.NET MVC 6 controllers. Alex has done some great work for the Web API community in the past and I always enjoy his posts. In this case, Alex suggested using self hosting for that, so spinning up a […]The post Integration testing ASP.NET 5 and ASP.NET MVC 6 applications appeared first on StrathWeb.

Accepting code from the community means accepting full responsibility for all time

AddThis Social Bookmark Button
Sometimes, we’ll reject a certain pull request from the community, not because it doesn’t meet our standards, or doesn’t do things properly. We’ll reject it because we don’t want to accept the responsibility for this. This seems obvious, but I got a comment on my recent post saying: If you e.g. say that you're willing to accept a new F# module within RavenDB that does scripted deploys and automation of various tasks, I bet people would jump in with enthusiasm. I wouldn’t accept such a PR. Not because there is anything wrong with F#, or because it wouldn’t be
valuable. I wouldn’t accept such a PR because none of the core team of RavenDB has great expertise in F#. Oh, we have a few guys that played with it, and would love to do some more. In fact, I’ve got a guy that is pushing hard for allowing RavenDB to run computations via F#. It is a pretty cool feature, and I’ll talk about that in detail in a future post. But imagine the scenario outline in the comment. A F# module that does some automation, scripted deploys, etc in F#. We go over the code, we are happy...(Read whole news on source site)

The Morning Brew #1863

AddThis Social Bookmark Button
Software SQL Server 2014 Service Pack 1 is now available – SQL Server Team – Site Home – MSDN Blogs – The SQL Server Team announce the release of SQL Server 2014 Service Pack 1 which includes all the fixes up to and including Cumulative Update 5 Information When everything you know is wrong, part […]

Entity Framework Multitenancy

AddThis Social Bookmark Button
IntroductionMultitenancy is currently a hot topic in web development. Azure, SharePoint, and many other frameworks are offering multitenant options, because it totally makes sense to make a better use of a server by hosting many different services.When it comes to data, there are usually three different strategies:Separate databases: each tenant is stored in its own database; different connection strings must be provided, one for each tenant;Shared database, separate schemas: all tenant’s data live in the same database and even share table names, but in different schemas;Shared database, shared schema tenants share the same physical tables,  but use
a discriminator column for distinguishing between them.Let’s explore how we can use each of these techniques in Entity Framework (Code First, of course – is there another?).PrerequisitesFirst, we need to have a way to obtain the current tenant, specifically, a tenant id or code. To simplify, let’s just assume a simple interface:

Home