Browse by Tags
All Tags »
Office »
.NET (
RSS)
I have come to the realization, at some point, that I never want to close Outlook. Really, there's no reason for me to shut it down except when doing something special, like freeing every available byte of memory, or when developing add-ins to it...
One of the most annoying things about writing add-ins for Office is that it tends to swallow any and all errors that occur. All exceptions are silently thrown into the trash heap without even a statusbar flag. Nothing. This meant that we often had to...
Writing the Outlook add-in described in my previous post was composed of the following steps: 1) Creating the project Ah, the wonders of VSTO. Saving us all the unnecessary hassle of adding COM references, implementing interfaces and working too hard...
Introduction Outlook has always been a bit of a latecomer to the VSTO game, being a step behind and a version later than Word and Excel. I'm glad to see that with Outlook 2007 and VSTO 2005SE it's gotten simpler and easier to write add-ins for...
I'm really surprised at how hard it is to find a good DateTimePicker control that meets all our requirements: 1) Must suppost null dates, like the Due Date datepicker in Outlook tasks. 2) Must be an ActiveX, and supported inside both .NET winforms and...
The hour is late, so I will be brief. If you want to debug an Office 2003 IBF solution, you must have C++ installed as part of your VS.NET 2003 installation. If you click on "Build Solution and Execute Action" and see the build succeed but nothing else...
At last, I have a glowingly positive, happily cheerful and satisfyingly pleased entry instead of my usual rant. I installed the Whidbey Beta 1 build yesterday, and immediately started checking out the beta of VSTOv2. After the grief I went through with...
Just in case someone else is running into this problem: If you're trying to install Office 2003 Professional and want to make sure you install the PIAs as well, you go to the setup components list and look for .NET Programmability Support and are surprised...
Technically, the same smart document can apply to both Word and Excel. In practice, if you want your smart-doc to actually DO something, chance are half your code will be hacked and kludged to work for both. For example: The XML model is different for...
A few tips to keep in mind when developing and debugging a Smart Document using C# (and probably VB.NET too). (For my own selfish ease-of-use, I will refer to Word exclusively here. All these steps should apply to Excel equally). When building the Smart...
More Posts
Next page »