From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 2002:a24:4145:: with SMTP id
 x66mr14604266ita.130.1557045604556;
        Sun, 05 May 2019 01:40:04 -0700 (PDT)
X-Received: by 2002:aca:e814:: with SMTP id f20mr4776187oih.83.1557045604363;
 Sun, 05 May 2019 01:40:04 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!136no428290itk.0!news-out.google.com!v189ni549itv.0!nntp.google.com!b2no428464itd.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Sun, 5 May 2019 01:40:03 -0700 (PDT)
In-Reply-To: <74dd6ea5-afb4-4d7e-b218-d01e67576287@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=101.164.108.182;
 posting-account=wavAeAoAAAAZF_sXSZepBukuPCBO0Zqt
NNTP-Posting-Host: 101.164.108.182
References: <13ce24c7-2cfd-4c77-8e4f-2aba216d9ca9@googlegroups.com>
 <12955098-0ae7-4e2e-b4dd-050620a1f039@googlegroups.com>
 <22ad2bb3-4d6e-48f0-9f72-ea2464390b13@googlegroups.com>
 <3d9b62c5-6461-420a-b051-132618c40369@googlegroups.com>
 <d47c40bf-aa85-48db-a53a-7ce8b6e368f4@googlegroups.com>
 <def045b0-1eab-45b2-b055-c7796f80cd67@googlegroups.com>
 <67e68b33-4fa1-45fc-aac5-3294258bb4da@googlegroups.com>
 <df352ec8-67af-4bae-a041-27e904d42f13@googlegroups.com>
 <b0cbcb52-d3fe-4fb6-85bf-cf6fb56b04f3@googlegroups.com>
 <30e9156c-193e-459d-987c-06182f78ae89@googlegroups.com>
 <f14259b2-6d2f-47e4-90fd-78e770cf2d2c@googlegroups.com>
 <8c5d8c9a-d594-4bb2-b5d7-6235c112a39d@googlegroups.com>
 <fa10bea9-034b-4fd7-9767-14e4ec8bd983@googlegroups.com>
 <ae903ebd-1369-4efa-afdd-6c2e2b1ed0f1@googlegroups.com>
 <992a0187-0acf-4807-9ee6-01456b85272c@googlegroups.com>
 <fe8f41dc-518b-45bb-9090-98e035b05c33@googlegroups.com>
 <fd489a42-6029-435f-b419-aca348a2cb3c@googlegroups.com>
 <3410e6b2-5695-4adf-b88d-b49e097a2cc7@googlegroups.com>
 <641f3f3b-9fe1-422f-8191-e234c94dc233@googlegroups.com>
 <7f439332-233b-4ce1-a798-3768c5a81157@googlegroups.com>
 <74dd6ea5-afb4-4d7e-b218-d01e67576287@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <7743c080-751b-40f6-a1e5-3e2a141e671b@googlegroups.com>
Subject: Re: ANN: VisualAda (Ada Integration for Visual Studio 2017 & 2019)
 release 1.1.12
From: alby.gamper@gmail.com
Injection-Date: Sun, 05 May 2019 08:40:04 +0000
Content-Type: text/plain; charset="UTF-8"
Xref: reader01.eternal-september.org comp.lang.ada:56240
Date: 2019-05-05T01:40:03-07:00
List-Id: <comp.lang.ada>

On Saturday, May 4, 2019 at 11:31:36 PM UTC+10, Greg wrote:
> Absolutely, my pleasure. Yes, all three of my machines are various versions of 2017 and in the last few weeks, 2019. Looking forward to it!
> 
> Thanks,
> Greg

Hi Greg

I have just released VisualAda version 1.2, which should fix the issue reported
earlier. Let me know if their are still issues with this

Alex