Hi,
When I open the samples in VS2010, the project update wizard coverts them, all appears to well no errors, however I am unable to compile the samples. I am getting either depending on if I choose to update the Silverlight framework or not.
Custom tool error: Failed to generate file: Could not resolve mscorlib for target framework 'Silverlight,Version=v4.0'. This can happen if the target framework is not installed or if the framework moniker is incorrectly formatted. C:\Users\Public\Documents\Infragistics\NetAdvantage 2010.1\Silverlight\Samples\SamplesBrowser\SamplesBrowser.Samples.LOB\Service References\FileDownloadServiceReference\Reference.svcmap 1 1 SamplesBrowser.Samples.LOB
or
Custom tool error: Failed to generate file: Could not resolve mscorlib for target framework 'Silverlight,Version=v3.0'. This can happen if the target framework is not installed or if the framework moniker is incorrectly formatted. C:\Users\Public\Documents\Infragistics\NetAdvantage 2010.1\Silverlight\Samples\SamplesBrowser\SamplesBrowser.Samples.LOB\Service References\FileDownloadServiceReference\Reference.svcmap 1 1 SamplesBrowser.Samples.LOB
I am also using Windows 7 64bit, I was wondering if this may have an effect?
Any suggestions on to fix this?
Cheers
Phil
Hi Phil,
Sorry for the late reply.Did you resolve your problem?If no, could you tell me what version of Silverlight you have installed?
Thanks,George
Hi George
Looks like I am having a similar problem. I got the samples from NetAdvantage_SilverlightDVWithSamplesAndHelp_20102.exe and the project SamplesBrowser.Samples.DV is not compiling in VS2010. I have Silverlight 4 installed. Please help.
When I build the complete project I am nor getting any error but the output shows like this -
========== Build: 4 succeeded or up-to-date, 1 failed, 0 skipped ==========
Hello mparash,
I have seen this error and I think it is due to the path length. I have 2 suggestions.
1. Have you tried to run the samples anyway? It says that the build failed, but the .xbap should have been created successfully. You can either check the bin folder or the output log.
2. Try to copy or move the samples to a folder like C:\Samples. This might solve the path length problem, which would solve the build failure.
Elizabeth Albert
Localization Engineer