Visual Studio cannot directly run on OS X, we need to get Windows running on the Mac Computer, then install VS on the Windows OS, there are multiple options for running Windows on a Mac and you can have a look at this blog. Maybe some of you know, that Visual Studio (Preview) is ready to use. I have simple question, maybe I did something wrong, or it doesn't work properly. When I start to debug Console Application doesn't want to let me read name from keyboard. Console application in C# for Beginners In the early 1970s the creators of the C wrote a book of the same name intended to teach the skills necessary to program in C.

To start up Visual Studio Express for the first time, go to the Start screen on Windows 8 or the Start menu on Windows 7 and look for the Menu Choice or tile for Visual Studio Express for desktop. You'll see that it's named VS Express. If this is the first time you've started up Visual Studio on your system, you'll be asked to register and provide a serial number. Follow the prompts and check your email for the serial number that will be emailed to you by Microsoft. Registration is free, but required.

Once you've started it up you'll be able to create your first project. To create a project, go to the Menu and choose File > New Project. Visual Studio Express for Windows Desktop lets you create applications using three programming languages, Visual Basic, Visual C#, and Visual C++. Within the Visual Basic section, choose the Windows category and you'll find a number of options. You can build three different types of applications, a Windows Forms application, a WPF or Windows Presentation Foundation application, or a Console application.

Create a Console Application. After selecting that option, name the application Console First App. I'm placing the application and project in my exercisefiles02gettingstarted folder, but you can place it anywhere you like. A Console App starts off as a simple Visual Basic file called a module. And it has a subroutine or a method called Main. This Main method will be executed automatically as the application starts up.

So place the cursor between the sub declaration and the end sub declaration. And any code you put there will be executed. Our first step is to execute a simple, hello world, outputting a simple string. And I'll use an expression that looks like this. Console.WriteLine. In Visual Studio, you can auto complete code by pressing the Tab key. So I started typing write and then I moved the cursor to WriteLine and pressed Tab.

Now I'll put in an opening parenthesis and then a simple string of, hello world. In Visual Basic you don't need to finish the line with a semi colon or any other punctuation. All you need is the end of the statement and in this case that's the closing parenthesis. I'll save my changes with Ctrl+s, and then I'll run the application. When you're working with a console application, if you run with debugging, you'll see that the console window flies by very, very fast, but doesn't stay open.

If all you're doing is outputting content into the console, run without debugging, and you can do that by going to the Menu and choosing Debug > Start Without Debugging, or pressin Ctrl+F5. And there is the result. I see the string, Hello World, and a prompt, press any key to continue. And when I press any key the console window closes. Now I'll add a few more lines of code. I'm going to declare a couple of simple variables.

In Visual Basic you declare a variable using the key word dim. I'll talk about what that keyword does and what it means later. But for now, all you need to know is that every variable should start with dim. Then, assign the variable name. I'll set it as value one and I'll give it a value of five. If you already know c style languages, such as C, C++, or Java, you might be wondering at this point whether you need to declare data types. That is, whether a variable is an integer, a double, a string, or some other type.

And the answer is, in Visual Basic, you don't have to. You can follow a pattern known as typeless programming, where you let the Visual Studio compiler infer the data types. In this case, I'm saying that the value is 5 and the compiler will respond by saying that the value 1 is an integer. Next I'll declare a second variable. I will say Dim value2 equals 20. You may have noticed that I was prompted for a keyword called as, but I'm not going to use that right now.

Finally I will declare a third variable named total. And I'll get its value by adding the first two variable together with this statement. Dim total equals value one plus value two. Just as I did earlier, with Autocompleting Command, you can also autocomplete variable names. For example, if I type in just val. I'll see a list of all available identifiers that have that string and I can choose the one I want and press tab. Now, I'll output to the console again.

Visual Studio Console Application Example

I'll once again use Console.WriteLine and I'll output a concatenated string. That's two strings put together. I'll start with the result is and then I'll append to that by putting in a plus operator and then I'll output total.ToString. That's how you convert a number to a string. I'll save my changes, once again with Ctrl S. And I'll run with Control F5, and there's the result.

25. So that's a look at how to build a very simple console application in Visual Studio using the visual basic programming language. We'll talk a a lot more about this code and the concept of typeless programming later on in the course. And for most of this course I won't be building console applications. I'll be building Windows Presentation Foundation or WPF-based desktop applications but if you need to use a console application, this is how you get started.

We’ve just published an update to the Console UWP App project templates on the Visual Studio marketplace here. The latest version (v1.5) adds support for C#. The C# template code only works with Visual Studio 2017 version 15.7 or later. In a previous post, I described how to build a simple findstr UWP app using the C++ Console templates. In this post, we’ll look at how to achieve the same with C#, and call out a few additional wrinkles you should be aware of.

Having installed the updated VSIX, you can now choose a C# Console UWP App from the New Project dialog:

Note that C# console apps are only supported from version 10.0.17134.0 of the platform. You should therefore specify a version >= 10.0.17134 for the minimum platform version when you create your project. If you forget this step, you can fix it at any time later by manually editing your .csproj and updating the TargetPlatformMinVersion value.

Also note that with the C# template, you might get the error message “Output type ‘Console Application’ is not supported by one or more of the project’s targets.” You can safely ignore this message – even though it is flagged as an error, it doesn’t actually make any difference to anything and doesn’t prevent the project from building correctly.

As with the C++ template, the generated code includes a Main method. One difference you’ll notice with the C# version is that the command-line arguments are passed directly into Main. Recall that in the C++ version, you don’t get the arguments into main, but instead you need to use the global __argc and __argv variables. Notice that you can also now use the System.Console APIs just as you would in a non-UWP console app.

Visual Studio For Mac Console Application C++ Win32

As before, for the file-handling behavior needed for the findstr app, you need to add the broadFileSystemAccess restricted capability. Adding this will cause your app to get some extra scrutiny when you submit it to the Store. You will need to describe how you intend to use the feature, and show that your usage is reasonable and legitimate.

Visual Studio For Mac Console Application C++ Programming

Because the app will be doing some simple file handling and pattern matching, in the C++ version, I had to #include the Windows.Storage.h and regex, and declare the corresponding namespaces. In C#, you need the equivalent Windows.Storage and System.Text.RegularExpressions namespaces.

For the findstr functionality, recall that I’m expecting a command-line such as “CsFindstr foo C:Bar”, where “foo” is the pattern to search for, and “C:Bar” is the folder location from which to start the recursive search. I can strip out all the generated code in Main, and replace it with firstly a simple test for the expected number of command-line arguments, and secondly a call to a RecurseFolders method (which I’ll write in a minute). In the C++ version, I tested __argc < 3, but in the managed version I need to test the incoming args.Length for < 2 (the executable module name itself is not included in the C# args).

Now for the custom RecurseFolders method. Inside this method, I need to use a number of async methods for the file handling, so the method needs to be declared async – and this is also why I called Wait() on the Task return from the method back up in Main. I can’t make Main async, so I must make sure to contain all meaningful async return values within the lower-level methods.

In this method, I’ll get the StorageFolder for the root folder supplied by the user on the command-line, get the files in this folder, and then continue down the folder tree for all sub-folders and their files:

The GetDirectories method is the actual recursive method that performs the same operation (get the files in the current folder, then recurse sub-folders):

Finally, the SearchFile method, which is where I’m doing the pattern-matching, using Regex. As before, I’m enhancing the raw search pattern to search for any whitespace-delimited “word” that contains the user-supplied pattern. Then I walk the returned MatchCollection, and print out all the found “words” and their position in the file.

With this, I can now press F5 to build and deploy the app. For console apps it often makes sense to set the Debug properties to “Do not launch, but debug my code when it starts” – because the most useful testing will be done with varying command-line arguments, and therefore by launching the app from a command prompt rather from Visual Studio.

I can test the app using a command window or powershell window:

That’s it! You can now write Console UWP apps in C#. Full source code for this sample app is on Githubhere.