Sam Gardiner wrote:
Why are you dealing with this at build time instead of test time? If I understand the problem, you want the plugin to work with any deployed framework (and I assume you mean something other than the .Net framework version). In that case, building against a specific set of binaries just tells you that they can be built for any framework. It doesn't tell you that once you have a build against one set of binaries, it can be deployed against a different framework in the field.
I'm trying to use the <solution> task to build a group of projects not
collected into any solution. the problem is that these projects have
project references and binary references but I'd like to compile them
against a known set of binaries, not what would be obtained by building
the projects. The reason is that I wish developers to create plugins
that use a framework and be able to deploy the plugins without
redeploying the framework. So the newly created plugins must be
compatible with the framework that is already deployed.
My reading of the documentation for the solution task says that NAnt is working as advertised. It says that it automatically converts file references into project references. I think you might be able to work around this by changing things so that the prebuilt binaries are in the same output directory as the ones you're building. Alternatively, I wonder what would happen if you left out the <referenceprojects> part entirely. I don't see why NAnt would need them in this case, for the same reason it wouldn't need them if you had some random third party .dll without a project at all.Here is my Nant call to <solution>:
<solution configuration="${Settings.Build.Configuration}" outputdir="${Directory.Build.Projects.Plugins}\bin" >
<projects>
<include
name="${Directory.Build.Projects.Plugins}\**\.*.vbproj" />
</projects>
<referenceprojects>
<include name="${Directory.Build.Common}\**\*.vbproj" />
<exclude
name="${Directory.Build.Projects.Plugins}\*.vbproj" />
</referenceprojects>
<assemblyfolders>
<include name="${Directory.Build.Bin}\*.dll" />
<include
name="${Directory.Build.Projects.Plugins}\bin\*.dll" /> </assemblyfolders>
</solution>
.
.
I haven't tried either of these suggestions, but they're simple enough for you to experiment with them.
Gary
------------------------------------------------------- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 _______________________________________________ Nant-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nant-users
