Programmatic access to the real time stylus is one of the real OOOH AAAAH features of the Tablet PC SDK 1.7. Larry O’Brien, who is a real tablet developer guru, has written an article on DevX that really digs into this wondrous API. This is not something that you would use in a typical data entry application, but I challenge you go check it out, think out of the box a little, and dream up some interesting scenarios. Aren’t you tired of writing data entry applications anyway? 🙂
Daily Archives: September 22, 2004
Vermont Software Developer Alliance – First meeting Sept 29
The initial website for VTSDA is now live.
If you are a Vermont Software Business or contractor, check it out and register for our first meeting. This is for any technology.
not speaking at Code Camp – but GO! GO! GO!
Although I have given in to the desire to spend a nice fall weekend with my husband and some sorely missed non-geek friends in mid-October, Code Camp II (Oct 15-16th at Microsoft’s Waltham,MA office) is going to be a great event. It is a weekend event – two loooong days filled with so much great content to get you up to speed on a variety of .NET topics. The event is free and there are many well-known speakers presenting.
Help : The Original Human Dilemma
This new book by Garret Keizer, who lives in Vermont, was featured this week in our local weekly, Seven Days.
I look forward to reading this book. It is about how people deal with wanting to help others, how people deal with being helped by others. It is not a book that is set out to answer questions, but to analyze this issue.
I am sitting here filling out paperwork and contracts, doing data entry, thinking about my work and in the meantime, I wonder why I do this stuff instead of hopping on a plane to Haiti or whereever I can to help people in real trouble. Every time I open up my web browser there it is (I have cnn.com as my home page). How do we manage to go about our daily lives. Certainly it is a form of self-preservation. It is a constant struggle for me as someone who is highly empathetic to other people’s troubles.
I recently read a description of a character in The Secret Life of Bees who is empathetic to the point of having created for herself a wailing wall to deal with her uncontrollable grief when she hears about the hardships of even perfect strangers. Things like reading in the newspaper about a car crash where people were killed. Thank goodness this person lives in the 60’s where she is protected from the onslaught of news that we have today. I completely understood this character and saw that she does not have whatever key it is that most of us do have to protect ourselves from internalizing the pain and suffering of others.
VS2005 Beta 1 Refresh and Visualizers
James Avery recently emailed me to see if I had experienced any problems with the refresh and some of the visualizers that I have written in the past.
As I had not yet bothered with the install I couldn’t confirm for him but we got a pointer from Scott Nonnenberg to check that the Microsoft.VisualStudio.Debugger.Visualizers dll was referenced in the project.
Yesterday I got the dvd so I went ahead and uninstalled the beta (but no the framework or other dependent stuff since apparently, the refresh only adds Team System). Then I discovered the same affect that James had. My custom visualizers did not work, but the ones that came with VS did.
Here is how I fixed it.
The quick list:
In your visualizer’s project
– Remove meehost.dll from references.
– Add a reference Microsoft.VisualStudio.Debugger.Visualizers
– Rebuild
– Copy resulting dll to My Documents\Visual Studio\Visualizers
In client application
-be sure that the visualizer’s assembly (dll) is NOT referenced
The Julie-style verbose explanation
The original project referenced meehost.dll. This needs to be removed and replaced with a reference to Microsoft.VisualStudio.Debugger.Visualizers. Note that if you leave meehost in there and add the other, you will learn that they have duplicate classes etc which is why I removed meehost.dll. (This is in the actual project where you build the visualizer). Rebuild the visualizer and copy the assembly into My Documents\Visual Studio\Visualizers folder.
This still did not fix the problem totally as I got a new error that happened on both my custom and the included visualizers. I noticed that my visualizer assembly was referenced in the client project. That shouldn’t be necessary as the visualizer is available to all projects once it’s copied into the (above mentioned) folder. So I removed that and voila – all was well.