Thanks for your answers. However, your answer to question 1 is quite vague. 
I'm looking for some very specific answers about the direction of MSIB. Plea
se answer the following for me:

1) Is it true that the Jupiter project is dead and there will not be a relea
se of a bundled product of CMS, CS and Biztalk.
2)Is there another release of CMS, non-service pack, non-upgrade planned for
 the future?
3)Will CS continue as a standalone server in future?
4)Can you provide any reasons to stay dedicated to the MSIB platform for eCo
mmerce web applications?

Thanks much,
Rey
3) Will CS "David Messner [MSFT]" wrote:

> 1)       The long range vision of Microsoft is to build tighter integratio
n
> across the Windows Server Sysetm products regardless of Microsoft
> orgnizational structure.  There is also a long range vision to provide
> customers a common portal architecture.  Therefore, we will indeed continu
e
> to focus on integration between the two products..  After the next version
> of CMS, CS will have better and better integration with it.
>
> 2)       We will continue to advance the integration with CS and VS.  As i
t
> is today CS is right inside the VS IDE for ease of development.
>
> 3)       As statecd above in answer (1) - the vision to have a common
> portal architecture and tighter integration across WSS products will also
> involve integration between CS and SharePoint in the future.  In Whidbey,
> all custom controls can be Web parts.  The scenario you describe (Commerce
> Server Cart Web part) is absolutely possible.
>
>  regards
> -djm
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> You assume all risk for your use. © 2004 Microsoft Corporation.  All righ
ts
> reserved.
>
> --------------------
> Thread-Topic: Commerce Server 2005 Integration with Sharepoint, Whidbey an
d
> MSIB
> thread-index: AcRe79PgF+NNzjyLSSWCu5DjTIOuEw==
> X-WBNR-Posting-Host: 209.77.1.214
> From: "examnotes" <Rey Zabala@discussions.microsoft.com
>
> Subject: Commerce Server 2005 Integration with Sharepoint, Whidbey and MSI
B
> Date: Wed, 30 Jun 2004 15:16:01 -0700
> Lines: 9
> Message-ID: <86D09471-165C-430B-B504-E24D421AAC21@microsoft.com>
> MIME-Version: 1.0
> Content-Type: text/plain;
> 	charset="Utf-8"
> Content-Transfer-Encoding: 7bit
> X-Newsreader: Microsoft CDO for Windows 2000
> Content-Class: urn:content-classes:message
> Importance: normal
> Priority: normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> Newsgroups: microsoft.public.commerceserver.general
> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 127.0.0.1
> Path:
> cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTFEED02.phx.gbl!TK2MSFTNGX
A0
> 1.phx.gbl!TK2MSFTNGXA03.phx.gbl
> Xref: cpmsftngxa06.phx.gbl microsoft.public.commerceserver.general:14174
> X-Tomcat-NG: microsoft.public.commerceserver.general
>
> Some questions for you:
>
> 1) It is my understanding that MSIB will continue to be supported, but is
> certainly not part of the long range vision within Microsoft. In other
> words, we should not expect a continued emphasis on integration between
> Commerce Server and CMS For instance, I am aware that CMS was moved into
> the Office Group because MS was receiving much more interest in integratio
n
> with SPS than with Commerce Server. Can you validate these claims?
>
> 2) Can you provide some insight into how Visual Studio 2005 and Commerce
> Server 2005 will play together?
>
> 3) Can you provide some insight into how Commerce Server and Sharepoint
> will integrate, if at all in the future. The reason I ask is that it is my
> current assumption that the "Web Part" concept will be exteneded to all of
> the enterprise servers that have a WinForm or WebForm facing UI. My curren
t
> client was hoping to build some reusable web parts that could be consumed
> by various applications. Hopefully, there would be the ability to create
> something like a "Cart" web part that could consume Commerce Server API's
> somehow. Hope this makes sense. Please be as wordy as possible as we are i
n
> the midst of some major technology decisions

[ Post a follow-up to this message ]