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 autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a24:7dd2:: with SMTP id b201mr8645658itc.93.1557499235498; Fri, 10 May 2019 07:40:35 -0700 (PDT) X-Received: by 2002:a54:4f15:: with SMTP id e21mr5326185oiy.122.1557499235234; Fri, 10 May 2019 07:40:35 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.166.215.MISMATCH!b2no168139itd.0!news-out.google.com!v82ni163ita.0!nntp.google.com!b2no168137itd.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 10 May 2019 07:40:34 -0700 (PDT) In-Reply-To: <0ae11fcc-f151-41fb-a578-af5cd53e371c@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=97.99.196.17; posting-account=zwxLlwoAAAChLBU7oraRzNDnqQYkYbpo NNTP-Posting-Host: 97.99.196.17 References: <50adfe1e-7bee-4048-8523-1b41bd0c9fe3@googlegroups.com> <2569c28e-ccde-4f39-87c9-8799973ecdba@googlegroups.com> <302b73dc-7b45-4b40-9fc8-328498bc264b@googlegroups.com> <42d78678-874f-478c-a627-78219830acfe@googlegroups.com> <0ae11fcc-f151-41fb-a578-af5cd53e371c@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <3bb6aa53-af56-41d5-a53b-30a47009cbb6@googlegroups.com> Subject: Re: ANN: VisualAda (Ada Integration for Visual Studio 2017 & 2019) release 1.2.0 From: Optikos Injection-Date: Fri, 10 May 2019 14:40:35 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader01.eternal-september.org comp.lang.ada:56278 Date: 2019-05-10T07:40:34-07:00 List-Id: On Friday, May 10, 2019 at 7:08:30 AM UTC-5, alby....@gmail.com wrote: > On Thursday, May 9, 2019 at 7:20:14 AM UTC+10, Greg wrote: > > Alex, sorry, been hammered with deadlines and too tired at night to eve= n look at a screen. > >=20 > > 1) and 2) would go a long way to helping others starting down this path= , and that's the point, at least from my perspective. Everyone talks about = promoting the language, and to me, this is one of the more outstanding ways= I've seen. > >=20 > > 3) I can't believe you can't set dependencies as you say, but who knows= , you might be right. If not, a mention in the README should certainly be s= ufficient. > >=20 > > 4) Figured something like that. > >=20 > > 5) I did monkey around with changing the target runtimes myself to more= recent ones, but didn't seem to make much difference, but defaulting to mo= re recent ones is definitely the way to go. > >=20 > > I guess just emphasizing that you HAVE to build THIS and THIS first (th= e WinRT stuff) before using Visual Ada, you know, step A, B, and C - as you= said, would help a lot.=20 > >=20 > > I suppose I could start doing PRs for documentation suggestions or othe= r issues of course, on the WinRT stuff. When/if VisualAda goes to GitHub, s= ame thing. > >=20 > > I'm just having fun doing this, and hey, anything I can do to help. I h= ave absolutely no need for GtkAda, and doing a Windows app in Ada is still = to me mind-blowing. > >=20 > > I did try to build a UWP DLL the other day and ran into an error, can't= remember what it was exactly, but when I get a chance, I'll pass along the= details. > >=20 > > I strongly suspect deploying a VisualAda UWP app to Xbox WILL work, jus= t haven't had the chance to set it up yet. But will soon. > >=20 > > Again, thanks for all of this incredible work, > > Greg >=20 > Hi Greg >=20 > I apologise, I actually missed this post (and replied to you later post w= ithout > seeing this one). So in response to your points, which are very much appr= eciated >=20 > 1) and 2) I have already posted some changes to the GitHub readme's for b= oth > winrt_runtime and winrt project to reflect the dependencies and additiona= l info. > PR's are very welcome for the documentation, But bear in mind that the wi= nrt > source code is generated of the back of the winmd metadata, so changes to= the > bindings need to be generic!. I am happy to accept PR's for winrt_runtime= . >=20 > BTW, Thanks for your comment's regarding my work, I in part embarked on t= his > journey. because I saw a need to promote Ada outside of its traditional u= se > case in the safety critical/embedded/Realtime markets and I always consid= ered > Ada as a general purpose language applicable to any environment. To this = end I > saw that providing bindings to Win32, WinRT and providing "Visual Studio" > integration would encourage young graduates / IT professionals to at leas= t be > given the tools to develop great Ada applications in a familiar developme= nt IDE > and lets face it, MS does have an impact (be it free or other wise) on th= e > choice of what IDE is used within an IT shop. >=20 > 3) I have done some more research (ie googling) and may have found a work= around > to being able to set project dependencies for VS solutions with multiple > projects, have a look in your spare time :-) TL:DR >=20 > https://blog.tonysneed.com/2011/09/14/build-a-multi-project-visual-studio= -template/ >=20 > 4) and 5) I have as yet not had a chance to look at this in detail yet, w= ill > do this over the weekend, while looking at the packaging/install issue wi= th > VisualAda. >=20 > On a side note: what's your thoughts on the following idea's >=20 > a) Use Nuget to install/reference the WinRT dependencies. But this does m= ean > that each UWP app has its own copy of the WinRT dependencies. Not ideal i= n my > view (unless of course you are diligent and update your refences regularl= y) and > definably / probably NOT workable in a very disciplined IT environment. This is the practice in place for all nugets. It is not as unwise as it fi= rst appears. This practice allows a decoupling of each project so that dif= ferent projects can update to different nuget dependencies as that project = sees fit internally. If not on a per-project basis for what that project/e= xecutable/library needs for its own internal needs, then on what basis? 1) one size fits all projects resident on some developer's individual Windo= ws 10 computer? 2) one size fits all across all developers in a software-development depart= ment? 3) one size fits all across an IT department (or per-.NET-programming-langu= age coding-standards culture) serving multiple software-development departm= ents? 4) one size fits all across a campus? 5) one size fits all across all campuses of an entire corporation? 6) one size fits all across the entire universe of all corporations? Or in fewer words, there is a method to Microsoft's madness. :-)=20 > b) I am not sure that a UWP app can be distributed with a "native DLL" vi= a > Windows Store (as opposed to statically linking to a LIB). If it cant, do= you > see any value in keeping the "UWP DLL" template ? Note that apps that are= side > loaded (ie within a corporate env and NOT distributed via the Windows Sto= re) are > not under the same restriction Although I have not personally distributed a UWP app that contains a Win32 = or WoW DLL (that obeys the subset-of-the-Win32-API restrictions) in the Mic= rosoft Store, it appears to be permitted, if enough requisites are satisfie= d: https://social.msdn.microsoft.com/forums/windowsapps/en-us/c5636e14-422f-4a= b0-b608-2609ad8198e4/metro-style-app-how-to-load-win32-dll Does the DLL in question in VisualAda confine itself to the UWP-compliant s= ubset of the Win32 API?