Can no longer add reference to CF 2.0 assembly in windows forms application

Can no longer add reference to CF 2.0 assembly in windows forms application

• andras99

  Thanks Manish,

  Is the only behavior to worry about design/compile time I was worried about any runtime issues using different mscorlib.dlls in the same project. I know the basics of how runtime assembly binding works I just wanted to make sure in this case.

  Regards,

  Dave

  
  
  

• Robert Gauvin

  Are these projects in VB .NET by any chance
  

• crjones99

  Daniel, you are right. This is due to a change brought about in VS2005 RTM. In VS2005 RTM, you cannot have a VB desktop project containing a P2P reference to a VB device project. This change was introduced as VB compile time architecture does not support this, and this lead to a few VB compiler crashes.

   

  Following scenario is  "Not Supported":

  1) Adding a reference to a VB Device Project in a VB Desktop project.

  < xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /> 

  For following scenarios you will get a prompt that "Adding a reference to a device project may produce unexpected results. Do you want to continue Yes/No". Clicking "Yes" will add a reference and clicking "No" will not:

  1) Adding a reference to a C# device project in a VB Desktop project.

  2) Adding a reference to C# or a VB device project in a C# Desktop project.

   

  Hope this answers your question.

   

  Regards,

    Manish

   

  
  

• jakistra

  I got the same issue.

  "Adding a reference to a device project may produce unexpected results. Do you want to continue "

  The problem is that my requirements are to hold CF projects that refer other CF assembly projects within a same solution that also contains winform and webform projects.

  Stil looking to resolve this issue.

  BTW when I click yes i run into compilation problems. Specified here: http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=205738&SiteID=1

  Using C# and VS 2005 on vista RC2.

  
  

• Mafti

  Hi Alex

  I actually tried this with a brand new solution, I created a new solution, added a smart device class library and smart device windows application project and a windows forms application project.  I added the class library reference to the smart device windows application without any problems but again I could not add the class library reference to the windows forms application.

  I take it that it is still possible to have .net CF 2.0 assembly references in a full framework application, and this is not something Microsoft have just changed in the final release, if so then it might be time a full reinstall of visual studio 2005.

  Many thanks

  Dan

  
  

• D.Ware

  This kind of issues is best resolved by creating a new project and re-adding the source files to it.
  
  

• JiriS

  We are having this problem. It is with a Solution that has both VB.NET CF assemblies and VB.NET (full framework) assemblies accessing the CF assemblies.

  The closest thing to a work-around that we have found that works somewhat nicely with a team and source control is to do the following:

  1. On all development environments, create a batch file to run the following command on startup (where each dev gets to specify the path):

     Code Snippet

     SUBST Q: "C:\MyPath"

  2. Go to the Compile settings on all CF assemblies (double-click "My Project" and go to the Compile tab) and set the Bin Output Folder option to "Q:\"
  3. Compile all CF assemblies so their DLLs exist in your Q drive.
  4. Now when adding references to the CF assemlbies, you CANNOT go to Add Reference -> Project -> [Project Name] as was previously posted here. However, nothing is to stop you from adding a reference to a DLL. So browse for your DLLs on your Q drive when you add your references.
  5. Lastly, VS doesn't realize the dependencies correctly when you do this so right-click on your solution and go to Project Dependencies and set it up correctly.
  6. Voila! You're done! This MOSTLY works with some annoying but not show-stopping side-effects.

  So now that this work-around has been stated, I am having one annoying side-effect that I'd like help with resolving. My solution has about 8 or so projects in it where 4 of them are CF assemblies and when I go to run my app, if I simply hit F5 to debug, it goes and compiles everything but at compile time, there are conficts when accessing the DLLs on my Q drive. HOWEVER, if I simply rebuild my solution, everything compiles fine and then I can hit F5 to debug.

  So my question is, is there any way to force a small time delay in between compiling various assemblies

  Thanks!

  -Shane

  
  

• Edgar.Marques

  Brilliant

  Thanks Manish, I was starting to tear my hair out wondering what the hell could be wrong.  Is there a recomended approach to the cross platform issue

  Many thanks

  Dan

  
  

• BStarDev

  Yes they are.
  
• Can no longer add reference to CF 2.0 assembly in windows forms application