

NET framework to be installed… and runs on the Mac… and Firefox … but supports the full VB.NET language? Uh… Okay, let’s chat.” “Let me get this straight… You want to write a web plug-in VB.NET… that doesn’t require the full. But when some partner teams started asking what it would take to write VB.NET code-behind for a browser plug-in that could run cross-browse andcross-platform, my interest was definitely piqued.
:max_bytes(150000):strip_icc()/SafariPluginsPref-595aa8355f9b58843f9d8a9d.jpg)
Despite my best efforts, the sheer volume of new stuff coming out is a bit overwhelming and maintaining more than a cursory understanding of the products that are incubating at Microsoft is pretty challenging.

It’s always exciting to see ideas take shape, evolve into a product, and eventually hit the market-often after four or five code names, a couple of tech previews, and a few release date/year extensions. One of the great things about being on the VB team is that we’re generally in the loop early and often with teams developing new technologies and products.
