VS Code, just noticed I'm getting two different versions of Node.js from powershell, and About.
Because the version from vscode is 'the node version of vscode', you know the vscode is developed by Typescript.
And the version from powershell is your own node version you installed.
Related
Hi I see two enabled versions in my pyenv versions result. Why is that, and what is this feature, how does it work?
Thanks.
Based on your comments, you have 2 versions, 2.7 and 3.9. If you are on a Mac or certain Linux distros, Python 2 comes preinstalled, which is why you would see it along with any other versions you installed (in this case 3.9).
I have installed AWS SDK toolkit for VS 2017. It was working fine. All of a sudden since few days back i am getting error "Error loading AWS profiles: Method not found:'Amazon.Runtime.TcpKeepAlive Amazon.Runtime.ClientConfig.get_TcpKeepAlive()"
I have tried uninstalling and reinstalling the toolkit, also i tried installing it on other machine with VS 2013, but both giving same error.
Is it problem with toolkit or anything changed on AWS side?
I have Windows 10 with latest updates.
VS2017 community edition
VS2013 community edition
Thanks in advance.
It is mostly caused an older version of AWSSDK.core that has already been added to GAC and is forcing your VS to use an older version of AWSSDK.core.dll.
After uninstalling all the other/previous versions of AWSSDK libraries (AWSSDK.S3.dll etc) from GAC solved the problem for me.
Also installing the latest AWSSDK.core.dll to GAC can work.
Hope this info helps someone.
Solution here that worked for me :
https://github.com/aws/aws-sdk-net/issues/1138
I have resolved this issue by uninstalling the latest one and installing this previous stable version of aws toolbar from visual studio update website(exact link https://aws.amazon.com/visualstudio where previous vsix downloaded).. if you cannot find the previous version here I added to my drive you can download.. https://drive.google.com/open?id=1Fkrxmv-dM8fwGDjNqse1Ssdm0k3YYbcH
Once you install old extention, be sure to disable auto update extension in VS.
I am new to Electron.
One of the biggest benefits of Electron is considered that it always comes with the latest versions of Node.js and Chromium.
But can I select which version of node js to use ?
You can't select which version of Node to use, however you can upgrade Node version as long as it is compatible with the current Electron's Chromium version.
Check this for farther information: https://electronjs.org/docs/development/upgrading-node
My company is using an old CentOS6 and they wont update it before months (years?). This is totally out of my control and it obviously makes using up to date software a nightmare.
I would like to use Visual Studio Code as a C++ IDE but its intellisense plugin is running with glibc >=2.14 and Centos6 comes with glibc 2.12.
It also needed some more dependencies I managed to recompile and load with LD_LIBRARY_PATH. I tried compiling a new glibc and load it as well but it segfault, as expected.
I used the compiled version of VSCode from the official website.
I tried compiling it myself but it requires to download many files and my virtual machine does not have Internet, I can only transfer files through ftp. I created a local yarn repository, compiled all appropriate version of Yarn, NodeJS but a compiled binary is trying to download electron and I have no idea where to put the file to trick him into thinking it's downloaded already (assuming I could).
There are standalone solutions to run software on old distribution, like AppImage but VSCode is not part of their apps.
Would you have any idea on how to run VSCode on Centos6? Did you ever try to compile VSCode without and Internet Connection?
Currently the only viable solution I see would be to create an AppImage at home.
To run VS Code Server on CentOS 6, I followed the "glibc and libstdc ++ on RHEL / CentOS 6 update" article from here.
Perhaps this option will help you.
I'm using NAnt 0.85 as a build script. Part of the script is to complete the signing process of delay-signed assemblies using the delay-sign task.
When the script is executed on the build server, it runs without any problems.
When I run the same script on my local development machine, I get the warning:
The SDK for the 'net-2.0' framework is not available or not configured.
at NAnt.Core.Tasks.ExternalProgramBase.DetermineFilePath()
at NAnt.Core.Tasks.ExternalProgramBase.get_ProgramFileName()
at NAnt.Core.Tasks.ExternalProgramBase.PrepareProcess(Process process)
at NAnt.Core.Tasks.ExternalProgramBase.StartProcess()
at NAnt.Core.Tasks.ExternalProgramBase.ExecuteTask()
at NAnt.DotNet.Tasks.DelaySignTask.ExecuteTask()
at NAnt.Core.Task.Execute()
at NAnt.Core.Target.Execute()
at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies)
at NAnt.Core.Tasks.CallTask.ExecuteTask()
at NAnt.Core.Task.Execute()
at NAnt.Core.Target.Execute()
at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies)
at NAnt.Core.Project.Execute()
at NAnt.Core.Project.Run()
I'm pretty sure I've got the SDK installed with Visual Studio 2008/2010.
Why do I receive this error and what can I do to diagnose the problem further?
The error is because I didn't have the .NET 2.0 SDK. I assumed SDKs were installed with Visual Studio, but apparently only the current version is. For 2008, that's .NET 3.5 SDK, not 2.0 and previous versions aren't provided.
Downloading and installing the 2.0 SDK from Microsoft resolved the issue.
For me, the fix was to update nant to 0.92. Nothing I did with the .NET 2.0 SDKs worked.
I also ran into this problem. I ensured that the 2.0 SDK was installed, and I upgraded to the latest version of NAnt, but that did not fix it. I verified the registry entries and even hard-coded the location of the SDK in the config -all to no avail.
What finally worked for me was to install the 32-bit version of the .NET 2.0 SDK on my 64-bit machine.