Re: Simplifying .NET installation.
From: CR (cr113_at_hotmail.com)
Date: 06/17/04
- Next message: Cor Ligthert: "Re: Group Check (Double Post)"
- Previous message: Roman: "RE: Vanishing Collection"
- In reply to: Cor Ligthert: "Re: Simplifying .NET installation."
- Messages sorted by: [ date ] [ thread ]
Date: 17 Jun 2004 07:18:31 -0700
"Cor Ligthert" <notfirstname@planet.nl> wrote in message news:<uuFy7aFVEHA.2564@TK2MSFTNGP11.phx.gbl>...
Yes. When I build the setup program it creates a setup.exe, setup.ini
and program_name.msi. When I run the setup.exe it installs the
application and then that application will successfully run excel
macros. But if I try to run a different app I get that error message
when I call a macro.
> Hi CR,
>
> And you have build an MSI file?
>
> Cor
>
> > To prepare a PC for my .NET apps I have to run dotnetfx.exe,
> > mdac_typ.exe and .NET setup programs for every single application. I
> > don't mind the dotnetfx.exe and mdac_typ.exe intalls because you only
> > have to do it once. What is annoying is having to run the setups for
> > each individual app. Is there an easier way to do this? In VB6 I was
> > able to run 1 setup program and that covered everything.
> >
> > My apps "almost" work without running individual setup programs,
> > except when I try to call an excel macro. Then I get this error: "File
> > or assembly name Interop.Excel, or one of its dependencies was not
> > found."
> >
> > Could I be calling my excel macro incorrectly?
> >
> > Here is my code for calling a macro:
> >
> > Dim objExcel As Excel.Application
> > objExcel = New Excel.Application
> > objExcel.Workbooks.Open(FileName:="c:\test.xls", ReadOnly:=True)
> > objExcel.Run("test.xls!test.test")
> > objExcel.Quit()
> > objExcel = Nothing
> >
> > Chuck.
- Next message: Cor Ligthert: "Re: Group Check (Double Post)"
- Previous message: Roman: "RE: Vanishing Collection"
- In reply to: Cor Ligthert: "Re: Simplifying .NET installation."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
