"Kikoz" <Kikoz@discussions.microsoft.com> wrote in message
news:090E537C-D5FA-4A2F-858E-E00A7BC90B11@microsoft.com...
> Hi all.
>
> I got small app. One of its functions is supposed to interact with user's
> Office 2003 (don't care about earlier versions). This functionality works
> just fine on dev machines if I reference PIA's in VS.2003. But I have no
> idea
> if the end user will have Office 2003 installed (and if he enabled its
> .NET
> programmability during installation). I can, of course, include
> Interop.Outlook.dll and stuff in my setup project and register it in
> user's
> GAC, but first those dlls are very large for my small app (app is 100kb
> and
> Interop.Outlook alone is about 400 kb) and second if my setup will manage
> to
> register my Interop.Outlook in user's GAC then his Office will stop
> working.
> So, my only choice here is to use late binding with some checking if all
> types are loaded. If not, then user doesn't have Office 2003 and app will
> simply disable its Office functionality. Right?
>
> The question: I tried to late bind to Outlook.Application but can't figure
> out how. Can anyone have any articles how to get proper references to
> Office
> 2003 types?
>
> Thanks much,
> Vlad.

"Jim Meyer" <jimmeyer@email.dk> wrote in message
news:ucbv9OG3FHA.3296@TK2MSFTNGP09.phx.gbl...
> Take a look at
> http://www.codeproject.com/csharp/ZetaLateBindingComEvents.asp - it should
> get you started.
>
> Regards,
> Jim
>
>
> "Kikoz" <Kikoz@discussions.microsoft.com> wrote in message
> news:090E537C-D5FA-4A2F-858E-E00A7BC90B11@microsoft.com...
>> Hi all.
>>
>> I got small app. One of its functions is supposed to interact with user's
>> Office 2003 (don't care about earlier versions). This functionality works
>> just fine on dev machines if I reference PIA's in VS.2003. But I have no
>> idea
>> if the end user will have Office 2003 installed (and if he enabled its
>> .NET
>> programmability during installation). I can, of course, include
>> Interop.Outlook.dll and stuff in my setup project and register it in
>> user's
>> GAC, but first those dlls are very large for my small app (app is 100kb
>> and
>> Interop.Outlook alone is about 400 kb) and second if my setup will manage
>> to
>> register my Interop.Outlook in user's GAC then his Office will stop
>> working.
>> So, my only choice here is to use late binding with some checking if all
>> types are loaded. If not, then user doesn't have Office 2003 and app will
>> simply disable its Office functionality. Right?
>>
>> The question: I tried to late bind to Outlook.Application but can't
>> figure
>> out how. Can anyone have any articles how to get proper references to
>> Office
>> 2003 types?
>>
>> Thanks much,
>> Vlad.
>
>