Today I came across another of those mistakes that specializes in both M $. The error in question appeared when compiling the project, then include a reference to class to classes contained in System.Data.SqlClient :
genasm.exe (1): There Was An Error initializing error Tracker. Helpers.CFSqlSP. Could not load file or assembly 'System, Version = 2.0.0.0, Culture = neutral, PublicKeyToken = 969db8053d3322ac, Retargetable = Yes' or one of STIs dependencies. The system can not find the file specified.
After much research and testing, including a reconstruction project in VS, I found the error was caused by the presence of DesignTimeAttributes.xmta file, which contains custom attributes used by the design editor VS. In my case, this file contained DesktopCompatible property (true) for multiple user controls in use within the project.
An exhaustive search on Google yielded a number of possible solutions, at least I do not worked:
- XMTA Exclude the project file: this effectively eliminated the error when compiling, but prevented loading the designer in any form containing user controls inherited.
- manually Include reference to the DLLs listed in error, within the project file.
the end, and only after much searching, I found a post one called Joaquin Raya, which offered the best explanation I found on the root of the problem. Joaquin explains in his post, the problem is caused by a bug in VS 2008 which, when used XTMA file within a project, cause confusion in the search paths for DLLs, causing VS try to locate specific DLLs. NET CF within files. NET Framework.
His solution was simple: place the DLLs listed in error and install in the GAC. In my case, I did as follows:
- opened a window Explorer in the folder C: \\ Program Files \\ Microsoft.NET \\ SDK \\ CompactFramework \\ v2.0 \\ WindowsCE
- I opened another Explorer window folder C: \\ Windows \\ assembly
- Select files and System.dll System.Data.dll WindowsCE folder and drag the folder assembly .
Note that even though my project was based on. NET CF 3.5, the error made reference to System.dll file version 2.0.0.0 . You have to look good in this to know which version of the DLL should be copied into the GAC.
And you know the saddest of the whole case? that this error has already been reported in VS 2005 and corrected in SP1 .... only to reappear alive and well in VS 2008 .... must see!
Thanks M $, for more than two hours unproductive and stressful
