How to install Visual Studio 2015 Professional Free Lifetime key 100% WORKING FEB 2016 - Duration: 6:05. Life Suggestion 145,993 views.
Visual Basic 2017 is the latest version of Visual Basic launched by Microsoft in 2017. Visual Basic 2017 is bundled together with other Microsoft Programming languages C# C++, F#, JavaScript, Python and other development tools in an integrated development environment called Visual Studio Community 2017 Release Candidate. Microsoft has added many new features in Visual Studio 2017 particularly those features for building mobile applications and gaming as well as web and cloud-based applications.
Visual Studio Community 2017 RC can be downloaded from the link below. You need to have a Microsoft account to download the package.
https://www.visualstudio.com/downloads/
After clicking on the link above, the following download page appears:
After downloading the file, run the VS2017RC community installer file
vs_community__695901156.1467100807 (7).exe.
If you receive a User Account Control notice, click Yes. Next, it will ask you to acknowledge the Microsoft License Terms and the Microsoft Privacy Statement, as shown in Figure 1.2. Click Install to continue.
You’ll see several status screens that show the progress of the installation. After the installer is finished installing, it’s time to pick the feature set that you want, as shown in Figure 1.3. Since we are keen on developing Visual Basic 2017 desktop app, we will select the .NET desktop development component. Besides that, you might want to install a particular language by clicking the Language packs. After making your selections, click install.
Upon completion of the installation, you are now ready to launch Visual Studio 2017 RC and start programming in Visual Basic 2017
The .NET Desktop application development in Visual Studio 2017 is designed for building WPF, Windows Forms, and console apps using.NET Framework. With shorter solution load time, improved IntelliSense, code navigation, and refactoring save you time and effort on everyday tasks, you can build desktop apps with great UI and better performance.
1.2 Visual Studio Community 2017 Start Page
When you first launch Visual Studio Community 2017, the following start Page appears, as shown in Figure 1.4
Now click on New Project under Start to launch the New Project window, as shown in Figure 1.5
In the New Project window, you can build many kinds of applications using different programming languages. They are Visual Basic, Visual C#, Visual C++, Visual F#, JavaScript, Python and more. As we are only dealing with Visual Basic, we shall click on Visual Basic Windows Form APP(.NET Framework). Before you continue, enter the application name at the bottom. Change the default name WindowsApplication1 to My First VB2017 project.
1.3 Visual Basic Community 2017 Integrated Development Environment
Upon clicking Windows Form Application, the Visual Basic Community 2017 Integrated Development Environment appears, as shown in Figure 1.6. You can see that the name of the project you entered earlier appears on the top right corner of the IDE.
Visual Basic Community 2017 IDE comprises a few windows, the Form window, the Solution Explorer window and the Properties window. It also consists of a toolbox which contains many useful controls that allow a programmer to develop his or her Visual Basic 2017 programs. The toolbox can be hidden or dragged to the bottom or side of the window.
Now, we shall proceed to show you how to create your first program in Visual Basic 2017. First, change the text of the form to My First VB2017 Program in the properties window, it will appear as the title of the program. Next, insert a button and change its text to Show Message. The design interface is shown in Figure 1.7
Click on the Show Message button to bring up the code window and enter the following statement between Private Sub and End Sub procedure, as shown in Figure 1.8
When you run this program and click on the show Message button, you should get the following popup message box.
The function MsgBox is a built-in function of Visual Basic 2017 and it will display the text enclosed within the brackets.Now you have created your first program in Visual Basic 2017, we shall learn more Visual Basic 2017 programming techniques in coming lessons.
GDI+ is the way to draw shapes, fonts, images or generally anything graphic in Visual Basic .NET.
This article is the first part of a complete introduction to using GDI+ in Visual Basic .NET.
GDI+ is an unusual part of .NET. It was here before .NET (GDI+ was released with Windows XP) and it doesn't share the same update cycles as the .NET Framework. Microsoft's documentation usually states that Microsoft Windows GDI+ is an API for C/C++ programmers into the Windows OS. But GDI+ also includes the namespaces used in VB.NET for software-based graphics programming.
WPF
But it's not the only graphics software provided by Microsoft, especially since Framework 3.0. When Vista and 3.0 were introduced, the totally new WPF was introduced with it. WPF is a high-level, hardware accelerated approach to graphics. As Tim Cahill, Microsoft WPF software team member, puts it, with WPF 'you describe your scene using high-level constructs, and we’ll worry about the rest.' And the fact that it's hardware accelerated means that you don't have to drag down the operation of your PC processor drawing shapes on the screen. Much of the real work is done by your graphics card.
We've been here before, however. Every 'great leap forward' is usually accompanied by a few stumbles backward, and besides, it will take years for WPF to work its way through the zillions of bytes of GDI+ code. That's especially true since WPF just about assumes that you're working with a high-powered system with lots of memory and a hot graphics card. That's why many PCs couldn't run Vista (or at least, use the Vista 'Aero' graphics) when it was first introduced. So this series continues to be available on the site for any and all who continue to need to use it.
Good Ol' Code
GDI+ isn't something that you can drag onto a form like other components in VB.NET. Instead, GDI+ objects generally have to be added the old way -- by coding them from scratch! (Although, VB .NET does include a number of very handy code snippets that can really help you.)
To code GDI+, you use objects and their members from a number of .NET namespaces. (At the present time, these are actually just wrapper code for Windows OS objects which actually do the work.)
Namespaces
The namespaces in GDI+ are:
System.Drawing
This is the core GDI+ namespace. It defines objects for basic rendering (fonts, pens, basic brushes, etc.) and the most important object: Graphics. We'll see more of this in just a few paragraphs.
System.Drawing.Drawing2D
This gives you objects for more advanced two-dimensional vector graphics. Some of them are gradient brushes, pen caps, and geometric transforms.
System.Drawing.Imaging
If you want to change graphical images - that is, change the palette, extract image metadata, manipulate metafiles, and so forth - this is the one you need.
System.Drawing.Printing
To render images to the printed page, interact with the printer itself, and format the overall appearance of a print job, use the objects here.
System.Drawing.Text
You can use collections of fonts with this namespace.
Graphics Object
The place to start with GDI+ is the Graphics object. Although the things you draw show up on your monitor or a printer, the Graphics object is the 'canvas' that you draw on.
But the Graphics object is also one of the first sources of confusion when using GDI+. The Graphics object is always associated with a particular device context. So the first problem that virtually every new student of GDI+ confronts is, 'How do I get a Graphics object?'
There are basically two ways:
You can use the e event parameter that is passed to the OnPaint event with the PaintEventArgs object. Several events pass the PaintEventArgs and you can use the to refer to the Graphics object that is already being used by the device context.
You can use the CreateGraphics method for a device context to create a Graphics object.
Here's an example of the first method:
Click Here to display the illustration
Add this into the Form1 class for a standard Windows Application to code it yourself.
In this example, a Graphics object is already created for the form Form1. All your code has to do is create a local instance of that object and use it to draw on the same form. Notice that your code Overrides the OnPaint method. That's why MyBase.OnPaint(e) is executed at the end. You need to make sure that if the base object (the one you're overriding) is doing something else, it gets a chance to do it. Often, your code works without this, but it's a good idea.
PaintEventArgs
You can also get a Graphics object using the PaintEventArgs object handed to your code in the OnPaint and OnPaintBackground methods of a Form. The PrintPageEventArgs passed in a PrintPage event will contain a Graphics object for printing. It's even possible to get a Graphics object for some images. This can let you paint right on the image the same way you would paint on a Form or component.
Event Handler
Another variation of method one is to add an event handler for the Paint event for the form. Here's what that code looks like:
CreateGraphics
The second method to get a Graphics object for your code uses a CreateGraphics method that is available with many components. The code looks like this:
There are a couple of differences here. This is in the Button1.Click event because when Form1 repaints itself in the Load event, our graphics are lost. So we have to add them in a later event. If you code this, you'll notice that the graphics are lost when Form1 has to be redrawn. (Mimimize and maximize again to see this.) That's a big advantage to using the first method.
Most references recommend using the first method since your graphics will be repainted automatically. GDI+ can be tricky!