Application Updater Block

A

AMDRIT

Hello Everyone,

I have an application that uses the application updater block V2. The
application is launched using an appStart assembly first. Everything has
been working great for a few weeks now, until last night when I added
reports to the manifest. I cannot for the life of me determine what is
going on.

I am using the Bits Downloader Provider to update my files. I have created
text files and given them the name of the report files and they transfer
fine. I have take the application.exe file and copied them as the report
file names and it transfers fine. The only time they will not transfer
properly is when they are the actual Crystal Reports. (I will concede that
Crystal has been out to torment my very existence since they came out with
the first version of their product, but this is pushing it.)

I have tested the reports function properly within the application.

Please assist me with this, I am nearing my release date, and I don't want
this to be a road block.

I challenge looking back at the updater code for two reasons: 1. It has
been compiled and unmarred since before the release of this application, and
was never altered from its original source when I downloaded it. 2. It has
been working in the past with both binary and ASCII files.

TIA
 
A

AMDRIT

Apparently the issue is more subtle than it first appeared. While I was
experiencing this issue last night across a couple of development machines,
I cannot replicate the issue now. Perhaps the issue lies with the web
server or the network itself. I will continue to monitor this.

Thanks anyway,
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top