Aws-lambda-dotnet: Can't install AWSToolkitPackage.vsix
The best beginning is to never begin!
10/10/2017 3:04:23 PM - Skipping 'C:\Users\brian.cullinan\AppData\Local\Microsoft SDKs' as it doesn't exist
10/10/2017 3:04:23 PM - An extension with a matching Identifier is already installed to this product.
10/10/2017 3:04:23 PM - Found installed product - Visual Studio Build Tools 2017 (2)
10/10/2017 3:04:23 PM - System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.VisualStudio.ExtensionManager.EngineUtilities.TryGetProductVersion(String productVersionString, Version& productVersion)
at Microsoft.VisualStudio.ExtensionManager.EngineUtilities.TryGetProductVersionFromPath(String path, Version& productVersion)
at VSIXInstaller.SupportedVSSKU.get_VersionWithBuildRevisionInfo()
at VSIXInstaller.App.IsValidSKUForExtension(SupportedVSSKU supportedSKU, IExtension extension, List`1 validSKUs)
at VSIXInstaller.App.ShouldAddSkuToValidSkuList(SupportedVSSKU sku, IInstallableExtension extension, List`1 validSKUs)
at VSIXInstaller.App.GetInstallableData(String vsixPath, Boolean isRepairSupported, IEnumerable`1& skuData)
at VSIXInstaller.App.Initialize(Boolean isRepairSupported)
at VSIXInstaller.App.Initialize()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
briancullinan
All 7 comments
We need the whole log that you would get if you clicked the "View Install Log". We have contact Microsoft about the issue with Visual Studio extension installer but until we get a full log we can't give them enough information for them to help us.
Also do you know if this is latest patch version of Visual Studio 2017? For example my version is 15.3.5, when we discussed this issue with MS engineers they said the 15.3 update did have some fixes to the extension installer.
normj
on 11 Oct 2017
Yeah sure, wouldn't be surprised if they changed something.
VSIXInstaller_89309f8d-69cc-4d23-ad8b-fb36c6829ecb.log
VS version 15.4.0
briancullinan
on 11 Oct 2017
Got a response back from Microsoft and looks like this is a known issue that has a been fixed but hasn't been released yet. He passed along a couple work arounds through.
A work around for this user would be to invoke the vsix installer from the command line and specify the specific instance that they would like to target with the install. For example the command would look like this:
“vsixinstaller.exe /instanceids:”. To find the instance id they can go to %programdata%/Microsoft/VisualStudio/Packages/_Instances, and there they will find folders whose names correspond to the instance ids of all of their installed instances.
Another possible solution could be to go to the 2017 BuildTools install directory under..\ BuildTools\Common7\Tools\ and remove/rename the LaunchDevCmd.bat file found there before they start their install by double clicking the VSIX. After the VSIX has finished installing they should put the file back.
normj
on 11 Oct 2017
Wow. Impressive. I wish I had a direct line to Microsoft! ;) Thank you
for looking into this. There's some gold here I've never even considered.
On Wed, Oct 11, 2017 at 1:43 PM, Norm Johanson notifications@github.com
wrote:
Got a response back from Microsoft and looks like this is a known issue
that has a been fixed but hasn't been released yet. He passed along a
couple work arounds through.A work around for this user would be to invoke the vsix installer from the
command line and specify the specific instance that they would like to
target with the install. For example the command would look like this:
“vsixinstaller.exe /instanceids: ”. To find the instance id they can go to
%programdata%/Microsoft/VisualStudio/Packages/_Instances, and there they
will find folders whose names correspond to the instance ids of all of
their installed instances.
Another possible solution could be to go to the 2017 BuildTools install
directory under..\ BuildTools\Common7\Tools\ and remove/rename the
LaunchDevCmd.bat file found there before they start their install by double
clicking the VSIX. After the VSIX has finished installing they should put
the file back.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-lambda-dotnet/issues/171#issuecomment-335942113,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AX5Xbh0GpC-msef3_ENAOfWbkPYBp94dks5srShtgaJpZM4P0pWL
.
--
CONFIDENTIALITY NOTICE: The contents of this email message and any
attachments are intended solely for the addressee(s) and may contain
confidential and/or privileged information and may be legally protected
from disclosure. It is then shared with tech companies, bots, hackers,
government agencies, and marketers. The security of this message is none,
and it may be shared on Instagram at anytime. If you are OK with this,
please respond. There isn't really any security or privacy anywhere. If
you disagree you may want to go camping and talk to people face-to-face
like in old times.
briancullinan
on 11 Oct 2017
I wouldn't say a direct line :) The Visual Studio 2017 has a lot changes for extensions which was great because those changes are what allowed us to publish AWS Toolkit through the VS Marketplace finally. I give full props to the VS extension team to help smooth out those changes.
normj
on 11 Oct 2017
@normj Thank you! Can you ask them to look at this one too? lol ;) https://twitter.com/VisualStudio/status/917900154426060800
briancullinan
on 11 Oct 2017
Closing as I assume the work around worked. I'm not comfortable asking Microsoft questions on your behalf that are not related to AWS.
normj
on 27 Oct 2017
Related issues
01binary
·
7Comments
martincostello
·
4Comments
ghost
·
3Comments
Aerendel
·
5Comments
Xocix
·
7Comments
Most helpful comment
Got a response back from Microsoft and looks like this is a known issue that has a been fixed but hasn't been released yet. He passed along a couple work arounds through.