June 2016 Blog Posts
Asp.NET Core 1.0 & TFS FTL

Why can’t this stuff just work?

So, I ended up recreating a significant Asp.NET Core solution as trying to upgrade from the previous RC versions just didn’t work.  Even after finally getting it to where it could build and run, I lost Intellisense on any code coming from projects built under .NET Framework.  It wasn’t so so bad, I did it in a couple of afternoons, and though I had some cleanup still remaining (it was having some issues seeing the CSS files associated with it), it was mostly good so I checked it into TFS, in order to share it among various machines, etc.

Apparently, this was a bad idea, as now it can’t build, as I get this error:

 error : Failed to make the following project runnable: XXX (.NETFramework,Version=v4.6.1) reason: Access to the path 'C:\XXX\bin\Debug\net461\win7-x64\EntityFramework.SqlServer.dll' is denied.

Apparently, I’m not the only one with this issue as there are a couple of GitHub open issues about this very thing (they were logged under RC2, but it obviously persists).  None of the suggested workarounds work for me (and didn’t for others as well).

So…I don’t know.  I had basically stopped active development for a month waiting on RTM and thought we were good, but, we are not.

Madness.  Hoping the morning brings some clarity/new ideas.

posted @ Thursday, June 30, 2016 11:46 PM | Feedback (0)
ADO.Net Entity Data Model: Getting column information from a stored procedure that returns data from temp tables

Way back machine on this one.

You need to temporarily add:


To the beginning of the proc for the data model to be able to get the column info.

posted @ Tuesday, June 28, 2016 11:24 PM | Feedback (0)
Penguins 50th Anniversary Logo Update
It was during the first period of the first game of the second round against Washington when I thought to myself for the first time in a long time, “This team is good enough to win the Stanley Cup.” They promptly lost that game, of course, but, in the end, it turns out I was right.
posted @ Saturday, June 18, 2016 5:46 PM | Feedback (0)
Asp.Net Core 1.0 RC2 fail, why? Who knows, it works on my machine, unless it’s the other machine

Related to the previous…..

After deciding that Asp.NET 5 MVC 6 (or whatever it was called) wasn’t quite how they wanted to do it, the brilliant Scotts from Microsoft decided to redo god knows what percentage of the damn thing, and it became Asp.NET Core 1.0.

Fantastic, but fine.  If that’s the direction to go and it makes sense, swell.  Rock the mutha out.

Of course, I then had to upgrade/port/bitchslap a major project that had been built on Asp.NET 5 MVC 6 (or whatever it was called) to Asp.NET Core 1.o.

Awesome.  Fantastic.  It was an exhilarating experience, but I finally pulled it off.

On my SurfacePro 4.  Which builds everything just fine.

But not on my SurfaceBook.  Which has the identical codebase pulled down from TFS, excuse me, Visual Studio Online, but won’t build it, because the updated shiny Asp.NET Core 1.0 RC2 site refuses to import/recognize/grok the .NET 4.5.2 references.  Why?  Who knows, it doesn’t say really.  I thought it might be because various projects had been built on 4.5 or 4.5.1 (even though the SurfacePro 4 didn’t care) so upgraded everything outside the shiny site to that, which of course didn’t fix it.

Which of course I now don’t want to check into TFS, excuse me, Visual Studio Online, because then if I sync my SufacePro 4, it might no longer work because, who the fuck knows why it works on one and not the other in the first place.


posted @ Wednesday, June 15, 2016 11:03 PM | Feedback (0)
Asp.Net Core fail, what a surprise, it’s NuGet related

Rebuilt my SurfaceBook, downloaded all code from TFS, solution has 41 projects, one of which is an upgrade to my most important web site to Asp.Net Core.

I’m on a flight from the west coast back to Chicago.  Every single project builds, except one.  And which one is that?  The Asp.Net Core one, of course.  Why is that?  Oh, it wants to connect to NuGet servers to download whatever it needs, it could actually keep those in TFS so that all packages were there from the start, but apparently not.

So much for using the 4 hours to work on CSS changes since I can’t view the site.  Oh, I guess I could pay for crappy in flight wireless, that would be cool.

posted @ Tuesday, June 14, 2016 12:12 PM | Feedback (0)