TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
David Botton <[log in to unmask]>
Reply To:
Date:
Fri, 14 Jul 2000 14:28:58 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
VS.Net is a tool (Visual Studio 7). They may throw in
their up and coming COM library under the VS.Net name,
but that will be seen.

Ada using GNATCOM can make use of the COM library with
no problem.

The issue here was to integrate Ada awareness, tools,
etc. in to Visual Studio 7 (aka VS.Net). MS has a COM
based API for doing this, but it is not released
except to Visual Studio.Net partners that pay big
bucks. A subset is according to them going to be
released with the product to allow some integration
from non "partners".

I have not seen anything that would indicate that MS's
COM library if and when it will be released will
infact offer any more then there current objects offer
(XML, ADO, CDO - Active Messaging, etc.)

For example, COM+ just means COM/DCOM + MSMQ + MTS.

David Botton

--- Tom Moran <[log in to unmask]> wrote:
>   Is VS.Net a non-upwardly compatible replacement
> for Windows OSes?
> Why does a compiler have to be modified to work with
> it?  What does
> it mean that VS.Net "supports a language" - someone
> offers a compiler
> for that language that works on that OS?

__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail  Free email you can access from anywhere!
http://mail.yahoo.com/

ATOM RSS1 RSS2