I'm migrating a website made in ASP.NET that was created with Visual Studio 2005 to Visual Studio 2013. When I try to upgrade Infragistics Version 13.1, Version Utility Tools "finds something" that won't let it update the solution. This is the message that I'm getting:
Unknown error (0x80005000) at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_AdsObject() at System.DirectoryServices.PropertyValueCollection.PopulateList() at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName) at System.DirectoryServices.PropertyCollection.get_Item(String propertyName) at Infragistics.VersionUtilitySupport.Core.File.Types.SolutionFile.ModifySolutionEntrySinceItsUsingIIS(String& solutionFileEntry) at Infragistics.VersionUtilitySupport.Core.File.Types.SolutionFile.Analyze()
Please let me know if you need any files to determine the solution to the problem.
Hello Jesus,
Welcome to the community!
What is the version of the product you are trying to update to 13.1? Are you using the VersionUtility shipped with 13.1 or some previous version of the VersionUtility Tool?
If you are migrating prior to NetAdvantage11.2 version to NetAdvantage 13.1, the version utility will not be of help, as the controls set is built on completely different architecture and the code logic should be changed accordingly. In such case simple change in the referenced assemblies will not be sufficient.
Here is a longshot you could try. Please notice, according our official documentation: “There are three editions of the utility depending on the interface used – a command line interface, an Add-in interface and a Stand-Alone application.” So I suggest you try starting the VersionUtility as a standalone application from All Programs/Infragistics/NetAdvantage13.1. Make sure Visual Studio is not running and navigate to the desired project/site to update.
Also if the product you are trying to migrate is 11.2 or later, you could change the references manually, instead of using the VersionUtility.
Reference to the official documentation:
http://help.infragistics.com/doc/ASPNET/2014.1/CLR4.0/?page=Web_Using_Version_Upgrade_Utility.html
You could also reference to the following forum thread for details:
http://ko.infragistics.com/community/forums/t/89510.aspx
Hello Ivaylo, thanks for your answer.
Unfortunately, I don't know what version of the product I'm trying to upgrade, as I've never worked with Infragistics before, and I'm new to the project I'm working on. I was given NetAdvantage_ASPNET_2013.exe to install, though. I tried using the stand-alone application like you said, but the application stopped, claiming that the project had nothing to upgrade. However, I'm not sure if VersionUtility is exactly what I need for my project to work.
Let me explain exactly what the problem is: I was given an ASP.NET website made in vs2005 so I could modify it. I want to open it in vs2013, but when I open it I encounter a couple of errors in the code. Visual Studio doesn't recognize any Infragistics controls. Here's an example:
Inside the <controls> tag there is
<add tagPrefix="igtxt" namespace="Infragistics.WebUI.WebDataInput" assembly="Infragistics2.WebUI.WebDataInput.v10.2, Version=10.2.20102.1011, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb"/>
"Infragistics.WebUI.WebDataInput" is what is not recognized. I have other controls that are recognized, only the Infragistics ones are not.
Also, when I try to run the website, I get this error:
Could not load file or assembly 'Infragistics2.Web.v10.2, Version=10.2.20102.1011, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' or one of its dependencies. The system cannot find the file specified. C:\Users\Kibs\Documents\Visual Studio 2013\Projects\slnCFDECO\CFDECO - cfdi QR\Web.config 55
My Web.config's line 55 is <add assembly="Infragistics2.Web.v10.2, Version=10.2.20102.1011, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB"/>, which is what I think is the problem. I do not know how to solve this, and thought I would be able to get rid of the error by using the Version Utility. So, any ideas on what I can do?
Let me know if you need to know anything else, and thank you for your time.
Hi Infragistics team,
In our project, we are planning to migrate as per below:
1) Win project from v8.2/8.3 to latest version (16.2).
2) WPF v8.2 to latest version (16.2).
3) Asp.net web from v7.2/6.3 to latest version (16.2).
Could you please suggest the best way to migrate in all above cases.
Thanks,
Tarun Parashar
Hey.
Just wanted to let you know that I just found a solution to my problem. Turns out it was all just a reference error. I erased the previous references, which were not being recognized, and updated them to the files I actually had in my computer. I also upgraded them from version 10.2 to 10.3, everything now seems to work as intended. Thanks for your time and help.
Hello once again, Ivaylo.
I see, so there's no helping it. I've given up trying to update the project, then. I've installed Visual Studio 2005 to build the website as it's been previously done, but I keep having errors in the code, hopefully you can help me with this. The thing is, after opening the project on my vs2005, I'm getting the same error:
Could not load file or assembly 'Infragistics2.Web.v10.2, Version=10.2.20102.1011, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' or one of its dependencies. The system cannot find the file specified. C:\Users\Kibs\Documents\Visual Studio 2005\Projects\CFDECO - cfdi QR\Web.config 56
Is there any way I can make this work? The website was running before, and building OK in one of my co-worker's Visual Studio 2005.
It is not possible to upgrade the project using the version utility, as it is as I see from the code shared,using Version=10.2.20102.1011 of our controls. They are different from the controls used in 13.1. They are built on top of different architecture and as such different code logic is used to work with these tools. This includes for example different properties and events. There is no backwards compatibility. So the VersionUtility will not update correctly the references. What is more, even if the references are manually updated to point to the purchased 13.1 version dlls, the project could not be build. This is because the code logic should be completely rewritten. As there are many sources regarding this migration from classic (prior to v11.2) controls, I believe you will find more detailed answer going through the following resources: http://help.infragistics.com/Help/Doc/ASPNET/2012.2/CLR4.0/html/Classic_Control_Migration_Guide.html
http://ko.infragistics.com/community/forums/t/89590.aspx
Please do not hesitate to ask if you have more questions regarding this.