UPDATE: I spelled it wrong, but now that so many RSS readers have it, I won’t change the title ;) It’s spelled Thawte, not Thwate, sorry for the confusion.
I browsed to AgiliTrain (my training company) and noticed that the SSL Cert was failing. Not a good thing. But it wasn’t expired, it couldn’t find the Intermediate Certificates that the issuer requires (I am using Thwate certs). I am not sure why this happens. Unfortunately my old GoDaddy certs didn’t need Intermediate Certificates. My next certs won’t either because it has caused me a lot of wasted time and energy. Much more than I saved going with the cheap Thwate certs.
I had the opportunity tonight to do a talk for the Atlanta XAML Meetup on Web Development for XAML Developers. I had fun explaining how XAML developers can use their existing skills with markup, design, data binding and data access on web page development. You can see the slides from the talk here:
Lesson for today? Function overloads. Coming from that world I wrote simple code like this:
Before I wax poetically about why to use distributed source control, let me talk about what it is (and why it is different).
Back in the very old days (did I mention I am old?) I would keep my source on a floppy disk and put in a safe every night (no, not 9 track tapes like some of you are thinking..I am not *that* old). This was a way to secure the source in case of disaster…but all it did was keep the source secure. Source control was more than that. Later as I used a myriad of source control vendors (yes, including the dreaded Source Safe), they all seemed to have some common features:
I’ve heard a lot of people wonder what’s going on behind my privacy curtain. If you follow me on twitter or notice the time of some of my blog posts, you might conjecture that I never sleep. That argument is not completely without merit. But it got me to thinking that it would be good if I wrote a short post explaining the types of things I do.
My work life is split amongst several types of work:
I will be returning to my 10 part series on Modern Web Development soon, but I have a quickie post that hopefully will help some of you.
So as some of you know, I’ve spent a lot of the last year working on a web project. I’ve been using ASP.NET MVC3 and it’s going well. I am at the point where we are creating the mobile apps. I service them, I need an API (which will eventually be available as a public API too). I had started creating using MVC and simple routes but I was urged to look at the new Web API stack that is installed with the new ASP.NET MVC4 installer.
This is the fifth of ten parts of this blog post. The topics will be:
This is the fourth of ten parts of this blog post. The topics will be:
My new article in DevProConnections Magazine is now live. If you want to see the top ten features of Windows Phone 7.5 (according to me), go see the article now!
If you have any comments, let me know!
This is the third of ten parts of this blog post. The topics will be:
What’s Wrong with CSS?
This is the second of ten parts. The topics will be:
This is the first of ten parts of this blog post. The topics will be:
In the past year I’ve had a side project. FirstInked’s Beta recently shipped and I wanted to share with you what I’ve learned. To start out, I want to specifically thank two people who were really great in helping me formulate the strategies I’ll talk about. They are:
I wasted an evening last night on a simple bug of mine. I was writing a simple HTML data entry page. I was using JSON + $.ajax to POST data to a ASP.NET MVC controller and it used to work. But for the life of me I couldn’t figure out what was wrong. Let’s start with some background.
A long labor of love of mine has finally been birthed. My Essential Windows Phone 7.5 book is now available for Kindle. You can also pre-order the physical book from Amazon or directly from Pearson. While I’ve been assured that the book is printed, sometimes it can take some time to make it into the retail chain for different outlets. To clear up some of this confusion I thought it would be helpful to tell you how you can get the book depending on which retailer you go with:
It’s been a long nine-months and I am excited to be able to talk about what I’ve been working on for the first time. I am working with a small team of people to build a new set of products. But unlike what I’ve been doing in the past, this new set of products is not for developers...
I buy a lot of music. I am not a hoarder like some, but I have 100GB’ish of MP3s. I don’t go around and ‘borrow’ friends collections just to up my count. What I do is buy music…just not at brick and mortar stores.
While I could go on about how iTunes on Windows is a bad piece of software, that’s not what I care about. It’s the DRM. I pave my machines constantly and I have my music on a lot of devices at once. Music Match sounds like a good idea, but Apple has burned that bridge with me a long time ago so I won’t harp on it. But as a consumer of music (and someone who wants to support the artists), what do I do?
So the Windows Phone Marketplace hit 40K apps. What does it mean to the platform? There are a number of articles out there that talk about the 40,000 apps and compares them to other platforms but I think they are missing a key differentiator.
Articles like the PC Magazine article point to the fact that Apple got to 50K in one year (faster than Microsoft) and that it took Android in 18 months (a tad slower than Microsoft). But to me the real remarkable news of this milestone isn’t the speed…it’s the size of the marketplace for that is astounding in my opinion.
As many of my readers know, I’ve been neck deep in the Windows Phone. More recently, I’ve been digging into Windows 8 development as well. On my most recent trip, I spent quite a bit of time with the BUILD tablet. Good news is that it’s a pretty good piece of hardware. Even though it’s not ARM, I am still getting a good four hours of battery life. This version of Windows 8 is early but I do think there are some things that Windows 8 should learn from what they’ve done with the Windows Phone. Here is a short list of what I think the team should look at on the phone:
In-App Back Button
|Implementing and Securing an API with ASP.NET Core (new)|
|Building a Web App with ASP.NET Core, MVC6, EF Core and AngularJS|
|Building a Web App with ASP.NET5, MVC6, EF7, and AngularJS (Retired)|
|Best Practices in ASP.NET: Entities, Validation, and View Models|
|Front-End Web Development Quick Start|
|Lessons from Real World .NET Code Reviews|
|Node.js for .NET Developers|
|Application Name||WilderBlog||Environment Name||Production|
|Application Ver||220.127.116.11||Runtime Framework||.NETCoreApp,Version=v1.1|
|App Path||D:\home\site\wwwroot||Runtime Version||.NET Core 4.6.24628.01|
|Operating System||Microsoft Windows 6.2.9200||Runtime Arch||X86|