Re: ANN: VisualAda (Ada Integration for Visual Studio 2017 & 2019) release 1.2.0

[Greg <arkman3112@gmail.com>]

Quick thoughts:

a) Use Nuget to install/reference the WinRT dependencies. But this does mean 
that each UWP app has its own copy of the WinRT dependencies. Not ideal in my 
view (unless of course you are diligent and update your refences regularly) and definably / probably NOT workable in a very disciplined IT environment. 

This would be massively good, one less step (actually more than one) to get up and running with a real Ada/UWP app. Just so I'm clear ... you mean a separate NuGet package for each Win10 SDK version, i.e. 1803/17134? Not sure I've seen that methodology, but I'm sure it's used. And for example, my personal stuff is running (now) Insiders with 18362 while my work laptop is currently suffering with 16299.

b) I am not sure that a UWP app can be distributed with a "native DLL" via 
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 Store) are not under the same restriction.

At first I thought, nah, I'd dump it because for my personal use cases (right now, anyway), I don't really have a use for it. I was just trying to break - sorry, I mean test :) - the different templates. But in enterprise situations, where you often couldn't care less about Windows Store - sure, it'd be very valuable. I mean, I build "common" DLLs (.NET) all the time, each used by 3-4 different apps. Absolutely.

... personally - and quite selfishly - I'd rather see Intellisense advance (which you've mentioned in your READMEs I know) , Object Explorer support of some kind, (probably the same thing, but then again I've never added that sort of extension support for a language before.) You know, the whole VS kind of stuff we've all come to expect and love (I've never been one to say, "hey, I'm a REAL developer - I don't NEED Intellisense" :))