Microsoft and the community did a great job in the complete overhaul of their documentation. I think the documentation is these days much better and also much more discoverable. But for some users is the switch to the code examples in Visual Basic much less discoverable. Better said: hard to find. It’s a littlebit hidden, but if you know how to do it, it’s easy to switch.
In the menu where you can find the bread crumbs of the path of the current topic, you can find default a < / > sign or, in some cases C#. Click on that item and in the popup-menu which is shown, you can select VB. Easy as that!
On Friday, October 13th I will speak about the future of Visual Basic. NET. Microsoft announced earlier this year that they changed their vision on the earlier idea on, what they called, ‘VB and C# Co-evolution’. The plan was – and is actually executed – to give Visual Basic .NET and C# the same language futures. This will change. But what does this mean for Visual Basic .NET developers? How will this affect us? In this session I will discuss these topics. I will talk also about what’s done to make Visual Basic .NET future proof in terms of cross platform development.
I started a new community, named .NET Oost. We will organize meetups in the east of the Netherlands to share knowledge about Microsoft .NET and related technologies. Last week we had our first meetup, where I talked about the basic of SOLID. The audience, mostly students, were very enthousiastic about it. And so was I! If you live in our area, please join our community. It’s free and have a pizza with us!
For two weeks ago my first post about ‘Dependency Injection with Visual Basic .NET’ was published on MSDN. Today the second post went live. In this post I explain the concept of using Inversion of Control containers from Visual Basic .NET code. I think that using these kind of techniques will make your code more maintainable, extensible and testable. Check it out!
I’m proud! Tonight my first blogpost for the Microsoft Visual Basic Team Blog is published on MSDN. In this post I explain the basic concept of dependency injection with Visual Basic .NET example code. This is the first post of a series of two. For those who are interested, please find below a link to the post.
I’m the kind developer who loves shortcuts. I think it makes me more productive. As a fervent user of ReSharper I learned a lot of new shortcuts by forcing myself to learn at least one shortcut a week. ReSharper provides already for years a nice cheat-sheet with al possible and relevant shortcuts. Now you can get one for the plain vanilla Visual Studio environment too!
Are you interested in creating a Console App in Visual Basic and run it on Linux? Or running your Xamarin.Forms-App written in Visual Basic on an iPhone, Android or a Windows Tablet? Thanks to .NET Standard, .NET Core and Visual Studio 2017 Update 3 it is now possible!
My friend Klaus Löffelmann has written – for the VB Team blog on MSDN – an excellent post about cross platform development with Visual Basic.NET. Since the release of Visual Studio 2017 Update 3, you are able to use Xamarin.Forms in combination with a Visual Basic .NET platform. The functionality is still a bit limited to C#, but you can write real, native apps for Android, iOS and Windows UWP!
How cool is that! This post is highly recommended for everyone who wants to learn about the next step in Visual Basic development.
Making decisions is one of the most executed tasks when writing business logic. In Visual Basic .NET you use in most cases an If .. Then .. Else statement or a Select Case statement. In C# there is no big difference, beside the fact that the naming of the keywords is a bit deviant. Let’s start with a simple If .. Then ... Else statement.
Tuples are primitive types where you can easily combine multiple values to one variable. They are as a datatype not completely new for C# 7.0 or Visual Basic 15, but the way you can use them is, with the new System.ValueTuple type, much improved. In this post I will show you how you can take advantage of the streamed syntax of value tuples. The old System.Tuple became not very populair, mainly because the results where not strongly named; you have to use them like result.Item1, result.Item2 etc.