Jeremy Foster

Jeremy Foster codefoster

Niner since 2012

Jeremy was educated in computer engineering and mathematics, gathered disparate
industry experience in education, aerospace manufacturing, and insurance. With
just enough and not nearly enough education and experience, he finally joined
Microsoft with the goal of informing and inspiring other software developers to
write code and write it right. When he is not working, he is likely spending
time with his wife and son, hiking and camping, sailing, scuba diving, or
working on house projects. Find Jeremy online at @codefoster and




  • CodeChat 067 - The Latest, Greatest Features of C# 7.0

    @Steven: it's a Lumia 830

  • Using Git and GitHub

    @fmorriso: I agree that we didn't do a good job of showing that. The main reason is that I'm more versed in the Git integration in Visual Studio Code than in Visual Studio 2015. Also, I tend to do most of my Git from the command line. I'll try to find some time to do some research on if there's an easy flow like you're talking about and blog about it on Thanks for watching.

  • CodeChat 061 - Talking TypeScript and Angular 2.0 with Bill Wagner

    @geeyef, since Angular is the stuff that gets sent to the client and processed there, it's should be a snap to get it going in whatever server side code you're using (i.e. Node/Express, ASP.NET, PHP, etc.).

    I suggest you start by creating your ASP.NET web app. Then find a good starter project for Angular 2.0. There are a lot of them. You could use my waterbug-ui project as a starting point if you want. Then just copy that project into a folder in your ASP.NET project. A lot of people put it in a folder called public.

    The hard part whenever you're using a client-side framework like Angular inside of a server-side framework like ASP.NET is figuring out what you what code you want to run where. Some sites, pages, and tasks are best executed on the server side, some are best on the client side, and overall you may have a hybrid site. You may even (I hope not) run in scenarios where the server is generating client-side code.

    Modern sites, however, tend to be more simple and single-purpose (and that's a good thing) and will only be either have server-side or a client-side logic. Certainly if you're just learning Angular 2.0 and ASP.NET Core 1.0, then it might be a good idea to learn them separately.

    Good luck!

  • Thursdays with Corey - the new ALIAS feature of AzureCLI

    Where do we find a list of the valid aliases? Are they case sensitive? I tried "Ubuntu" and "ubuntu" and both returned "image-urn or os-disk-vhd parameter is required to create a VM"

  • Web.Dev 2: Getting Started with Angular 2.0

    @Mensur, could have been. They're closing in on me!

  • Web.Dev 2: Getting Started with Angular 2.0

    @ajmacapaz, TypeScript is not required. You can also use plain 'ol JavaScript if you'd rather. I beg you to glance at the advantages of TypeScript before you go down another road though. It's not heavy in terms of learning.

  • CodeChat 057 - INSTEON for Home Automation

    I can't disagree with you @Bob. I tend to chock it up to being a young market, but it's actually not that young. There are just so many standards and proprietary protocols. I'm hoping that AllJoyn creates some sanity in the compatibility of devices, hubs, and devices. I guess we'll see.

  • CodeChat 055 - Stealing Some Time with David Crook

    Dang it. It's because Smith said "Mr. Anderson" that I thought that. Plus I suppose it's been decades since those movies by now. :)

  • The Maker Show: Episode 1 - Intro to Electronics

    @tomhall: We'll work on that. Thanks, Tom.

  • The Maker Show: Meet Your Makers

    @Jamie Dixon: We hear ya! We have at least two gals on the show team, but they had stuff come up just before we recorded that introductory episode. Dang.

  • Building Windows Apps Using the Universal Windows Platform

    @JSRocks, I completely agree that docs and guidance for the JS strategy is weak. I'm just saying that I don't choose to take that to indicate a lack of intent or support. I haven't heard Microsoft say "we want to back off from the strategy of using JavaScript to build Windows apps".

    As time permits, I will be working to get video and other content in place, and will push your feedback (which I concur with strongly) up the chain. Thank you so much for your input.

  • Building Windows Apps Using the Universal Windows Platform

    @JSRocks, don't hear anything that's not being said. Microsoft loves JavaScript all over the place. It is building tools for JavaScript. Shoot, in many cases it's building tools with JavaScript.

    Using HTML/JavaScript is a completely supported scenario in Windows 10 UWP apps.

    It's true that we're heavier on the XAML/C# samples. There are a log of strong cases for using the power of XAML and C# and building a glossy, native app that takes advantage of numerous platform functionalities is one of them. Especially when you're more experienced with C#.

    Don't look for an either or... a this way or that way. We're making tools for the code people are writing, and these days there are a lot of people writing JavaScript. I suppose like anything, that could change, but I can't see it. I'm going to keep writing JavaScript... when it makes good sense.

View All