Force ClickOnce PreRequisite file to deploy with application?

[Dean Slindee]

Using VS2005, I am deploying a WinForm application with ClickOnce. The
project contains a ReportViewer2005 control, so there is a prerequisite for
the ReportViewer2005.dll.

The ReportViewer.dll that is included with Visual Studio 2005 works fine on
my (developer) pc, both within Visual Studio 2005, and after deployed, from
my pc. However, this is not the case with the user's pcs. When they
download the ReportViewer2005.dll from Microsoft, they get a
ReportViewer2005 with built-in bugs.

There is a service pack for ReportViewer2005.dll, but I would rather bundle
the Visual Studio copy of ReportViewer2005 in with the ClickOnce deployment.
It is possible?
On Project properties | publish | Application Files., should I be changing
the Publish Status column to "Include", (Required), and then manually point
to the ClickOnce site where I have copied the Visual Studio
ReportViewer2005.dll? Would this bundle the Visual Studio
ReportViewer2005.dll in with my application?

Thanks in advance,
Dean S

[Steve Gerrard]

Dean Slindee wrote:

Using VS2005, I am deploying a WinForm application with ClickOnce. The project
contains a ReportViewer2005 control, so there is a
prerequisite for the ReportViewer2005.dll.

The ReportViewer.dll that is included with Visual Studio 2005 works
fine on my (developer) pc, both within Visual Studio 2005, and after
deployed, from my pc. However, this is not the case with the user's
pcs. When they download the ReportViewer2005.dll from Microsoft,
they get a ReportViewer2005 with built-in bugs.

Ooo, built in bugs, an extra bonus! :)

>
There is a service pack for ReportViewer2005.dll, but I would rather
bundle the Visual Studio copy of ReportViewer2005 in with the
ClickOnce deployment. It is possible?
On Project properties | publish | Application Files., should I be
changing the Publish Status column to "Include", (Required), and then
manually point to the ClickOnce site where I have copied the Visual
Studio ReportViewer2005.dll? Would this bundle the Visual Studio
ReportViewer2005.dll in with my application?

I would click Include (Required), and include the file right from your dev PC.
The ClickOnce publish copies all those files to the publication folder, so no
need to point it somewhere else. I publish my ClickOnce to a local folder, then
copy it in stages to the actual deployment location. After the first time, I
only copy the updated files up the ladder. My sequence is to publish local, copy
new and updated files to a transfer folder on the server, then remote desktop to
server, where I copy from the transfer folder to the actual folder. Works nice,
gives good control, and the final step is very quick so no interruptions or
synch issues.

[Steve Gerrard]

RobinS wrote:

>
But it sounds like you are only copying the changed files:

>After the first time, I only copy the updated files up the ladder. My
sequence is to publish local, copy new and updated files to a
transfer folder on the server...

Is that true? Or are you copying the whole deployment folder over,
and then continuing?

1. Publish to a local folder, i.e. hit Publish Now button.
2. Copy needed files to deployment server.
3. Copy needed files to deployment folder.

Not really sure what you are asking...

[Steve Gerrard]

RobinS wrote:

>>

Well, whatever makes you happy. :-) I was just curious. I guess in
the interest of easier-for-me, and
making-sure-I-didn't-miss-something, I could just copy the entire
folder, and let it overlay anything that was already there.

But you found something that works for you, so go with it!

RobinS.

Yup. There are some reasons for not publishing directly to the production
server, but they are not interesting ones.

I do sometimes copy the whole folder, only say no to each thing that is already
there and up to date, as a way of checking that I'm not missing something. I
don't have a good reason for not just copying the whole thing, other than habit
I guess.