Hi Mike,

Actually, you don't need to install NA Reporting in the Build Server. I'd include the reporting DLL in a 'dependencies' folder in your source control tree, and have the projects have references to them. This will also solve the issue of having the installer removing the assemblies you were referencing.

Regards,

Andres

Thanks for the rational. It helps.

But one big problem remaining is that we can't use a single build machine to build the current product and build patched version of older products, because the assemblies required by the older products will no longer be there. We would have to update the old projects to use the new assemblies, which seems wrong when all we really want to do is change a line or two of code which has nothing to do with Infragistics.

Mike

Hi Mike,

Thanks for your feedback.

The main issue is that we cannot have two version of the Reporting designer installed in Visual Studio. When you open a Report, VS will use the installed add-in to open it.. If you go to 'Preview', it will use the code that is in the VS add-in to render it, not the one from the assemblies you have in your project.

On the other hand, if you have a project with the assemblies copied locally, so they are not removed by the 12.1 installed, the reports will work with 11.2 in runtime. When you open them, they will be edited in the 12.1 editor but in this version it's back-compatible so that would be fine. When you run them, they will be run with the in 11.2 runtime.

One solution to this issue could be enabling having 2 reporting designers installed in VS, but that will require you selecting which one you want to use somehow, and also having multiple 'New Report' templates, one per each option version, which will make the experience more complicated for the user. I agree that it could make sense in some scenarios, so we'll be researching this path.

I also agree that this should be communicated better in our documentation. We are starting to work on that.

Thanks for your patience.

Andres

In yesterday's webcast, your folks made a point of almost boasting about being able to install multiple versions side-by-side. And every other component (including Reporting Help and Samples) kept the previous versions.

I consider this to be a very serious bug! This must be dealt with ASAP.

We did not want to upgrade yet (we're way too close to release), so we were going to stay with 2011.2. I only installed 2012.1 to see what was new, having been told explicitly that this wouldn't cause problems. Now I'm left cleaning up a real mess (not to mention what my boss must be thinking).

Mike