I'm putting the finishing touches on my sessions for Tech Ed South Africa next week. If you haven't booked yet, there are still some places, it seems, so book now (good luck getting flights from C.T. though!)
I'll be giving a couple of sessions this year, so I hope to see you there. My breakout sessions are:
- WEB303 - Performance and Scalability in ASP.NET Development
- DEV310 - Understanding LINQ To SQL
- SOA203 - Introduction to Windows Workflow Foundation
And I'll be giving the following Chalk 'n Talks:
- CNT230 - Developing Solutions with LINQ To SQL – Lessons From The Trenches
- CNT234 - Practical Code Generation With Microsoft's T4 Engine
The full agenda for Tech Ed is at http://www.teched.co.za/agenda.aspx. There are a lot of sessions this year, so it should be a bumper event.
In this VSX How Do I Video, we look at how to add Code Snippet functionality to your language service.
For reasons unbeknownst to me, MS have not yet posted the actual initial video on Language Services in 2008 yet *->.
Screen shot for code snippets:
In this video, I cover how to add Intellisense functionality to your custom language service. The video covers Statement/Word Completion and QuickInfo. I can see this coming to a LOLCode Language Service near you!
Here's a screen shot:
I've been a bit bogged down, so I haven't noticed some of the recent Visual Studio eXtensibility (VSX) How Do I videos going live. I see that How Do I: Work With Other Combo Box Types? is now available. It's a follow on to an earlier video which covered adding a standard combo box, and it includes adding an Indexed Combo, a Most-Recently Used (MRU) Combo (like the Find combo in Visual Studio) and a Dynamic Combo (Like the Zoom combo in most PDF viewers).
Here's a screenshot:
I've made use of the Log property on the DataContext class in a few of my LINQ To SQL posts. Usually, it's been in a console application, and we're just looking at the SQL output in the console window, so we use:
dataContext.Log = Console.Out;
However, in a web application, this won't help. If you want to see the output of your SQL directly in the page, you can use:
System.IO.StreamWriter httpResponseStreamWriter = new StreamWriter(HttpContext.Current.Response.OutputStream);
dc.Log = httpResponseStreamWriter;
As to whether it's a good idea to display this directly into the output (effectively Response.Write) - that's up to you ;->. As an alternative, as Log is just expecting a TextWriter, you could use a StringBuilder with a StringWriter, and then display it's output in a label.
For a more robust solution, Kris Vandermotten has a sample on Sending the LINQ To SQL log to the debugger output window.