Re: using PIA'S at the time of deployment
- From: "Willy Denoyette [MVP]" <willy.denoyette@xxxxxxxxxx>
- Date: Mon, 10 Oct 2005 22:20:31 +0200
PIA's do not contain any code, they are simply .NET metadata representing
the COM interfaces exposed by the native COM servers (here Office XP). This
metadata is used by the COM interop layer to manufacture a RCW, but the code
that is called through this wrapper is actually native code in the Office
application (Word.exe or any other office app.)
So when you deploy a solution, you need the PIA's and the Office package
corresponding to the PIA, without the latter your application cannot work.
Another remarks is that Office automation from services like web
applications are not supported by MSFT , it's hard to set-up correctly, they
don't scale, they are memory hungry, you need to take care you aren't
launching multiple instances of the Office application, and there is a
serious licensing issue associated with this.
Willy.
<kunallalwani@xxxxxxxxx> wrote in message
news:1128941660.764230.273350@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi Friends, I have a strange problem, I am using Office XP PIA's to
> extract the text from any office file. I downloaded the office XP PIA,
> and developed a module which extracted text from any file that is
> uploaded to the server using Visual Studio.NET 2003 and .NET Framework
> 1.1. During development the code runs well and gives the proper output.
>
>
> 1)But now i Have to deploy this application on the client side where
> OFFICE XP or Office 2003 might not be installed, in that case where
> will i have to keep those office xp pia's that i have used during my
> development in the bin folder of my web application or the global
> assembly cache?
>
> I experimented a little bit by first running the application on the
> client side where office xp is installed, it ran perfectly and gave me
> the output. But the problem arised when i uninstalled the office xp
> suite and then manually added the files in the global assembly cache
> and registered them in the registry also. At that time it gave me an
> error that CLSID[0029--......] is either not valid or registered
> component but when i checked the assembly folder the
> Microsoft.Interop.Word.dll was present and it was also had an entry in
> the registry. Please help me ....
>
> Thanks in advance
> Kunal Ramesh Lalwani
> Software Developer
> Fahm Softwares
> India
>
.
- References:
- using PIA'S at the time of deployment
- From: kunallalwani
- using PIA'S at the time of deployment
- Prev by Date: "Proper" way to Interop with Unmanaged Dll
- Next by Date: Re: COM-Interface usage in MultiThreaded-Environment fails
- Previous by thread: using PIA'S at the time of deployment
- Next by thread: COM-Interop broken after installing VS 2005
- Index(es):
Relevant Pages
|
