First off, the ReSharper 4.0 builds are much improved over 3.1 when it comes to mixed targets. We have a pretty big solution (over 50 projects) with a mixture of C, C++, and C# projects. The C# projects are about half for the full framework and half for compact framework. In 3.1 almost all (no exaggeration) of the code in the compact framework projects were marked as errors. Fortunately you guys have fixed this in 4.0 (mostly). However, I'm still having a few issues:
1. When I controlclick classes that are in an external assembly, the object browser sometimes points to the library for the incorrect framework. This is pretty easily reproducible: Create a new solution for smart devices for Windows CE 5. Then add a new project to this solution that is a standard Windows (full framework) project. Now controlclick in the auto-generated code (say, the Application.Run() call) in both of the project's Program.cs and observe which library is opened in the object browser. For me, the full framework project opens the System.Windows.Forms element in the tree.
2. I still get some erroneous errors marked by ReSharper when viewing some code in my compact framework projects. Unfortunately, I can't figure out how to produce a reduced test case as the errors are occurring in a rather larger source code file (10000+ lines of code). All of the errors occur on calls on objects that exist in a referenced library. The source file exists in the compact framework project and is added as a link to another project that targets the full framework. The full framework project references the full framework version of the library and it has no errors. Both projects build and run with problems. Unfortunately, creating a new solution with a similar setup referencing the same library doesn't show the errors, so there is something funky going on. The ReSharper errors that I get are along the lines of "Argument type 'bool' is not assignable to parameter type 'bool'". At first I thought I may not have built the libraries properly for compact framework, but this problem doesn't show up in a small project. Is there a way I can turn on some type of debug logging for ReSharper to help you guys solve this issue?
3. Lastly, I get errors similar to those in #2 when I try to make calls into a COM wrapper class that was generated by Visual Studio. I think it may have been compiled incorrectly, so I may need to play with that, but the application itself compiles and runs without a problem. See the attached screenshot for the error. These errors do show up in a smaller solution when referencing the same libraries, so maybe there is something wrong with the libraries themselves?
I am currently running build 804, but I think these issues have been mostly present throughout the 4.0 EAP.
Thanks for any help you may have. Let me know if there is anything I can do to help you guys fix these problems.