Was going to make a offline install disk of the Community Edition of VS 2017. Can't even do that without surfing through bullshit. The file you download isn't good enough. Now they say you have to update Windows 8.1. So I try to do that and they say "this update not applicable for your computer".
Oh yeah...if you have the time or patience you may discover something called a hotfix that you can install first.
Oh so let me see...
You gotta download one file to your drive to discover it doesn't work properly. Then you do what they tell you to do only to find out that doesn't work either.
I am trying to create a grid to use in IE 11 using VS and coding the CSS in VS 2017. I get the message 199px not a valid value for CSS3. Also the intellisense gives me -ms-grid-colum and not -ms-grid-columns. Can anyone help me out as to why VS is doing this. The code is:
It should be in the Project's intermediate output folder, usually called Debug or Release, depending on the build type. You should take a good look at the solution directory tree and get familiar with the different directories and what they are used for. Also look at project properties and expand the Macros link to see all the macro expansions that are available.
Let's say that I make a new project called Welcome Program. Okay Visual Studio creates the project and places that in a new folder called Welcome Program. Next, I create a source code file and I call that WelcomeProgram.cpp.
Now here is where I notice that instead of placing that source code file in the main Welcome Program folder that Visual Studio just created, it automatically creates another new folder inside the Welcome Program folder, and it also calls it Welcome Program.
I'm wondering why Visual Studio does this?
Is it better organized this way?
Is there a way to tell Visual Studio not to create another folder, but rather place my source code in the main folder?
I'd like to know...even though I will probably not change it.