1. Trace the execution of BizTalk processes end-to-end, covering both messaging and orchestrations. While this seems obvious at first, it can be tough on complex solutions that rely heavily on pub/sub and direct binding!
2. Discovering the reasons why a service instance might be getting suspended. In particular, quickly finding any possible exception information coming from faulted instances.
3. Using the orchestration debugger to figure out where a given Orchestration instance is getting suspended.
4. Matching any receive shapes in an orchestration to the origin of messages coming for it. This might require matching logical ports with physical ports as well as possible direct-binding sources of messages.
5. Tracking possible reasons for routing failures, particularly when correlations are involved. This includes being able to understand routing failure reports, checking the state of any required promoted property, comparing subscription information either directly on the message box as well as from reading orchestration code, and so on.
6. Detecting and solving situations that stop flow/processing of messages, related to thread pool issues or thread starvation.
7. Detecting zombie message instances and their possible consequences.
8. Knowing how to enable the BAM tracing infrastructure to debug and solve issues with BAM not writing data to the BAM primary import database.
9. Using the Visual Studio Debugger or WinDBG to debug BizTalk processes. This includes figuring out the right processes to attach to!
10. Debugging assembly-loading/versioning issues. This includes how to use Fuslogvw.exe and friends.

Anyone else has any other ideas?

I did have to struggle with a couple of things. For example, I originally installed that machine with Xubuntu a long time ago and then converted to GNome. The Karmic upgrade enabled Xubuntu as the default again and configured XFCE as the default session, but that’s easy enough to fix. I can’t seem to find where to change my logon screen to the one I was using, though.

The big issue issues I’m running on, however, are related to what I use my machine the most for :

• I had to change some of my scripts for mounting Windows shares in other machines as specifying the rw option to mount was no longer working. No errors, just mounting read-only instead. To fix this, I had to add the file_mode=0777 and dir_mode=0777 options to the mount command. No big deal, but took me a few Google searches to figure it out.
• Building C/C++ apps/libraries on a samba share doesn’t work anymore, as GCC will always fail with a “Value too large for the defined data type” error. I’m basically hitting the bug described in this bug report. I do hope it gets fixed soon, as otherwise I will have to get back to 9.04, which does work fine. Meanwhile, I’ll try setting up another VM with 9.04 to see if I can get some work done. Ouch!

This week I took a bit of time to uninstall the RC and install the RTM version of Windows Virtual PC. Notice that I have no interest in XP mode, merely in running my existing VMs, many of which are running Windows Server 2003.

A couple of things worth pointing out from this sad experience:

• Updating Virtual PC from the RC to RTM took me 4 reboots. Seriously screwed up in this day and age, but I fully blame it on…
• The ungodly bad UI that Windows Virtual PC uses. The old Virtual PC console was a bad UI, but getting rid of it and replacing it with a shell extension, and one that forces you to keep your virtual machine definition files in a specific folder and has terrible usability was an incredibly stupid choice. No wonder so many reboots are needed for any updates, since Windows Explorer will get in the way.
• After updating the integration components on my Windows Server 2003 virtual machines, imagine my surprise at seeing: (a) virtual pc locking the VM and wanting me to log in pretty often, (b) no way to change VM resolution from inside the VM and without ClearType being used to render fonts at all.

And then I remembered what causes this: Windows Virtual PC sort of ditches the old display rendering and instead will use RDP to access your VM (so you’re pretty much working in a sort of embedded RDP client). Windows Server 2003 didn’t support ClearType over RDP originally, so I went hunting for KB946633 and install it on my VM. One more restart, and ClearType was enabled.

This is supposed to be progress, ladies and gentlemen.

What I like

• After fooling around with my Windows configuration, font rendering on beta 2 looks a bit better than it used to do in beta 1, which is great. It’s now on par with VS2008, I’d say (and zoomed text looks awesome). The only exception here is the rendering of line numbers, which is pretty bad, for whatever reason.
• One of the issues I had commented earlier about background color handling in the editor seems to have been improved. Not sure how well it will work in practice, but the new behavior seems a lot better and more useful. Here’s a quick look at how the same line looks like normally, with a breakpoint and as the current statement:

  

• You can now change the colors used when highlighting a collapsible region so that it doesn’t screw up with your custom color scheme. I still find the feature fairly useless, though, but maybe it’s just me.
• Easy horizontal splitting of code windows is back. Yay!

  

• The IDE seems a bit more stable (beta 1 was pretty bad). I haven’t had any bad crashes yet. If you’re writing Visual Studio Extensions, though, be aware that VS handling of exceptions thrown by extensions (particularly editor-related ones) is still absolutely awful. It will crash, and it will do so badly. You might get a fairly useless dialog box before the crash, if you’re lucky.
• Vertical Selection is back. Sorely needed. The Insert-In-Vertical-Selection bit is useful, but I’ve had that with ViEmu for years on previous VS versions. (By the way, there’s a slight bug in this feature in Beta 2: if you want to insert text at the start of multiple lines, you need to block-select the first char, type in the new text and then fix the first chars of the lines that you overwrote. If you make instead an empty vertical selection first, insertion will go very wrong).
• The new C# signature help tooltips are pretty nice. They contain useful information, and they look pretty good. They are very much easier to read than the old VS2008 tooltips.

   

  I do have one complain here, and it’s the lack of consistency: These nice tooltips only appear if you use the Intellisense –> Parameter Info command (usually bound to Ctrl + Shift + Space). If you just hover the mouse over a method, you get a tooltip with the same info, but without all the nice formatting (looking very much like the VS2008 ones, just maybe in a different color).
  

  But it goes a bit beyond that. For example, those uglier tooltips use fixed-with fonts for all the text. One more inconsistency is that the tooltips shown when a member is selected in the IntelliSense completion list dropdown have the almost the same contents as the other two cases, but this time rendered in a proportional font instead. At least be consistent about it in all places! It would be awesome if all of them used the really nice thing the new formatted tooltips do: render the description text was in a proportional font and leave the signature in a monospaced font.

What I don’t like so much

• Editor Performance: When it comes to actually editing text, the editor is still not very fast. It’s a bit better in some spots than beta 1, and in general redrawing of the screen is fairly good, though I still see a very, very slight delay when typing text fast.

  Part of the problem here is that I’m running VS2010 on a Virtual Machine (and one running Win7 at that, which isn’t exactly snappy). Without hardware acceleration, the WPF-based text editor doesn’t quite perform as well as one would like. On the other hand, this is pretty much the standard setup for a lot of developers out there, so just ignoring this isn’t really an option for lots of us (not sure if it’s something MS cares about, though).

  The part where performance is pretty bad, in my specific experience, is scrolling: Right now, scrolling in the editor is absolutely awful. It is very slow, regardless of whether you are scrolling by simply moving around with the caret or using the scrollbar. Really hope this gets fixed.

  As an aside: I did try running VS2010 through RDP (terminal services). The experience was pretty much the same: It works reasonably OK as long as you have a large enough bandwidth between the two machines to enable all the graphics features (particularly ClearType, without which the editor is not as nice). Scrolling still sucks the big one over RDP. For more restricted connections, I’m not sure yet usable the editor will be.

• Italics: Still not there. Seriously screwed up that we’ll have to wait another 3 years to get one stupid checkbox added to the Fonts & Colors option dialog to enable italics fonts on our configurations. The text editor itself does fully support italics and they look beautiful; you just have to hack your way around it to enable them (or use extensions that forces part of the text to render as italics). Not a happy panda about this.

I had already worked around some problems my custom classifier was causing with Beta 2 related to it’s use of a recursive invocation of the classifier services, but @noahsmark proposed a better way to get this done in Beta 2 that would simplify the code a bit and get rid of the need to do the recursive invocation in the first place. This involved switching away from a custom classifier and instead implementing a custom ITagger<ClassificationTag> service instead.

The end result (to the user) is the same, but the code is definitely cleaner! In retrospect, though, naming the extension “KeywordClassifier” might not have been the best choice .

I reworked the code to avoid this call and instead manually create a new geometry directly out of the line bounds (which I would always do anyway to adjust the margins). This seems to work pretty well for now. Here’s a screenshot of how it looks like on the new build:

As usual, the updated code can be found in the GitHub repository.

Here’s a list of the most important changes that were required:

1. The IEnvironment interface is gone, and this affected a few signatures of methods in the extensibility interfaces.
2. The [VsCatalogName] attribute is also gone, and needed to be removed from the assembly.
3. The *.vsixmanifest file now needs to be always named source.extension.vsixmanifest, and it needs to be added to your VS project with the action set to “None”. Otherwise, you will get a build error.
4. The schema for the VSIX manifest file has changed, so I had to update it by hand. Most changes aren’t too big, mostly the case of elements and attributes. I did get stuck a bit here after incorrectly changing my <Components/> section, but @noahsmark helped me get it resolved. Thanks!

Other than this, the process has been mostly straightforward.

You can get the updated code for my KeywordClassifier extension from the GitHub repository. Here’s a screenshot of how it looks like in the new beta:

I’ve also updated the code of my LineAdornments extension, and the updated code is in the GitHub repository as well. Unfortunately, I seem to have hit an issue with this one that I haven’t managed to resolve successfully yet, which I’ll mention on another post.

Mark was also gracious enough to propose the fix, which I’ve now committed to the PipelineTesting GIT repository, along with a unit test to make sure the problem doesn’t come up again. Thanks a lot, Mark!