Dotnet Core Build Error in Docker: Resource file “**/*.resx” cannot be found

While building my new .NET Core project using Docker I ran into an error with the two stage build:

/usr/share/dotnet/sdk/2.0.0/Microsoft.Common.CurrentVersion.targets(2924,5): error MSB3552: Resource file “**/*.resx” cannot be found. [/Hapthorn.csproj]
The command ‘/bin/sh -c dotnet publish -c Release -o out’ returned a non-zero code: 1

The problem it turned out was that while trying to tune my Dockerfile I’d accidentally removed the WORKDIR directive. As a result MSBuild was interpreting the *.resx as an absolute path instead of a grouping/collection directive.

To fix it I put back in a WORKDIR /src directive in my Dockerfile.

Quick and easy!

Advice for .NET Web Developers: Learn the command-line!

Visual Studio has spoiled us .NET developers. In Visual Studio we have a GUI that does everything for us: compiling, source-control, editing, you don’t even have to remember class or method names because of auto-complete and parameter guessing! It is all there and it holds your hand and it feels safe and easy.

The next version of ASP.NET is going to use a lot of the web functionality that many .NET devs have never seen: NPM, Bower, Grunt, and others. Visual Studio will probably cover the front-end of those things, but it will be invaluable for you to learn them the way they were meant to be used: from the command-line.

Those Dangerous UpdatePanels and “The Intern”

At my current contract I am saddled working with an intern. He’s a bright kid, and he’s gone through three years of school, but I’m kind of staggered by how much he doesn’t actually know! Development is extremely difficult because he doesn’t know much about JavaScript, AJAX, jQuery, CSS styling and positioning, Web Services, C#, UpdatePanels, LINQ, Ruby on Rails, MVC, DLL Libraries, ReSharper, and the list goes on and on! It’s hard to believe what eight years of experience teaches you, and I’m finding it difficult, and sometimes limiting because I have to move at a slower speed bringing him up to speed.

I was using some cool features of jQuery to do AJAX instead of using UpdatePanels, but when The Intern wanted to do some AJAX he got totally lost. In the end I taught him to use both jQuery and (despite how dangerous it is), Ihow to use UpdatePanels.  In the end I encouraged him to use the UpdatePanel with his pages, read on to find out why.

Continue reading “Those Dangerous UpdatePanels and “The Intern””

Comparing Open Source ORM: SubSonic vs. NHibernate

ORM tools are probably one of the most time-saving tools for a web developer.  Nothing is more tedious than building a data access layer, adding caching or coordinating transactions.  Well okay, sometimes things like that are really fun, but when you’re trying to start a project out from scratch you want to get something up and running ASAP to show to your customers.

In the .NET world there are two powerful ORM tools out there, NHibernate and SubSonic.  NHibernate is based on the successful and popular Java EE ORM Hibernate.  SubSonic is an entirely new ORM developed in the Ruby on Rails ActiveRecord development model, with some nice .NET 2.0 features like Controllers that you can use with ObjectDataSource controls.

For a recent project I quickly evaluated both software tools, and I’m publishing what I learned here.

Continue reading “Comparing Open Source ORM: SubSonic vs. NHibernate”

Those Dangerous UpdatePanels

I’ve read the post from Encosia (Dave Ward) before, but I was reminded on the Twitter by MasterMaq about how dangerous UpdatePanels are a week or two ago.

Okay, UpdatePanels aren’t dangerous, but they do use more bandwidth and server CPU than a simple web service call.  I figure a web developer ought to know what is being sent behind the scenes, but I can understand that a lot of people don’t.  UpdatePanels require sending the ViewState and building the control structure behind the scenes, as well as doing a subset of the ASP.NET Page event model, which means more data being POSTed behind the scenes and it takes a little longer to do all that processing.

UpdatePanels are easy though, and for some things in ASP.NET it is so much easier to use.  But Encosia does give us an awesome was to still use ASP.NET User Controls within web services and jQuery gives us some awesome tools to build pages dynamically without using UpdatePanels here: http://encosia.com/2008/02/05/boost-aspnet-performance-with-deferred-content-loading/.  It’s not quite as easy to maintain as UpdatePanels, but it’s still very easy to use, and also very very fast.

CodeIgniter Thoughts

I’m finding CodeIgniter a little frustrating right now.  I really wanted to use an MVC tool, but CI is not playing well with IIS.  Also, the documentation really isn’t that great, even for an open-source project.

Alas, like most PHP projects it just wasn’t designed or tested with IIS in mind.  Fortunately I’m discovering this relatively early in the project, but I’m a little frustrated that some of these things are coming up now.

I think given the choice, since the IIS setup was decided for me before, I might have push ASP.NET Forms (vs MVC) instead.  Something I’ll keep in mind for next time.

Of course, CodeIgniter does work much better on my local Apache development environment.  I don’t want to come down too hard on it.  I’m just not impressed with how it works on IIS.