This is a follow-up to another posting I had about problems with launching the VSTA editor from various scripts. I have been experimenting with this further and while available RAM seems to have something to do with it, more clearly appears to be that
launching VSTA requires me to be logged on as administrator. IT security only allows us developers to get Admin for one hour at a time -- have to request it, log off, then log back on. After an hour it expires and we would have to request again,
log off and then back on yet again for another hour. Needless to say, this would be rather frustrating. Any ideas about how/why launching VSTA from SSDT script tasks or components would require administrator privs and how I could get around that?
Thanks kindly,
Mike