Downloading and running Visual Studio Code Post: 303028959

Sponsored Content

Top Forums UNIX for Beginners Questions & Answers Downloading and running Visual Studio Code Post 303028959 by Circuits on Friday 18th of January 2019 11:56:30 AM

01-18-2019

Registered User

Downloading and running Visual Studio Code

Ubuntu 16.04

I tried downloading the .deb package of Visual Studio Code from here but for some reason it won't open. From Activities Overview if I select the program it shows up in the task panel on the left but it just blinks a few times then goes away. I would rather not have to use snap every time I want to download a program that wasn't specifically designed for UNIX system. Is this some kind of settings problem or privileges problem that has a simple fix?

EDIT: I figured this out, sorry to waste anyone's time.

Last edited by Circuits; 01-18-2019 at 01:02 PM..

This User Gave Thanks to Circuits For This Post:

Circuits

View Public Profile for Circuits

Find all posts by Circuits

3 More Discussions You Might Find Interesting

1. Windows & DOS: Issues & Discussions

Visual Studio .Net

How can I create and run a stand-alone console application in Visual Studio .Net ? (cpp-file)....... ...thanks for any help

2. Programming

Looking for equal to Visual Studio for Unix

Hello all Im looking for IDE to edit / compile / debug similar to VC++ on windows I need it for verity of UNIX platforms, what do you think is the best tool to use And that its learning carve is easy ( as much as possible) . Thanks

3. Programming

Debug with VIsual Studio 6, cpp project

Hi, I"m trying to debug one project in VS6 this is cpp ,with source/headers/resource files. I need to start program from terminal with some parameters, e.g. c> feetcmd -a param1 -d param2, now this program going into the loop and the whole PC is frozen, I tried to do TASK_MANAGER/right...

LEARN ABOUT MINIX

deb-shlibs

deb-shlibs(5)							    dpkg suite							     deb-shlibs(5)

NAME

       deb-shlibs - Debian shared library information file

DESCRIPTION

       shlibs  files  map shared library names and versions (sonames) to dependencies suitable for a package control file.  There is one entry per
       line. Blank lines are not allowed.  Lines beginning with an # character are considered commentary, and are ignored.  All other  lines  must
       have the format

	      [type:] library version dependencies

       The  library  and  version  fields  are whitespace-delimited, but the dependencies field extends to the end of the line.  The type field is
       optional and normally not needed.

       The dependencies field has the same syntax as the Depends field in a binary control file, see deb-control(5).

EXAMPLES

       The shlibs file for a typical library package, named libcrunch1, that provides one library whose soname is libcrunch.so.1, might read

	      libcrunch 1 libcrunch1 (>= 1.2-1)

       The dependencies must mention the most recent version of the package that added new symbols to the  library:  in  the  above  example,  new
       symbols were added to version 1.2 of libcrunch.	This is not the only reason the dependencies might need to be tightened.

SEE ALSO

       deb-control(5), dpkg-shlibdeps(1), deb-symbols(5).

1.19.0.5							    2018-04-16							     deb-shlibs(5)