One of the overlooked or simply misunderstood features of the VB language is calling a function which has a ByRef parameter. Most languages support only a single method of passing parameters by reference , that is the scenarios directly supported by the CLR.
Code snippets were introduced in the Visual Basic 2005 release. They provide an easy way to learn how to do a particular coding task, or to re-use a piece of code in various parts of your application. Code snippets can be inserted in a variety of ways.
The VB Catch syntax has a unique feature: When. It allows users to filter expressions based on something other than their type. Any arbitrary code can enter a When block to decide whether or not to handle an Exception.
<span>Catch </span>ex <span>As </span>Exception <span>When </span>Filter(ex)
Newsgroups often ask,
Did you know that Sara Ford just recently passed the 300 mark for her Visual Studio Tips & Tricks? Sara used to be a tester on the Visual Studio Core IDE team, and knows the IDE inside and out! I remember the first time I met Sara was 4 years ago when she was writing some automation and called to find out the expected behavior for arrowing over tab stops in VB. 🙂 Now she works on CodePlex,
I’m happy to announce that the PInvoke Interop Assistant tool is now available on CodePlex. This includes the binaries, source code and the dev authored unit tests.
It is hosted on the more general CLR Interop Tools page.
Do you use code snippets (introduced in VB 2005)? If you do, then you’ve probably noticed the green highlighting that stays around for the lifetime of the file. We’ve heard *a lot* of feedback that once you are done customizing the snippet,
Jared here again.
I very excited to announce we recently released a tool I’ve been working on to MSDN that will greatly help with using PInvoke in managed code. The tool is called the “PInvoke Interop Assistant” and is included as part of a MSDN article on marshalling data for PInvoke and Reverse PInvoke scenarios.
Our goal in designing VB2008 IntelliSense was to make users of the feature the most productive that they could be. One problem we found in watching people use the feature, is that sometimes intelliSense displays so many items that it is hard to know whether or not you’re close to the item you’re looking for.
There’s a lot of cool functionality built into VS debugger datatips that often goes unnoticed… For example, did you know that not only can you *see* values in the expanded datatips, but you can also edit them? Watch the following walk-through…
Just like Alt+Tab for Windows you can use Ctrl+Tab for Visual Studio. Ctrl+Tab will show you the active tool windows *and* the active files, so it is a good navigation tool for both. VS2008 has even added a cool miniature-sized visualization to this view,