I installed 2012.1 (everything) tonight, just to look at the docs to see what's changed. But I have not changed any projects to use 2012.1 yet.
But when I went to recompile my solution, all of the 2011.2 Reporting assemblies are not being found.
I'm still looking into this, but beware!
Mike
Hi Mike,
Different installations of Reporting can’t coexist, therefore when you install 12.1 it performs an upgrade of your previous installation.
You can use version utility to migrate your projects. You have several options for launching the tool:
1. You can open it directly from the Start Menu, look for “Version Utility 2012.1” and then choose the solution or projects you want to migrate.
2. Inside Visual Studio, right click the project or solution you want to migrate and choose “Upgrade Infragistics Version 12.1”
3. Inside Visual Studio, go to Tools -> Upgrade Infragistics Version 12.1, which will close the solution and open the Version utility to migrate it.
By default the Version Utility tool will do a backup of the migrated files.
Currently we don’t have a help topic explaining how to do it, we will write a blog post shortly explaining the steps required. In the meantime, since the process of migrating a solution/project using the version utility is very similar among products you can refer to this document (targeting Winform) to get more information.
Please, let me now if you need any additional help on this.
If you need to downgrade to 11.2 you would need to uninstall 12.1 first and install 11.2 again.
Best,
Leo
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).
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
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.
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,