A subset of generic collections is also supported.
(If you’re interested in digging into the details, you can also view the types in the Object Browser using the tools described below.) Supported…
Here’s a laundry list of what’s supported/not supported currently.
The Silverlight 1.1 Alpha is our first crack at it… and it may be refined over the coming months with feedback.
It was a delicate balance to strike between functionality and overall size.
When deciding what aspects of the Visual Basic language and runtime should be included with Silverlight v1.1, we tried to follow a similar pattern: we wanted to preserve the core VB programming experience-late binding, conversions, Linq, and so on and we didn’t want to bloat the download size with anything that wasn’t absolutely necessary or didn’t make sense in Silverlight-things like some of the COM helpers (COM is not supported in Silverlight), financial functions, etc. And although a lot has been removed, the core set of types is included along with some APIs that are particularly useful for writing plug-ins-things like a “lite” version of, support for making web service calls, and so on. NET Framework to keep the download size down and installation time short. Clearly, some things have been factored out of the. NET Framework at 4.2 MB (and hopefully shrinking!). If you’ve had a chance to download the Silverlight 1.1 runtime, you may have noticed that it’s MUCH smaller than the full. NET Framework’s types and APIs I’ve come to rely on. Not to mention that the introduction of VB.NET into the Silverlight world brings with it many of the. While the Javascript model is certainly powerful, using VB is always my preference-it’s a language I know well, and its flexibility suits my programming style. Prior to the announcement of Silverlight 1.1, Silverlight plug-ins were written in XAML and Javascript. And while I’m by no means a Silverlight guru, I have been using it for a little while now and I thought I’d shed some light on what’s out there for VB developers who are interested in trying out Silverlight v1.1. It has only been a few months and a handful codename changes since we had that discussion (For a humorous history of Silverlight’s codenames, check out Tim Sneath’s blog.), and despite a number of obstacles, we’re getting there with the Alpha release of Silverlight v 1.1.
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. 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.