A Quick Parse of the //Build 2015 Session List

I just flicked through the session list for //Build and was making a note of the sessions that (on first pass) line up with my particular set of interests and I thought I’d publish it here given that I was making the list anyway Smile

Note that the list;

  • isn’t sorted or prioritised in any way
  • has been made without any visibility about what’s happening in any of these sessions
  • is long – looks like around 80-100 hours of material to watch here at least
  • would be likely to be revised once the material starts to show up

With a big conference like this, I always watch the keynotes and then I typically make a few folders on my disk;

  • queue
  • watched
    • vital
    • useful
    • other

and I download as many videos as I can into that queue folder and then watch them and, once watched, I partition them across into one of the other 3 folders for future reference. It’s worth saying that ‘other’ category is often a reflection of whether I think the session is of use to me rather than a reflection on a talk.

I do generally download the videos because I can then watch them when travelling and so on and also because I usually watch them at 1.4x speed or similar.

Here’s the big list (so far);

Windows App sessions

Cross Platform App sessions

IoT sessions

Visual Studio sessions

Web sessions

.NET sessions

Azure sessions

Security sessions

Some ‘mystery’ sounding sessions;

“Hello! Hello!”–Fake Microsoft Virus Phone Calls (logmein123.com)

While working at home today I was “lucky” enough to get a call from one of those scammers who rings your house and offers you technical assistance with your PC.

There’s a decent write-up over here on the Guardian’s website of the sort of scam we’re talking about and there are some examples over here of actual conversations where people have been much better than me in that they managed to record the call.

The call ran something like this;

  1. There was an awful lot of “Hello! Hello!” which seemed to go on for quite a while – if you’re going to telephone scam people I recommend investing in a decent headset.
  2. The initial “engineer” told me that he was ringing about the problems that I had with my computer and then remembered to check whether I had a computer and whether I had any problems with it. I said that I did. I’ve got lots of computers and they all have their problems Winking smile I guessed where we might be heading.
  3. He also mentioned “Microsoft” quite a lot and talked about how it’s likely that the warranty on my computer’s software (?) might have “expired” thereby “opening it up to lots of viruses and problems being downloaded from the internet”.
  4. He then led me on a course of diagnostics which involved me finding the CTRL key on my keyboard ( “I want you to look at the keyboard and press the key in the bottom left corner” ) and, from there, to the Windows key and used the R shortcut to get a Run dialog.
  5. He then ran the event viewer.
  6. Once in the event viewer he encouraged me to scroll up and down and count up how many “little yellow triangles” and “little red circles” I could see. I reported that I could see “hundreds”.
  7. He explained that the triangles and circles represented viruses and that they “multiply every twenty four hours” which I found a little bit frightening although I did wonder why they waited so long and what they were doing for the rest of each day Smile
  8. Once “the problem” was clearly demonstrated he handed me over to his supervisor who was a “Microsoft Registered Technician”.
  9. The registered technician checked that I had understood the nature of the problem and then proceeded to get me to run up a browser and go to http://logmein123.com and he wanted me to type in a passcode up there ( 843718 ). Note – I haven’t tried to login on that website and I’ve no idea what kind of malware lurks behind it. You have been warned.

At this point, I decided that I didn’t want to log in to the site so I stalled for a while and then started to ask the supervisor whether it was risky to log in to this site and I mentioned that it didn’t look like a Microsoft site and couldn’t they have spent a little more money on the branding of it?

This opened up the general question of budgets at Microsoft and I could tell that he was starting to get wise as I asked him if he could give me his address and phone number “just in case it goes wrong” and the call ended quickly when I added that I worked for Microsoft and so was curious about a few of the things that he’d just been telling me.

I wasn’t perhaps the ideal candidate for this kind of phone scam and it’s easy to have a laugh at the scammers expense but I can see how it would be very easy to fall for if you’re having some kind of computer trouble and the phone happens to ring at the same time with someone who says “Microsoft” a lot and offers to “help” Sad smile

With that in mind, here’s a “message from our sponsor” providing a legitimate place to go to look for computer security issues for the home user;

image

Catching up on blog reading…

It was very warm and humid last night in Manchester, UK and so I sat up late catching up on a whole bunch of blog-reading that I haven’t done for a few weeks.

I tend to use my blog-reader ( FeedDemon ) in the same way that I use Outlook. I go through everything, delete anything I’m less interested in and then revisit the other stuff at a later point and I thought I’d spend some time today visiting all those posts I’d flagged as interesting. Whilst doing that, I thought I’d share what they were here – note that some of this stuff is a little old now as I’ve not been reading those blogs as frequently as I used to.

I’m sure I was meant to be doing something else but I found a day mostly made up of reading other people’s posts really useful and enjoyable so I reckon it was a day well spent.

WPF

Multi-touch in WPF 4 Beta 1 – this seemed particularly relevant to me based on my recent experiments with multi-touch

Workflow

10-4 Good Buddy, First Look at WF 4

Learning by Example with 4

Introducing the WF4 Designer

Introduction to WF Designer Rehosting (Part 1)

Introduction to WF Designer Rehosting (Part 2)

A Tour on the WF4 Activity Palette

Debugging in Workflow 4

Migration Guidance for the WF Developer

Introduction to Workflow Tracking in .NET Framework 4.0 Beta1

Sequential and Flowchart modeling styles

Mapping WF3 Activities to WF4

Getting started with Windows Workflow Foundation 4

The new Windows Workflow Foundation 4 runtime

Parallel Programming ( lots and lots of goodness in here )

The Nature of TaskCompletionSource

Mechanisms for Creating Tasks

.NET 4 Cancellation Framework

Cancellation in Parallel Extensions

Tasks and the APM Pattern

Tasks and the Event-based Asynchronous Pattern

Tasks and Unhandled Exceptions

Don’t Dispose of Objects You Don’t Own

Partitioning in PLINQ

How PLINQ Processes an IEnumerable on Multiple Cores

Achieving Speedups with Small Parallel Loop Bodies

Parallel Loops over Non Integral Types

CLR 4 – Inside the ThreadPool

Daniel's Updated Parallel Slides for Beta 1

Error Handling in Concurrent Code

WCF

Service Configuration Improvements in .NET 4

Dude, Where's my WCF Content? – I really like the redesign of this developer centre around simplification – seems like a step forward to me. BTW go here for the training kit for WCF/WF 4.

Entity Framework

Updated Entity Framework Documentation for Beta1

POCO in the Entity Framework- Part 1 – The Experience

POCO in the Entity Framework – Part 2 – Complex Types, Deferred Loading and Explicit Loading

POCO in the Entity Framework – Part 3 – Change Tracking with POCO

Using Repository and Unit of Work patterns with Entity Framework 4.0

Announcing- Entity Framework Feature CTP 1

Feature CTP Walkthrough- Self Tracking Entities for Entity Framework

Feature CTP Walkthrough- POCO Templates for Entity Framework

Feature CTP Walkthrough- Code Only for Entity Framework

General

Debugging .NET Dumps in Visual Studio 2010

Security Policy in the V4 CLR

Sandboxing in .NET 4

Security Policy in .NET 4 – Implicit Uses of CAS Policy ( and part 2 )