I am putting together some nant build scripts to enable rapid deployment. As well as setting up a version control environment, the tool is Merant version manager or PVCS, but this should not really matter.
I want to avoid having binary files checked into source control, thus local .net project bin folders and dlls are not being checked in. I would instead like shared assemblies to exist on a special folder. All projects will reference dlls from this special shared folder and there will be no project references. This will allow the nAnt build scripts to place generated dlls here and other build should be able to pick them up, as well as dependencies assigned using CruiseControl.Net can monitor changes and rebuild as necessary. I did have this special assembly folder on a shared network drive but I keep getting access errors. I moved this to a local folder and get the same thing but it disappear after a refresh. Is this something to do with code access security, this doesn't occur when the dll is in the projects local bin folder. The error looks something like this. Access is denied: 'MyAssembly'. Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind). -- View this message in context: http://www.nabble.com/version-build-deploy-environment-tf1868370.html#a5105700 Sent from the NAnt - Users forum at Nabble.com. Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ NAnt-users mailing list NAnt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
