VS.NET 2003 does not deploy assemblies which are not referred to

[Guest]

I am developing a .NET Compact application for smartphone device.
In my solution, there is a couple of assemblies (projects) which are not
referred to by main project either directly or indirectly at design time.
They are loaded through reflection instead.
When I select "Deploy Solution" form the "Build" menu, these assemblies are
not deployed to the device since VS.NET thinks that they are not needed.
How do I override this "smart" behavior of VS.NET and force it to deploy all
assemblies in my solution?
In Configuration Manager, all "Deploy" check boxes are checked, but it
doesn't help.

 

[Guest]

When you use the IDE to deploy a project, it will only do what you are
experiencing. If you want a specific dll to be included in the deployment,
it needs to be a part of the project somehow. The easiest way for you to
accomplish this is to include the dll that you need as a content source. So,
build the dll, then copy it to the deployment project, and set it's type to
content.

It will then be deployed with the project.

This is the same way that deploying web applications work, if the dll isn't
in the GAC or a content source, then it will NOT be deployed with the web
site.

 

[Alex Feinman [MVP]]

If these assemblies are built dynamically, ensure that their project
properties point tothe same deployment directory as the main project. An
alternative would be to make their build directory the same as main project
source directory, and include them in build as "content"

 

[Guest]

Looks like I've found a better solution: to set "Deployment Device" property
of those "unreferenced" projects to some concrete value instead of "Same as
device of consuming project".
After doing that, they are deployed just fine.