On 10/18/05, Anderson, Kelly <[EMAIL PROTECTED]> wrote:
> If you just expect the tools to be installed, then you have a job
> setting up a new machine, virtual machine or whatever. If you do this
> often, it might be worth automating, and it might be as easy to write a
> NAnt script to do this as t
Unfortunately you have to call out to DevEnv to build you Biztalk solutions.
There is no current support for Biztalk Project files. A good site and also
a good framework can be found at
http://www.traceofthought.net/CategoryView,category,Deployment%20Framework.a
spx
-Original Message-
Fro
Sorry - I left the wrong subject
***
Has anyone created an automated build that compiles BizTalk dlls. I have
scripted something for MS Commerces server using Nants Solution Task to
build a .csproj file.
Similarly I would like to know if there is a way to build
Has anyone created an automated build that compiles BizTalk dlls. I have
scripted something for MS Commerces server using Nants Solution Task to
build a .csproj file.
Similarly I would like to know if there is a way to build a .btproj
file.
I run into the following error:
Unknown pro
> I have to admit a real lack of knowledge on Cruise Control (is there a
> CC list?)
Yes, at https://lists.sourceforge.net/lists/listinfo/ccnet-user.
> Do you install from a network share? If you have the tools in
> a revision control system, then you need revision control installed to
> get goin
I have to admit a real lack of knowledge on Cruise Control (is there a
CC list?) Do you install from a network share? If you have the tools in
a revision control system, then you need revision control installed to
get going, or does CC have mechanisms for setting up revision control
programs?
I'm
The middle way works well on one of our servers.
We didn't want to build on every change, so we set up a separate cruise
project that monitors the build tools separately from the code builds.
It's scheduled to run at the end of the day, and it installs all updated
tools when it spots a change.
I think it may come as a surprise how many occasions you might make use of a
separate script that setup the build environment:
- re-creating an old build
- setting up a new machine
- disaster recovery tests and (heaven forbid) the real deal - an actual disaster
- the next team in the organisation
