Feeds:
Posts
Comments

We’re excited to announce plans to simultaneously ship Visual Assist X 10.6 with Visual Studio 2010 this Spring!  As a Visual Studio Industry Partner, we’ve been working hard to make sure the features you’ve come to expect from Visual Assist X are ready to boost your productivity with Microsoft’s latest IDE.  Visit our beta forum to keep tabs on the latest Visual Studio 2010 developments.

We are pleased to announce a new beta build of Visual Assist X for Visual Studio 2010 Beta 2.

Get all the details in our forums.

VA X in VS2010 Update

With Visual Studio 2010 Beta 2 released last week, we want to get our next Beta of VA X out as soon as we can.  We are currently working through some breaking changes introduced in Beta 2, but we hope to resolve these quickly and get a build out in the next week or two.

Thanks for your patience, and we’ll keep you updated…

Enhanced suggestions

In our latest builds of Visual Assist X, we’ve been sneaking in some enhancements from our work on the upcoming Visual Studio 2010 beta. We decided to roll these features out early so our users could start enjoying them in currently supported IDEs with out having to wait for the full VS2010 beta. Hope you enjoy!

Enhanced suggestions are one of the items we’ve added.

VA now offers smarter suggestions based on types in assignments, conditional statements, method arguments and return values. For example, when assigning to a variable “v = “, VA will suggest other variables of the same type from the current scope. For certain types such as bool, VA will also suggest relevant values (“true” and “false”).  In method calls, VA looks at the method signature and makes suggestions based on the type of the current argument. Suggestions are also offered for return values, based on the method’s return type.

EnhancedSuggestions

Enhanced suggestions are influenced by scope.  For example, VA suggests case/break/default in switch statements and private/protected/public in class definitions. Within a switch statement on an enum, VA suggests the enum items in the case statements.

You may also notice that our suggestions as a whole are less noisy, take up less screen real estate and are more accurate. They contain less of the stuff you will likely never type and better guesses at what you are likely to type. Suggestion listbox tooltips only display once you pause typing, reducing distraction and saving valuable screen real estate, yet preserving the additional information for when you need it. We hope you like the changes!

Give the latest build a try and tell us what you think.

VA X in VS2010

As an excuse for not posting for four months, we’ve been hard at work on some new things, one of which has been getting Visual Assist X ready for Visual Studio 2010.

VS2010: VAX and C++/CLI

VS2010: VA X and C++/CLI

So how are we doing?  Well, Microsoft seems to have challenged themselves to see how much they can change for VS2010 — new WPF shell, snazzy text editor, MEF-based extensibility, VSIX installers, C++ build system, oh my. This is a major release both on the surface and under the hood, and the changes have impacted VA X on all sides.  But we’re happy to report we have VA X running in VS2010, and we are currently shaking out bugs.

We are excited by the possibilities of the new WPF text editor, as it will enable new VA X features that simply were not possible in earlier IDEs.  But for now, most of our time has been spent simply trying to achieve feature parity with what we already do in the older IDEs.  Once we’ve done that, we can begin the real brainstorming for what’s ahead.

We’ll be releasing a beta of our VS2010 support when Microsoft releases their next public beta.  So until then we’ll post some morsels here to whet your appetite.

Add Include

We recently released a feature for C/C++ that has long been requested: Add Include.  A lot of work had previously been put into our #include completion listboxes – but that work is moot because now you don’t need to type #includes directives by hand.

The Add Include command is available when you place the caret on a symbol which is declared in a header file that is not directly included in the active file.

If the header that the symbol is defined in is already directly included in the current file, the command is disabled.  Otherwise, it is enabled – even though the dependency may already be satisfied by another directive that itself #includes the header.  This is by design as many programming style guidelines mandate explicit inclusion of declarations (as opposed to happenstance or indirect inclusion).

For types and functions, Add Include straightforwardly adds an include directive for the header in which the type or function is declared.  For variables that are declared in the active file, Add Include acts on the type of the variable (no need to go to the declaration of the variable to add the include for its type).  For variables that are not declared in the active file, Add Include operates in the same way as it does for types and functions.

While the command is available in the usual VA Refactor menus, the easiest way to invoke it (at least for keyboardists) is to place the caret on a symbol and press alt+x, r, n.


VA Snippet Tip #1

VA Snippets support a number of reserved strings that enable text substitution when inserted into the text editor.  For example, any occurrence of $selected$ in a snippet is replaced with the actual text editor selection at the time the snippet was invoked.

As noted in a previous post, VA Snippets support shortcuts.  You wouldn’t want to use the $selected$ reserved string with a snippet that you want to invoke via a shortcut since typing the shortcut will overwrite your text selection (in this case, occurrences of $selected$ would simply be removed from the snippet when it is inserted into the text editor).

Instead of using the $selected$ reserved string, use $clipboard$.

Now you can use a shortcut to invoke the snippet with one small extra step:

  • Make your text selection
  • Copy (or Cut)
  • Type the shortcut and accept the snippet suggestion

Methods in File

Here’s a quickie…

When you are in a source window, pressing Alt+M displays the VA X Methods in File list.

Did you know you can filter the list by typing after the list is displayed?  Yeah, most people know that.

Did you know you can filter using multiple strings as in the OFIS and FSIS dialogs?  You can, as of build 1645 (2008.07.10).  The filter supports the use of ‘-’ to exclude items.

Several members of the Whole Tomato Software crew attended the Seattle XNA Gamefest held back in July.  It was a great opportunity for us to get face time with quite a few of our customers.  We received a lot of feedback some of which has bubbled up in VA X 10.5.

We learned that many Visual Studio users only work in the IDE for editing and debugging but not for doing builds.  Because it is not being used for builds, people are working with solutions that are empty or are incomplete, adhoc file collections.

To address editing and navigation productivity in these scenarios, we have added optional support for directory based file discovery. If enabled, VA X will scan for files that are in the same directory as any opened file.  Newly discovered files (those which are not already explicitly listed in the solution) are treated as part of the solution in the eyes of VA X.  The files are listed in the VA X file lists (OFIS and VA View) and symbols declared in them are listed in the VA X symbol lists (FSIS and VA View).

File discovery is controlled via two settings on the Projects|File Handling node of the VA X Options dialog.  The first setting enables this support for only when the loaded solution is empty.  The second enables it independently for when files are present in the loaded solution.  The first setting is enabled by default whereas the second is disabled.  If you use partial solutions as described above, then we recommend enabling the second option.

Yesterday, I posted about a new feature in VA X 10.5.  I failed to mention that the new feature is only supported in Visual Studio versions starting with Visual Studio.NET (vs2002+).  While we continue to support VC++ 6, not all features we introduce going forward will be available in that environment.  That said, we don’t currently have any plans to end VC++ 6 support.

For those of you still using VC++ 6, care to share why?  Are you still using the VC++ 6 compiler and libraries, or have you modified the build environment to use different tools?

Older Posts »