Hello,
I created a VS 2005 .NET CF application that uses some third party controls and additional assembly DLLs that I created, some are in the GAC and some are not. When I add a Smart Device CAB Project to my solution and add the primary output of the application project the list of referenced assemblies is properly included into the File System Editor in the CAB project. Then if I close and reopen the solution and look at the CAB projects File System Editor the referenced assemblies will be missing from the list of files to deploy. At this point I can not remove or re-add the primary output of the application project to the CAB project. I have to delete the entire CAB project and create a new one from scratch. If I view the deployment project *.vddproj file in a text editor I see that there are entries for the assemblies that are no longer shown in the File System Editor.
Any idea what could be going on or how to fix this
Thank you,
Jarod
Smart Device CAB Project will not rebuild after closing and reopening
ginnyK
Are you opening the entire solution or just the CAB project Since the CAB project should include the output of your primary project, the actual list of DLLs will appear once you build the entire solution.
Manav
CodeDjinn
but there is one new small problem, when I add the output of the EXE project to the CAB project the EXE and the proper referenced assemblies are added to the CAB project but the mscorlib.DLL and TLB files are also added to the CAB project and files to be deployed, it's very strange
I can just mark the mscorlib files as excluded and they are not bundled into the CAB file. At least I can now save and reopen CAB projects.
Martijn Mulder
I found a work around but would still like to know if anyone has any input or info on this.
In the vddproj file I located each line for the referenced DLLs that look like this
"SourcePath" = "8:MyCompany.Controls.dll"
and changed them to full paths like this
"SourcePath" = "8:C:\\MyProjects\\ControlLibrary\\build\\CF2\\Release\\MyCompany.Controls.dll"
once this was done for all assembly DLLs that are not part of the CF I was able to reopen and see all the assemblies in the File System Editor as well as recompile the CAB file.
Thanks
Jarod
AlexBB
I'm opening the entire solution
And even when I use the workaround I described in the second post the problem of the file paths being lost comes back when I save the CAB project. Saving the CAB project removes the path information from each of the DLLs.
Jarod
Abelard
Did you get this working yet If yes, than please post your workaround/answers for everyone's benefit.
Manav