I am working to upgrade our application that uses Infragistics 2005 v5.3 to use Infragistics 2009 v9.1. I used the version upgrade utility to have the solution upgraded. However, I am stuck with an error saying:
The type 'Infragistics.WebUI.WebDataInput.WebTextEdit' is defined in an assembly that is not referenced. You must add a reference to assembly 'Infragistics.WebUI.WebDataInput.v5.3, Version=5.3.20053.1106, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb'.
I am baffled why the code would look for reference for Infragistics 2005. The 2005 version is not referenced anywhere in the solution. I have updated the web.config to use 2009 version. All the references have been cleaned. I read in another blog that it could be a license issue and wiping the data within License.licx file might help. Tried that but did not work. Is WebTextEdit not available in 2009 version? What am I missing??
WebTextEdit is available in 2009 version. It seems that you may have missed cleaning some references. I would double check again for old references. Also try to remove any WebTextEdit and WebDataInput controls from your app and drag-n-drop the same from your Visual Studio toolbox.
Related
I am using VS 2017. I have this line in my packages.config file.
<package id="System.IdentityModel.Tokens.Jwt" version="4.0.4.403061554" targetFramework="net461" />
I got this error my trying to start my .net application.
System.TypeLoadException: Could not load type 'System.IdentityModel.Tokens.NamedKeySecurityKeyIdentifierClause' from assembly 'System.IdentityModel.Tokens.Jwt, Version=5.2.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Because System.IdentityModel.Tokens.NamedKeySecurityKeyIdentifierClause really does not exist in version 5.2.1.0. But it seem NuGet simply ignores the version specification, and always loads the latest version.
I have tried to clean NuGet caches, clean and rebuild entire solution, and restart computer...
Is there anything else I can do?
Update
One strange thing I observed in VS 2017. Notice the differences of the icons for System.Data and System.IdentityModel.Tokens.Jwt. When I try to check the properties of the latter, VS says the package is not installed, which it clearly did. The build went successful, but the application just wont load the right version.
There are a couple of steps you can perform to check that the right version is loaded:
Rebuild your solution to make sure all NuGet packages are restored and that the started application is up to date (You already did that).
Check the tag HintPath for the reference in the project file that references the package. Just open the file in a text editor and look for an XML tag starting with <Reference Include="System.IdentityModel.Tokens.Jwt. Make sure that no version-specific reference is set or that the version matches the version in the packages.config file.
Check in the properties of the according reference in Visual Studio that it is resolved correctly. That means, there must be no yellow exclamation-mark icon on the reference in the solution explorer and in the properties of the reference, the Path entry must point to the installed package. Hence, the path should point to the packages directory inside your solution directory and therein into a directory System.IdentityModel.Tokens.Jwt.4.0.4.403061554.
In most cases (from my experience), there is some mismatch between the reference in the packages.config file and in the project file. If that does not help, make sure that no other module is loaded by your application that has a reference to System.IdentityModel.Tokens.Jwt in version 5.2.1.0.
So far, it is still unclear why VS cannot handle the changes of the NuGet packages, and why it thinks my project is using both .Net Framework and .Net Standard at the same time. I bet it is a but in VS, and hope MS can fix it soon.
Before that, installing Rider and use it to fix the packages, then went back to VS, and everything went back to normal.
I'm looking for the current version of VSLangProj150.dll but I can't seem to find it anywhere.
I have this version, VSLangProj150.15.0.26228 retrieved from nuget but I believe this is an old version because: 1) it was published on 4/13/2017 and 2) it only contains a single interface called PackageReferences which is empty and a VsProjReferencesPropId150 enum with only two values.
Today, I've installed VS 2017 v15.5 and included the Visual Studio SDK component, but I can't seem to find the dll anywhere on my system.
It appears that there is a new version because I've seen references on the web that refers to VSProject4 and Reference6 which are defined in VSLangProj150. And I've found this reference in NuGet.Clients that reads:
AsVsProject4.PackageRefereences?.InstalledPackages
Or am I missing something?
Found it! Must manually get it from nuget.org using VSLangProj150 Version 1.0.0 or as I did, I just added the following:
<package id="VSLangProj150" version="1.0.0" targetFramework="net46" />
to my packages.config file and then let VS 2017 automatically restore any of my missing packages!
Today after updating our projects it seems Xunit.KRunner is no longer available on NuGet. We checked the Microsoft projects and it looks like they are using the xunit.runner.kre package. When trying to install this the xunit.assert assemly is failing to download from Nuget. Any suggestions to get this working? I am guessing that the versions are messed up.
Here are my nuget package locations:
I'm also using the beta2 version of the kre.
There is/was an issue with the new xunit.runner.kre and VS CTP 5. See below discussion:
https://github.com/aspnet/Testing/issues/65
xunit.runner.xre is available only on myget/vnext feed. Include that in the Nuget.config that you should be able to restore the package
By running on the beta2 kre you're then having mismatched dependencies. If you look at the versions of your xunit bits they're all beta3. I'd recommend upping your kre to beta3 to fix your issue (will affect which packages your app pulls in).
Also as a side note I'd recommend ensuring your nuget.org/api/v2/ feed is enabled (in the SS you posted it wasn't). There's currently an issue where it'll occasionally disable itself; has definitely made my life frustrating several times when things don't build :).
This question actually is an implicit answer, since I could fix the problem in the meantime for myself. But I wanted to publish my experience, since some other developers might have a similar problems.
The problem:
I am using VS2010 prof SP1 on Windows XP SP3, pure C++ only. (AntiVirus software present).
Since some days Intellisense - which is quite helpful under normal conditions - does not work anymore.
Things tried:
created a new simple console application. -> Intellisense still not working.
resetting VS-Settings by means of Tools/Import & Export Settings/Reset. -> Intellisense still not working
Changes to option settings in Text-Editor/C++/Advanced inclusive logging did not help.
-> Intellisense still not working
There was actually an interesting observation:
Intellisense normally creates a directory 'ipch' in the solution directory to store intermediate files. In my solution folders it disappeared as soon as the solution was opened. When I created a folder 'ipch' and opened the solution Intellisense removed the folder again - strange.
The final fix:
During the last week some new Windows updates were installed. I noticed some other unusual behaviour of my PC as well. After having created an image of my PC, I decided to
uninstall Windows updates from 2013-09-11 (4 packages) and one update from 2013-08-28.
(unfortunately I did not note down the KB-numbers)
AND: out of a sudden Intellisense is working again !
Maybe this report could be helpful for some other persons.
Automatic Updates are now disabled on my PCs.
Confirmed 100%
Microsoft Visual Studio 2010 Version 10.0.30319.1 RTMRel
Microsoft NET framework 4.0.30319 RTMRel
Microsoft Windows XP Professional Version 2002 Service Pack 3
Intellisense stops working after installing KB2876217.
Intellisense is back after removing update.
I had the same problem and also had the idea that one of the Windows Updates is buggy, so I can confirm your report.
I tried to uninstall them one-b<-one and found the "bad guy":
KB2876217 destroys intellisense for VS2010 under XP SP3.
A supported hotfix is available from Microsoft to fix this issue. Check at http://support.microsoft.com/kb/2526044/en-us
Actually, it may not be such a good idea to uninstall update KB2876217. Instead, install Visual Studio SP1 update (if not already installed) and then install update KB2526044. I have tried it before and it does work...
How do I get rid of this build error in my winforms app?
Error 121 The type 'Infragistics.Win.UltraWinGrid.UltraGridRow' exists in both 'c:\Program Files\Infragistics\NetAdvantage for .NET 2007 Volume 1 CLR 1.x\Windows Forms\Bin\Infragistics.Win.UltraWinGrid.v7.1.dll' and 'c:\WINNT\assembly\GAC_MSIL\Infragistics2.Win.UltraWinGrid.v8.1\8.1.20081.1000__7dd5c3163f2cd0cb\Infragistics2.Win.UltraWinGrid.v8.1.dll'
Thanks.
At first guess i would say that you've referenced both Infragistics.Win.UltraWinGrid.v7.1.dll and Infragistics2.Win.UltraWinGrid.v8.1.dll. CHeck your project's references. Also if Infragistics offer an upgrade your project type functionality when you install a new version, make sure it hasn't left stray references or using statements, or incorrect variable declarations that reference older versions of the componentry.
also, there is 10.3 out there now. best to upgrade to latest version. Also Infragistics has "Version Utility" which allows you to upgrade your solution and projects to newer binaries easily (will update project references for you). but yeah as Slugster mentioned, you have 2 diffirent versions of infragistics dll in your solution and there is class name clashes.