Wrapping Outlook's database...
-
Is it possible to write my own outlook, but only interface (UI) wise? In other words, does Outlook provide access to it's internals (database, code to send recieve email, account information, etc.)? Sammy "A good friend, is like a good book: the inside is better than the cover..."
-
Is it possible to write my own outlook, but only interface (UI) wise? In other words, does Outlook provide access to it's internals (database, code to send recieve email, account information, etc.)? Sammy "A good friend, is like a good book: the inside is better than the cover..."
:wtf: I don't think you want to go there. Outlook does a hell of a lot more than you could possibly imagine. Outlook does expose its object model, though, providing you programmatic access to send emails, enumerate folders and items, and more. I've used this years ago in a couple different scheduling-type applications. You can find more about the Outlook object model - along with simple examples - at Office Solutions Development[^], under which you'll find topics on development and articles outlining different solutions. If you're using Office 2003 Professional (including Enterprise Professional, which is only available with volume purchase orders), be sure to install the Office primary interop assemblies (called something like ".NET Framework Programming Support" or something). If you have Office XP (and they should work in part from '95 up), you can download the PIAs and view information on them at http://msdn.microsoft.com/library/en-us/dnoxpta/html/odc_oxppias.asp[^].
Microsoft MVP, Visual C# My Articles
-
:wtf: I don't think you want to go there. Outlook does a hell of a lot more than you could possibly imagine. Outlook does expose its object model, though, providing you programmatic access to send emails, enumerate folders and items, and more. I've used this years ago in a couple different scheduling-type applications. You can find more about the Outlook object model - along with simple examples - at Office Solutions Development[^], under which you'll find topics on development and articles outlining different solutions. If you're using Office 2003 Professional (including Enterprise Professional, which is only available with volume purchase orders), be sure to install the Office primary interop assemblies (called something like ".NET Framework Programming Support" or something). If you have Office XP (and they should work in part from '95 up), you can download the PIAs and view information on them at http://msdn.microsoft.com/library/en-us/dnoxpta/html/odc_oxppias.asp[^].
Microsoft MVP, Visual C# My Articles
You are a wealth of information, knock on wood! Heath Stewart wrote: be sure to install the Office primary interop assemblies I did. How can I use them? Should they be added to that folder where the mshtml interop assembly is? Sammy "A good friend, is like a good book: the inside is better than the cover..."
-
You are a wealth of information, knock on wood! Heath Stewart wrote: be sure to install the Office primary interop assemblies I did. How can I use them? Should they be added to that folder where the mshtml interop assembly is? Sammy "A good friend, is like a good book: the inside is better than the cover..."
Just run the batch script in the PIA folder if you haven't already. This installs them into the Global Assembly Cache (GAC), which makes them available to all .NET applications without having duplicate assemblies in your application folder. For that matter, the Microsoft.mshtml.dll assembly should be in the the GAC as well if you installed VS.NET. The GAC is a far better place to put assemblies that multiple applications could use because it fosters assembly versioning and is non-specific to any one application. You only need to add a reference to these assemblies in VS.NET for your project, then. IIRC, the Office XP PIAs do not install a registry key that VS.NET uses to find assemblies in folders (the references dialog does not scan the GAC). To do this, open the registry editor (regedit.exe), go to HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework\AssemblyFolders and add a new key with the default value set to the folder in which your PIAs are located. See the other keys there for examples. Restart VS.NET and when you open the Add Reference dialog, you'll them listed.
Microsoft MVP, Visual C# My Articles