|
Home > Archive > BizTalk Server > May 2004 > Automatting BizTalk Server Project Builds
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Automatting BizTalk Server Project Builds
|
|
| Mike Doerfler 2004-05-06, 12:39 pm |
| I was wondering if anyone knows how to build a BizTalk Server 2004 Project
in an automatted fashion. With my Web Projects and Class Libraries I use
NAnt to do the builds so all I need is the .NET Framework SDK on the build
server. From what I can tell with BTS Projects you have to use Visual
Studio .NET to build them. If there are some command line tools (besides
devenv.exe) that could be integrated with NAnt to build this type of VS.NET
project could you provide a link. I have seached google but did not find
anything 
Thanks in advance for any help or links!
Mike
| |
| Gilles [MSFT] 2004-05-14, 12:55 pm |
| Hello Mike,
>I was wondering if anyone knows how to build a BizTalk Server 2004 Project
>in an automatted fashion. With my Web Projects and Class Libraries I use
>NAnt to do the builds so all I need is the .NET Framework SDK on the build
>server. From what I can tell with BTS Projects you have to use Visual
>Studio .NET to build them. If there are some command line tools (besides
>devenv.exe) that could be integrated with NAnt to build this type of VS.NET
>project could you provide a link. I have seached google but did not find
>anything
Currently, the only supported way to build BizTalk 2004 projects is to use devenv's command line build capabilities.
Thanks.
-Gilles.
| |
| Steef D. 2004-05-30, 10:46 am |
| When you install BizTalk, a so-called 'package' for Visual Studio.Net
is installed. This is a piece of software developed with the Visual
Studio .NET Integration Program (VSIP) 7.1. A package enables you to
create your own type of projects and compile them. When you add a
BizTalk project, compilation is a two step process :
1. Generation of a set of files in your temporary directory
2. Compilation of these files into an assembly.
The generation is invoking a COM-component, which in the case of
BizTalk is an
inprocess-server. That's the reason why you need devenv to build
BizTalk.
Remarkably enhough, when you compile a C#-application, you don not
need the csc.exe compiler. You can rename it and you can still compile
C#-applications, Microsoft actually made 2 C#-compilers, one for
integration with Visual Studio and one for command-line builds.
Theoretically, compiling a C#-application from within Visual Studio
and with csc.exe could produce different output, Microsoft needs tobe
sure these two are kept in sinc.
BTW, you can see what gets compiled with Charles Young's BTSFileDump
utility:
http://www.gotdotnet.com/Community/...62-0825daf15ab0
|
|
|
|
|