from qTeam in teams select NickName = qTeam.NickName, Population = qTeam.City.Population

Window 10 comes with a new browser: Edge. So maybe you can still give it a try when it comes out.

After having to reset my password on several web accounts, I realized that all someone needs to logon into any of my accounts is my e-mail. All password resetting involves sending me an e-mail. So if someone can receive my e-mail, they can reset all of my internet passwords. How difficult is it to redirect my e-mail somewhere else? Is it just my e-mail password that's required? Or is something else involved?

WPF applications don't need to by async to be responsive. If you want to let WPF do some graphic rendering, just call its dispatcher. No need to use the new Async/AWait stuff.

No, they repeated my license number

But they did know it.

I got an unsolicited phone call from TechStork claiming that I have security errors on my Windows computer. They claimed that they know this because my computer sends them my event log and they know my name a phone number because they know my Microsoft license number. Has anyone gotten such a phone call? And would Windows be sending my event log without my knowledge or consent?

You have programed the bot to make the value judgement that killing 2 people is always better than killing 6.

The 'clean' way is not so clean because C# (and VB) do not have any language constructs to handle them. A function that would return a tuple will require some 'dirty' code to untangle the tuple. I thing tuples were added to .Net to support F#, which does make language constructs to deal with them. Until C# adds similar constructs, I don't see using them.

In VB, a function that returns void is a "Sub". This is true with lambda function as well. So your ForEach lambda should be

ForEach(Sub(item) Thread.Sleep(10))

I like ribbons. You can collapse the ribbon so that just the tabs show. It looks like a menu bar. Then you can add commands to the quick bar which kind of like a tool bar. Window 7 Explorer did away with tool bars. So with Windows 8 you can have a "tool bar" and a "menu bar". You can place the quick bar on the title bar, so it takes up even less real estate. Ribbons are vary flexible.

I've become a ribbon convert. When I first used Microsoft Word with ribbons, I didn't like them because I knew Word's menu system and knew what menu to scan for a function I wanted to perform. But once I learned my way around ribbons, I like them better. I think there easier to find things then the menu/tool bar system. As to "space eating UI": You can collapse the ribbon vertically to just a line of ribbon tabs. Controls within a ribbon can change depending on the horizontal space available down to just a button per group. This you cannot do with tool bars. I wrote an application using ribbons and wound up putting more stuff in the ribbons then I ever could with menus. I think this is a positive thing: it makes my interface more consistent. From a developer's point of view, ribbons take more work because they are more flexible but then you can do more with them. How ugly or pretty they look will depend upon how well you design them. Menu/toolbars just are: you don't have any artistic design decisions.

Maybe you people should upgrade to VS 2010. Microsoft revamp the help system. Its web based even with local help files. And you no longer get the 10 minute waits.

The reason VB'ers don't share is because of people like you. We're afraid to reveal that we write in VB (and feel guilty that we like it).So If you ask us for a sample code, we may try to quickly convert it to C#. But then you would find us out because we would inevitably make a syntax error.

Hey! I like that silly round thingy! I liked my little doggy helper too. Microsoft got rid of that of few releases back. They just don't what you to have any fun!

I Read on a Kindle. The dictionary is just a button away. I find I lookup words I thought I knew because it's so easy.

I was very frustrated with WPF when I first started too, but now I’m loving it. I hardly ever use the tool bar or property sheet. I love WPF’s layout system. You never have to worry about tab order when you add a new control in the middle. My dexterity was always challenged when I had to drag a control into a group. Now I just insert a XAML element where I what it or if I put a control in the wrong place, I can just cut-and-paste the XAML code. When I’m debugging a complicated window, I cut out the more complex graphics until I discover the bug, then paste the graphics back in. The more I work with WPF the more I discover its power. The XAML editor is still immature. I least I’m hopping its InteliSense and outlining will improve.