Re: Creating Build Script for Scott Colestock NAnt Deployment Wiza
Web Server forum
Back To The Forum Home!Search!Private Messaging System

Web Server Talk Web Server Talk > Web Servers reviews > BizTalk Server > BizTalk Server General > Re: Creating Build Script for Scott Colestock NAnt Deployment Wiza




  Last Thread   Next Thread Next
  Show Printable Version Email this Page Subscribe to this Thread      Post New Thread    Post A Reply      

    Re: Creating Build Script for Scott Colestock NAnt Deployment Wiza  
Craig Butler


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
09-02-04 11:20 PM

All,

I think I have my build file set up, but I am not getting a gacit error

gacit:

[exec] C:\Program Files\Microsoft Visual Studio .NET
2003\SDK\v1.1\\bin\gacutil.exe /u

Microsoft (R) .NET Global Assembly Cache Utility.  Version
1.1.4322.573
Copyright (C) Microsoft Corporation 1998-2002. All rights
reserved.

Option /u takes 1 argument

BUILD FAILED

C:\BizTalkLabs\EAISolution\EAISolution.sln.build(180,5):
External Program Failed: C:\Program Files\Microsoft Visual Studio .NET
2003\SDK\v1.1\\bin\gacutil.exe (return code was 1)

Total time: 15.7 seconds.

I am clueless as to know what this message means.  Can anyone out there help
me out??

Thanks!


"Asbjørn Rygg" wrote:

> Hi Craig,
>
> You should only need to alter the project names for your orchestrations
> and schemas as well as the orchestration names under
> "unenlist.orchestration" to create your own deployment file. If your
> project don`t include custom pipelines or .NET components just place a
> comment around or remove those sections.. (remember the original file as
> a reference)
>
> I don`t know if this helps you, but Peter Provost has created a modified
> version of Scott Colestocks NAnt build file for BizTalk. The idea is
> that you set up a property file instead of editing inside the build file
> it self. (Note: I haven`t tested this yet..) His blog posting is here:
> http://www.peterprovost.org/archive...08/18/1802.aspx
>
> For both cases you will need to manually deploy your orchestration to
> "bootstrap" your orchestration binding file (using Deployment wizard or
> btsdeploy.exe). The sample ships with that binding file already present.
> That confused me a bit when I first tried it..
>
> The reason for choosing debug instead of development as output folders
> is to support any custom .NET components you might have in your project
> as these will already have a debug folder by default - the point is to
> have the same output folder for all your projects, being a BTS
> orchestration or a .NET component. If you only have an orchestration and
> a schema project, you can assign development instead of debug to the
> ${Configuration} variable..
>
> HTH,
> - Asbjørn
>
> Craig Butler wrote: 
>





[ Post a follow-up to this message ]



    Sponsored Links  




 





   All times are GMT. The time now is 09:56 AM.      Post New Thread    Post A Reply      
  Last Thread   Next Thread Next


Most Popular forums 

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 
Medical and Health forum | Computer Games Reviews | Graphics design forum

Back To The Top
Home | Usercp | Faq | Register