Microsoft.ReportViewer.ProcessingObjectModel required in GAC?

Question

First, a little background.  Right now we are using manual copy/paste style deployment of a windows application.  Now that everything is stable we wanted to setup ClickOnce deployment.  We had a fully functioning application running at the client site going into this.  My first attempt worked, but it was myself deploying to my dev machine.  When the client tried it they received the error mentioned in the subject.

I did a lot of searching on this issue and all I could find was this:

http://social.msdn.microsoft.com/Forums/en/winformssetup/thread/29155be0-9f27-4ed7-81da-88d1174d6ba8

However, I can assure you we were not trying to install by clicking the .application file, we were indeed using the setup.exe

So, what I did was to check the prerequisite for ReportViewer 2010 and the "Download prerequisites form the same location as my application" checkboxes.  This works, but it has to install the report viewer.  Obviously my app ran fine before ClickOnce was introduced, indicating I had all of the prerequisites installed.

The question is: why did my application work on the client machine before installing the ReportViewer?

---

Ken

Answer 1

[Right now we are using manual copy/paste style deployment of a windows application.  Now that everything is stable we wanted to setup ClickOnce deployment.]
Do you mean you just copy your product related files to the end users PC, and it can run fine for all your end users, right? Or you just test the copy deployment way in your dev PC?

[When the client tried it they received the error mentioned in the subject.]
[Microsoft.ReportViewer.ProcessingObjectModel required in GAC]
When this error message reported to you, it is the Microsoft.ReportViewer.ProcessingObjectModel need to be installed into GAC.
I did not used ReportViewer controls, if you know which installer has this component, then you just need to install it to the end users PC, it would install the assemblies into GAC, I think.

[Obviously my app ran fine before ClickOnce was introduced]
Maybe your test PCs has the old version component.
Or maybe you have your assembly with your output assemblies together, but you exclude the Microsoft.ReportViewer.ProcessingObjectModel component in the "Publish"->"Application Files..." in your project property page.

---

Mike Zhang[MSFT]
MSDN Community Support | Feedback to us

Answer 2

[Right now we are using manual copy/paste style deployment of a windows application. Now that everything is stable we wanted to setup ClickOnce deployment.] Do you mean you just copy your product related files to the end users PC, and it can run fine for all your end users, right? Or you just test the copy deployment way in your dev PC?

We literally copied the entire debug directory onto the clients machine and put a link to the executable on their desktop.

[When the client tried it they received the error mentioned in the subject.] [Microsoft.ReportViewer.ProcessingObjectModel required in GAC] When this error message reported to you, it is the Microsoft.ReportViewer.ProcessingObjectModel need to be installed into GAC. I did not used ReportViewer controls, if you know which installer has this component, then you just need to install it to the end users PC, it would install the assemblies into GAC, I think.

You are correct, but it's not the error that I'm questioning, I know exactly what it means.  It's the "why" that I want answered (see below).

[Obviously my app ran fine before ClickOnce was introduced] Maybe your test PCs has the old version component. Or maybe you have your assembly with your output assemblies together, but you exclude the Microsoft.ReportViewer.ProcessingObjectModel component in the "Publish"->"Application Files..." in your project property page.

There were no test PCs, just the client's machines.  The application has been running fine since January and that DLL was definitely not on their machines.

This seems to me to be a bug in ClickOnce that is detecting a prerequisite that isn't actually needed.

And that brings us back to the original question: why did my app run fine without that DLL before ClickOnce?

---

Ken

Answer 3

[There were no test PCs, just the client's machines.  The application has been running fine since January and that DLL was definitely not on their machines.
This seems to me to be a bug in ClickOnce that is detecting a prerequisite that isn't actually needed.]

Once you test your installer on one PC, then this PC would be a test PC, I'm not meaning the separated test PC.

Do you mean you have not used the ReportViewer component in your project, right? If so, then I don't know how you configured your project make it has this reference, otherwise the ClickOnce will not checked out this dependence. 

[And that brings us back to the original question: why did my app run fine without that DLL before ClickOnce?]

I'm trying to help you find the root cause, but first I need the problem details, so I have the above questions.

If you also cannot solve this issue by yourself after read my post, then can you share me your project? So that I can look into it, and try to look everywhere of it, try to find any clues. [e-mail]

---

Mike Zhang[MSFT]
MSDN Community Support | Feedback to us

Answer 4

I am writing to check the status of the issue on your side.

What about this problem now? 

---

Mike Zhang[MSFT]
MSDN Community Support | Feedback to us