I recently installed NetAdvantage_Silverlight5_20112.2031_SR.exe and now my project won't compile.
I created a very simple silverlight 5 app that only references these DLLs, and it fails to compile.
InfragisticsSL5.Controls.Maps.XamMap.v11.2.dllInfragisticsSL5.DataVisualization.v11.2.dllInfragisticsSL5.v11.2.dll
Seems like either XamMap didn't get updated with SR2031 on my machine, or at all in SR2031.
Hello,
Thank you for your post. I have been investigating the behavior that you have described and after installing the 2031 service release the assembly for the XmMap control is also updated. I have created a sample application that contains a XamMap control and uses the 2031 service release and the InfragisticsSL5.Controls.Maps.XamMap.v11.2.dll is the same version as the other assemblies in the application (build 11.2.20112.2031). I am attaching the sample application and a video of creating it:
This type of issues might be caused if the InfragisticsSL5.Controls.Maps.XamMap.v11.2.dll assembly is not referenced form the Global Assembly Cache and when the service release is installed the reference to that assembly does not point to the assembly with the new version. I can suggest following the steps below:
1. Delete bin and obj folder from your project
2. Remove the assemblies form the References and then add them again (from the Global Assembly Cache).
3. Set the Specific Version property of all the assemblies that you are using to False.
4. Clean and Rebuild your project.
Please let me know if after following these steps the issues still appears in you project.
Looking forward to hearing from you.
Sincerely,
Krasimir
Developer Support Engineer
Infragistics
www.infragistics.com/support
Krasimir -
Do you have any other ideas I can try to get the MSP for the Silverligh5 DV controls to get applied correctly?
Also, I've opened a support case for this CAS-90432-H9JJF1
thanks
Hi Jeremy,
I've passed this information along to our product team and let them know this would be beneficial for both us and the community to have.
per the support issue - my problem was resolves.
seems I had some installers with same filenames that were out of date.
downloading the newest installers fixed the issue.
hopefuly infragistics can start distributing MD5 hashes with their downloads... since they don't seem to rename installer files when they version them.
I've posted an update to the support case. We'll handle this issue from there.