When the Sep 2013 toolkit is installed using NuGet, it also installs AjaxMin v4.97. Everything in my project works normally. In particular, the VS2012 report designer (for RDLC files) lets me add a new DataSet to any report, and displays all of my business object data sources as expected.
Next, if I rerun NuGet, it wants to upgrade AjaxMin to v5.2. If I do, then my project is broken in a very odd way: In the report designer, adding a DataSet doesn’t show any of my business object data sources. Instead, the Data Source Configuration Wizard pops up to help me create a data source from scratch.
This is a mature project and has been working for a long time. I spent a couple of days trying to isolate the problem and reduce the test procedure as much as possible. My conclusion is that AjaxMin v5.2 causes this problem. This is true if I install v5.2 via NuGet or if I download and install it manually.
Is there any known incompatibility between the toolkit and the newer version of AjaxMin?
Comments: I have a very similar situation as the original poster: a mid-sized mature solution (composed of six projects). Everything has been working for a long time, including the report designer. At some point during ongoing development, the report designer stopped letting me select existing business object data sources. Instead, it only wants to create a new data source from a database connection. This cripples development of new reports – I have to use the business object data sources, but it won’t let me. After several days of troubleshooting, I came to the same conclusion as the OP. Here are a few of the particulars if it helps: Our solution has two projects that are class libraries, and one of these uses the Ajax Control Toolkit (which requires AjaxMin). Three other projects are web applications, and two use ACT and AjaxMin, and both have reference to the two libraries above. The only thing usual about this is the library that uses the ACT; I may try to refactor it out to see if it helps. The report designer works normally with the versions below installed by NuGet. However, building the project complains of conflicts between different versions. Apparently, ACT depends on AjaxMin 5.11.5295.12304 rather than the older version that is actually installed at the same time. ``` AjaxControlToolkit 7.1213 AjaxMin 4.97.4951.28483 HtmlAgilityPack 1.4.6 WindowsAzureStorage 4.1.0 ``` Next, I upgrade AjaxMin to the latest version. The report designer then fails to find the business object data sources with the versions below installed. Note there are no more conflict errors. ``` AjaxControlToolkit 7.1213 AjaxMin 5.11.5295.12309 HtmlAgilityPack 1.4.6 WindowsAzureStorage 4.1.0 ``` The above suggests a workaround: When developing a new report, uninstall and reinstall the ACT, which will install AjaxMin 4.97. Then, attach the business object data sources in the report designer. Finally, upgrade to the newer version of AjaxMin (5.11) to resolve the version conflicts. This is a slow and painful process, but it’s better than not being able to develop any new reports.
Next, if I rerun NuGet, it wants to upgrade AjaxMin to v5.2. If I do, then my project is broken in a very odd way: In the report designer, adding a DataSet doesn’t show any of my business object data sources. Instead, the Data Source Configuration Wizard pops up to help me create a data source from scratch.
This is a mature project and has been working for a long time. I spent a couple of days trying to isolate the problem and reduce the test procedure as much as possible. My conclusion is that AjaxMin v5.2 causes this problem. This is true if I install v5.2 via NuGet or if I download and install it manually.
Is there any known incompatibility between the toolkit and the newer version of AjaxMin?
Comments: I have a very similar situation as the original poster: a mid-sized mature solution (composed of six projects). Everything has been working for a long time, including the report designer. At some point during ongoing development, the report designer stopped letting me select existing business object data sources. Instead, it only wants to create a new data source from a database connection. This cripples development of new reports – I have to use the business object data sources, but it won’t let me. After several days of troubleshooting, I came to the same conclusion as the OP. Here are a few of the particulars if it helps: Our solution has two projects that are class libraries, and one of these uses the Ajax Control Toolkit (which requires AjaxMin). Three other projects are web applications, and two use ACT and AjaxMin, and both have reference to the two libraries above. The only thing usual about this is the library that uses the ACT; I may try to refactor it out to see if it helps. The report designer works normally with the versions below installed by NuGet. However, building the project complains of conflicts between different versions. Apparently, ACT depends on AjaxMin 5.11.5295.12304 rather than the older version that is actually installed at the same time. ``` AjaxControlToolkit 7.1213 AjaxMin 4.97.4951.28483 HtmlAgilityPack 1.4.6 WindowsAzureStorage 4.1.0 ``` Next, I upgrade AjaxMin to the latest version. The report designer then fails to find the business object data sources with the versions below installed. Note there are no more conflict errors. ``` AjaxControlToolkit 7.1213 AjaxMin 5.11.5295.12309 HtmlAgilityPack 1.4.6 WindowsAzureStorage 4.1.0 ``` The above suggests a workaround: When developing a new report, uninstall and reinstall the ACT, which will install AjaxMin 4.97. Then, attach the business object data sources in the report designer. Finally, upgrade to the newer version of AjaxMin (5.11) to resolve the version conflicts. This is a slow and painful process, but it’s better than not being able to develop any new reports.