Installer in VS2005

[Rick]

Hi guys, i made an app using C# (vs2005) and i added some references to MS
Excel in my project, when i try to install the app in a machine it begins
but at some time it says "Cant find file My_App_Name.app lication" (that file
exist at the directory when im publishing the installer), the closes itself,
but i can execute my app because there are a shortcut in desktop, my problem
is my app is not installing necesary dlls to work, and in my project
properties -> publish ->Application Files it has in Download Group column
Interop.Excel.d ll, Interop.Microso ft.Office.Core. dll and Interop.VBIDE.d ll
as Required and in Publish Status column as Include(Auto) all them.

but the specific report that uses excel doesn't works, it crashes, whats
wrong in my publish configuration?? or how can i make an installer like VB6
style to include all dlls?

Thanks all.

[SP]

"Rick" <za*******@gmai l.com> wrote in message
news:e$******** ******@TK2MSFTN GP15.phx.gbl...

Hi guys, i made an app using C# (vs2005) and i added some references to MS
Excel in my project, when i try to install the app in a machine it begins
but at some time it says "Cant find file My_App_Name.app lication" (that
file exist at the directory when im publishing the installer), the closes
itself, but i can execute my app because there are a shortcut in desktop,
my problem is my app is not installing necesary dlls to work, and in my
project properties -> publish ->Application Files it has in Download
Group column Interop.Excel.d ll, Interop.Microso ft.Office.Core. dll and
Interop.VBIDE.d ll as Required and in Publish Status column as
Include(Auto) all them.

but the specific report that uses excel doesn't works, it crashes, whats
wrong in my publish configuration?? or how can i make an installer like
VB6 style to include all dlls?

I just dealt with this last week so here is my take on it. Publish is using
the ClickOnce method of deployment and is installed in a very different way
than using an MSI. I found it easy to mismatch things mainly because of the
security model. For example you have to resign the manifest if you change
files etc. Click Once has some great features but you must understand it
well. I ended up using the Setup and Deployment project that creates a
traditional MSI. Both Click Once and the Setup and Deployment have the
prerequsites option to include the framework, SQL Server Express, MDAC etc
which can be downloaded from Microsoft's website so that you can keep the
installation file small. My SQL Server based application with a large sample
database and extensive help files was a 20Mb file.

HTH

SP