Hey guys,

I have a project that used to use the Classic Controls, but when 2012.1 came out, I manually upgraded all of the classic controls to the Aikido-based controls, as per Taz's blog:

http://community.infragistics.com/blogs/taz_abdeali/archive/2011/11/17/asp-net-product-changes-in-2011-volume-2.aspx

I have been running the 12.1 controls with no problems since then.  Today, I tried using the Version Utility to upgrade to 12.2, and the upgrade failed, with the following upgrade log:

11:54:43: Running User Interface Version 12.2.20122.1000
11:54:43: Gathering volume and assembly information.
11:54:43: Gathering volume and assembly information.
11:54:53: Analyzing LBEWeb.csproj...
11:54:53: The project has references that need to be updated.
11:54:53: We have determined this solution/project/website to have retired ASP.NET controls in the following file C:\TFM\Projects\Product\LBEWeb\LBEWeb\LBEWeb.aspx. NOTE: There could be retired controls in other files too.  The utility cannot proceed any further. Please refer to the following blog post on how retired controls are being handled. http://community.infragistics.com/blogs/taz_abdeali/archive/2011/11/17/asp-net-product-changes-in-2011-volume-2.aspx
11:54:53: Could not load the project. Please see the Log file for more details.
11:54:53: Exception of type 'Infragistics.VersionUtilitySupport.Core.Exceptions.RetiredControlException' was thrown.
11:54:53:    at Infragistics.VersionUtilitySupport.Core.File.Types.WebFile.Analyze()
   at Infragistics.VersionUtilitySupport.Core.File.Types.AdditionalFiles.AddFile(String fileName, List`1 listOfAssemblies)
   at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.CheckProjectForAdditionalFiles(Boolean isSLProject, XmlNode node)
   at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.Analyze()

I have included the LBEWeb.aspx file in question.  I see no references to any classic controls in the file.  I have also checked the .designer.cs file, and there are no classic controls in there either.  The only control that MIGHT be suspicious is the WebSplitter, because I don't see it referenced anywhere in Taz's blog.  Having said that, I'm pretty sure it's Aikido-based as well, so it shouldn't be a problem.

The .aspx file in question references some custom controls from within the project and a master page, and I have also combed through all of them looking for any hint of deprecated controls, and could not find any (in case the Version Utility drills all the way through the page into the controls it's referencing.)

My project only references 2 dll's:

Infragistics4.Web.v12.1

Infragistics4.WebUI.Documents.Reports.v12.1

My Web.config file is referencing the following assemblies:

<add assembly="Infragistics4.Web.v12.1, Version=12.1.20121.1005, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB"/>

<add assembly="Infragistics4.WebUI.Documents.Reports.v12.1, Version=12.1.20121.1005, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB"/>

<add assembly="Infragistics4.WebUI.Documents.Excel.v12.1, Version=12.1.20121.1005, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB"/>

<add assembly="Infragistics4.WebUI.Documents.Word.v12.1, Version=12.1.20121.1005, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB"/>

<add assembly="Infragistics4.WebUI.Documents.IO.v12.1, Version=12.1.20121.1005, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB"/>

Any suggestions are appreciated!

Thanks!

Jamie Foster