Deploy a project without references

[Fredy Muñoz [MCSD]]

Hi there. I have the following scenario. I'm developing a Windows Mobile
Application (one solution with one executable and three class libraries) and
at the same time my partner is developing a set of libraries (a separate
solution with three class libraries) to extend the functionality of the same
application.

My partner needs to reference one of the class libraries that I'm working on
in every class library he is developing (becouse it contains interfaces and
base classes to inherit from) so he downloaded my solution from our source
control system and build the entire solution. After that, he referenced the
class library from his solution.

Right now we are in the testing phase and have two users testing the
application. We make the changes and fixes to both solutions during the day
and at the end we update the PDAs to continue the testing the next day. First
I deploy my solution and then I pass the PDA to my partner so he deploys his
solution too (of course there are better ways but since there are only two
PDAs that's our process for the moment). When I deploy my solution to the
PDAs from Visual Studio 2005 everything works fine, but after my partner
deploys his solution the PDA ends up with and older version of the 'shared'
library and the application crashes.

We noticed that when my partner deploys his solution Visual Studio deploys
his version of the 'shared' library. Here are two things:

1. I would expect that if Visual Studio deploys the referenced libraries
(which is a good thing) at least it should check the dates and since the
'shared' library deployed by me is newer than the one in my partners PC then
Visual Studio shouldn't deploy it. Am I right?

2. Of course that the problem is solved if my partner deploys his solution
first and then I do, but what if only his solution has changed? Is there an
option to avoid the deployment of the references? (We tried "Copy Local =
False" but didn't work).

 

[Paul G. Tobey [eMVP]]

You could set up his project so that Deploy is not enabled for your class
libraries in his project. In VS2008, I have a project that uses a
"personality module" that handles special functions differently on some
devices. I can enable deployment of that or disable it via Properties of
the workspace (right-click on the workspace name in the Solution Explorer
window). Choose Configuration Properties | Configuration and you can select
which things to Deploy. It looks to me like VS2005 has the same thing...

Paul T.

 

[Fredy Muñoz [MCSD]]

Thanks for your answer Paul, but what is the equivalent of a workspace in
VS2005? I can't find the options you mention.
--
Fredy Muñoz
MCSD .NET Developer

You could set up his project so that Deploy is not enabled for your class
libraries in his project. In VS2008, I have a project that uses a
"personality module" that handles special functions differently on some
devices. I can enable deployment of that or disable it via Properties of
the workspace (right-click on the workspace name in the Solution Explorer
window). Choose Configuration Properties | Configuration and you can select
which things to Deploy. It looks to me like VS2005 has the same thing...

Paul T.

 

[Chris Tacke, eMVP]

The fastest way there is to pull down the Debug/Release dropdown and select
"Configuration Manager"


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com

Thanks for your answer Paul, but what is the equivalent of a workspace in
VS2005? I can't find the options you mention.

 

[Fredy Muñoz [MCSD]]

Ok, I see it, but it only lists the projects in the solution. I'm referencing
an assembly which is not part of my solution.