If you’re using Visual Studio Code or another text editor to work on your ASP.NET Core web app then you’ll want to know how to add (and start using) MVC.
Not sure if you should learn .NET Core yet? It’s new, shiny and all the cool kids are using it, but is Core right for you?
Keep your controllers thin using the command pattern and MediatR
We’ve recently adopted the excellent S#arp Architecture for our projects. I highly recommend taking a look at the project site.
On Friday I created a simple WCF service using S#arp’s Northwind sample site for reference.
Using WcfTestClient I located my service and attempted to test one of the methods, only to get the following error.
Could not load file or assembly ‘Castle.Windsor, Version=22.214.171.124, Culture=neutral, PublicKeyToken=407dd0808d44fbdc’ or one of its dependencies. The system cannot find the file specified.
Other posts in this series: Part 1 Part 3 (AJAX) Slow progress is still progress don’t yer know
First off, I can only apologise for the decades which have passed since I put up part one of this post, as it happens part two is extremely straightforward.
To briefly recap part one, we introduced several helper methods that enabled us to render a site menu using unordered lists.
Other posts in this series: Part 2 Part 3 (AJAX) One of the key differences between ASP.NET Web forms and ASP.NET MVC is that WebForms contained many controls which you could use on your web pages and MVC doesn’t.
Not that this is a bad thing, the difficult thing about WebForms was the horrendous html they generated and the hoops you had to go through to gain fine control over them.
One of the exciting aspects of asp.net mvc is it’s inherent support for Test Driven Devleopment.
This post outlines how to make NUnit and RhinoMocks appear as options when generating a test project during creation of a new MVC app.
And an updated post for Preview 3