Christian, >But just for interest: did you ever try to get this code to run in an >ASP.NET application?
No, there are enough Outlook issues without doing that. <g>. The Outlook library was designed to work on a local client and is not supported in a server environment. If you're trying to access Exchange Server through ASP.NET then you need to use CDO or WebDAV/OLEDB. In the March 2002 Exchange Server SDK there's an ASP.NET Issue Tracking sample that might be of interest. See: http://msdn.microsoft.com/msdn-files/027/001/834/ReadmeDocs.htm - Mike -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of Christian Weyer Sent: May 16, 2002 5:09 PM To: [EMAIL PROTECTED] Subject: [DOTNET] DCOM timeout with outlook.exe (was: Re: get Holidays in an Year) Nice snippet, Mike. But just for interest: did you ever try to get this code to run in an ASP.NET application? Of course I mean after having done all of the necessary security settings ... I still keep getting (on N machines) a timeout when trying to connect to the outlook.exe DCOM server. Any ideas about this? Cheers, Christian --------------------------------- .NET XML Web Services Repertory http://www.xmlwebservices.cc/ --------------------------------- Mike Timms wrote: > The following VB.NET code fragment prints all the holidays registered > in the default Outlook Calendar folder for a specific country and year > in date sequence. The values in the restrict string probably need to > be adjusted to reflect the specific local language setting for the > client. You can check the LanguageSettings property of the Outlook > Application object to determine this. It was tested on Outlook 2002 > but should also work on other versions. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
