|
Home > Archive > BizTalk Server Setup > January 2005 > BizTalk 2004 Setup Hell?
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 |
BizTalk 2004 Setup Hell?
|
|
| posmasternet 2004-12-02, 5:42 am |
| I have donwloaded the BizTalk 2004 trial from the Microsoft website, and have installed it on our SQL Server, ready to manage the relationships, and data between our CRM (MS SQL Server) and our website db (MySQL).
However, when I previously saw the application running at a possible supplier, they used the Visual linking or orchastration as I think it is correctly named.
The documentation with the software seems to be really poor, and from what I can understand I need Visual Studio .NET
Can anyone give me some guidence on how to do this?
Is there any Value in getting an older version of BizTalk as I have been lead to belive the tools are in those version...
Regards
Dave | |
| Niklas E 2004-12-02, 5:48 pm |
| You need VS.Net 2003 to be able to develop (orchestrations etc). You can
deploy already developed BizTalk assemblies on a server without VS.Net 2003
installed.
Martijnh has a good tool, BizTalk Explorer, which is like Microsoft's
BizTalk Explorer and more, but you don't need Visual Studio installed. This
is a good tool to use on servers which are not on the same domain where you
don't want or need Visual Studio.
http://martijnh.blogspot.com/
BTW:
You need only Visual C#.Net 2003 if you don't have the full Visual Studio
2003.
Best regards
Niklas Engfelt
"posmasternet" <posmasternet.1gn391@mail.webservertalk.com> wrote in message
news:posmasternet.1gn391@mail.webservertalk.com...
>
> I have donwloaded the BizTalk 2004 trial from the Microsoft website, and
> have installed it on our SQL Server, ready to manage the relationships,
> and data between our CRM (MS SQL Server) and our website db (MySQL).
>
> However, when I previously saw the application running at a possible
> supplier, they used the Visual linking or orchastration as I think it
> is correctly named.
>
> The documentation with the software seems to be really poor, and from
> what I can understand I need Visual Studio .NET
>
> Can anyone give me some guidence on how to do this?
>
> Is there any Value in getting an older version of BizTalk as I have
> been lead to belive the tools are in those version...
>
> Regards
>
> Dave
>
>
>
> --
> posmasternet
> ------------------------------------------------------------------------
> Posted via http://www.webservertalk.com
> ------------------------------------------------------------------------
> View this thread: http://www.webservertalk.com/message579435.html
>
| |
| Josh King 2004-12-02, 5:48 pm |
| posmasternet <posmasternet.1gn391@mail.webservertalk.com> wrote in message news:<posmasternet.1gn391@mail.webservertalk.com>...
> I have donwloaded the BizTalk 2004 trial from the Microsoft website, and
> have installed it on our SQL Server, ready to manage the relationships,
> and data between our CRM (MS SQL Server) and our website db (MySQL).
>
> However, when I previously saw the application running at a possible
> supplier, they used the Visual linking or orchastration as I think it
> is correctly named.
>
> The documentation with the software seems to be really poor, and from
> what I can understand I need Visual Studio .NET
>
> Can anyone give me some guidence on how to do this?
>
> Is there any Value in getting an older version of BizTalk as I have
> been lead to belive the tools are in those version...
>
> Regards
>
> Dave
Welcome to BizTalk Setup Hell. It's nice and warm here and there are many of us.
| |
| Goutham[MSFT] 2005-01-17, 5:53 pm |
| Dave,
As Niklas pointed out, you need Visual Studio .Net 2003 (C# should be
sufficient) to develop BizTalk applications. The original documentation
which shipped with the product was not up to par, so there is an updated
version of the docs on the web, you can download it from
http://www.microsoft.com/downloads/...7461-f4e2-4bc6-
b5c2-2018aff2823d&DisplayLang=en
regards
-g
|
|
|
|
|