stdole.dll not in DOTNET 1.1 redist ?

  • Thread starter Thread starter Sagaert Johan
  • Start date Start date
S

Sagaert Johan

Why is this dll not in te redistribution ?
I had problems with a project using an activex (see my earlier posts)

Johan
 
Sagaert Johan said:
Why is this dll not in te redistribution ?
I had problems with a project using an activex (see my earlier posts)

Johan
Click to expand...

Bacause it's a private interop assembly, you have to redistribute it with
your application when deploying.

Willy.
 
Willy Denoyette said:
Bacause it's a private interop assembly, you have to redistribute it with
your application when deploying.

Willy.
Click to expand...

Hi Willy,

but isn't it installed with the PIAs if they need it to work?

Christof
 
Christof Nordiek said:
Hi Willy,

but isn't it installed with the PIAs if they need it to work?

Christof
Click to expand...

Yes, they are, but the PIA's are not part of the runtime, they are installed
when installing Office2003 on a system with .NET installed (or they can be
installed separately like te Office XP webdownload PIA's).

Willy.
 
Willy Denoyette said:
Yes, they are, but the PIA's are not part of the runtime, they are
installed when installing Office2003 on a system with .NET installed (or
they can be installed separately like te Office XP webdownload PIA's).

Willy.
Click to expand...

So, if Word2003 is installed on the target machine including the feature
'.NET Programmability Support', my app should work fine?
On my development machine Office2003 is installed and i'm referencing the
PIA's in the project.
The installation of the target machine i didn't check personally (maybe i'll
do it) but i think if the '.NET Programmability Support' isn't installed the
automation should fail totally.

The only problem i have, is that a word event is handled by my app only on
my development machine but not on the target machine. Same Problem as
Sagaert Johan solved by deploying the stdole.dll.

Christof
 
I don't have office 2003 , the olestd.dll seems to appear on the system
AFTER installing VS.NET.
the IDE seems to include olestd.dll in the references as soon as an activex
is added on the form.
The 'copy local' is false ! Thats why i could only run my app on a system
that had vs 2003 installed.
I tried it on Widbey beta : here the copy local seems to be true by
default.
 
Sagaert Johan said:
I don't have office 2003 , the olestd.dll seems to appear on the system
AFTER installing VS.NET.
the IDE seems to include olestd.dll in the references as soon as an
activex
is added on the form.
The 'copy local' is false ! Thats why i could only run my app on a system
that had vs 2003 installed.
I tried it on Widbey beta : here the copy local seems to be true by
default.
Click to expand...

I never said you needed office2003, I said YOU have to distribute it with
your application, it's a IA generated when you import a COM object for
interop in your project. If you create a deployment project it will be
included automatically.
Make also sure that the COM dll is also deployed or already available (same
version!) on the target system.
Willy.
 
Back
Top