Cheap And Reliable Hosting :: Create Console Application ASP.NET 5 Using Visual Studio 2015

We know Visual Studio 2015 Preview has been released, it has been announced by Microsoft on November 12, 2014 at the Visual Studio Connect() event in New York, USA. With this new release of Visual Studio 2015 many new features have been added but this article is only about the two new ways to create projects with ASP.NET 5 under the Web node that is in Visual Studio 2015 Preview.

ASP.NET 5 came with Visual Studio 2015 Preview. Now we have a new way to create a Console Application project under Visual C# \Web Template. The following are the two new templates for ASP.NET 5 but this article only explains:


Now use the following procedure to create a Console Application using the ASP.NET 5  project template in Visual Studio 2015 Preview.

Step I

To create a new Console Application using the ASP.NET 5 Console Application project template use the following procedure:

“File” -> “New” -> “Project…”

Now in the New Project window the following project template will be shown in which we will select the language Visual C# and select Web from the child menu of Visual C#. It will look like as in the following figure.


In the preceding project template we can see that now we have the three types of projects, in other words:

  • ASP.NET Web Application
  • ASP.NET 5 Console Application
  • ASP.NET 5 Class Library

But this article only explains ASP.NET 5 Console Application. So select ASP.NET 5 Console Application and continue to create this project.

Step II

Now we can see a quite different look of Solution Explorer in comparison to other older version. Let’s see the following figure that represents the new architecture of projects.


In the preceding picture we are watching various new files that were not available with the older version Console Application. Let’s see the following short explanation that describes the new files and their roles.

This file (project.json) is synchronized with Solution Explorer, it contains the information about dependencies (assemblies references that are being used by this application).

Note: when we remove any dependency from the project then this file will be updated automatically. It behaves very similar to web.config in web applications.

This file contains the following default code that contains the information of version, dependencies, framework and the two new assembly references.

    "version": "1.0.0-*",  
    "dependencies": {  
    "commands": {   
        "run" : "run"  
    "frameworks" : {  
        "aspnet50" : { },  
        "aspnetcore50" : {   
            "dependencies": {  
                "System.Console": "4.0.0-beta-22231"  

In the preceding code we can see that only one dependency is showing, which is:

“System.Console” :”4.0.0-beta-22231” – it is a new assembly that is added with .NET Framework 5 in Visual Studio 2015.


This file contains the information about solutions. In other words it keeps the definition about which is the solution folder for the source files of the current application. When we create a new project in an ASP.NET 5 Console Application, we have the following default line of code in the global.json file.

      "sources": [ "src", "test" ]  

Here src represents the folder that contains all the project’s files that contain the source code that make up our application.

Step III

Now we will write some program code to test the application. So for this program we will write a simple program to display the counting table. Let’s see how we write this code in the Program.cs file.

    using System;   
    using System.Console;   
    namespace AspNet5ConsoleAppExample  
        public class Program  
            public void Main(string[] args)  
                Console.WriteLine("\nThis is an example program written \nin ASP.NET 5 !");  
                ShowCountingTable(1, 100);  
            //A program code to print 1-100  
            private void ShowCountingTable(int startPont, int endPoint)  
                int i = startPont;    
                int symbolCount = 0;  
                while (startPont <= endPoint)  
                    if (symbolCount <= 10)  
                        Write(startPont + "\t");  
                        if (symbolCount == 10)  
                            symbolCount = 0;  

Step IV

Now execute the application to see the output. After successful execution we will see the following output.

Output Window



DotNetNuke 7.3.4 Hosting

Best DotNetNuke 7.3.4 Hosting Service with HostForLIFE.eu

European leading web hosting provider, HostForLIFE.eu announces support for DotNetNuke 7.3.4 hosting plan due to high demand of DotNetNuke CMS users in Europe.

HostForLIFE.eu proudly launches the support of DotNetNuke 7.3.4 Hosting on all their newest Windows Server environment. HostForLIFE.eu DotNetNuke 7.3.4 Hosting plan starts from just as low as €3.00/month only and this plan has supported ASP.NET 5, ASP.NET MVC 5/6 and SQL Server 2012/2014.

DotNetNuke 7.3.4, as well known in the web industry and familiar among .NET developers, is a Web Content Management System (WCMS) based on Microsoft .NET platform. It is an excellent open source software that you can use to manage your website without having much technical knowledge.

HostForLIFE.eu clients are specialized in providing supports for DotNetNuke for many years. They are glad to provide support for European DotNetNuke 7.3.4 hosting users with advices and troubleshooting for their clients website when necessary.

DotNetNuke 7.3.4 is a smaller maintenance release than normal and is focused on addressing the most serious platform issues. DotNetNuke 7.3.4 addresses a number of platform issues and should be the last release before DNN 7.4.0. DNN 7.3.4 added ability to save localized lists to resource file, added method to remove all subscriptions from a ContentItem, fixed issue where AUM was not correctly handling 301 redirects, Fixed issue where popup iframe is not initialized correctly and fixed issue where multiple region/country controls in a profile did not work correctly.

DotNetNuke 7.3.4 will be a great content management system that support many advance website features such as blogs, forums, e-commerce system, photo galleries and more. DotNetNuke 7.3.4 is a great platform to build your web presence with. HostForLIFE.eu can help customize any web software that company wishes to utilize.

Further information and the full range of features DotNetNuke 7.3.4 Hosting can be viewed here http://www.hostforlife.eu/European-DotNetNuke-734-Hosting

About Company
HostForLIFE.eu is European Windows Hosting Provider which focuses on Windows Platform only. HostForLIFE.eu deliver on-demand hosting solutions including shared hosting, Reseller Hosting, Cloud Hosting, Dedicated Servers, and IT as a Service for companies of all sizes.

HostForLIFE.eu is awarded Top No#1 SPOTLIGHT Recommended Hosting Partner by Microsoft (see http://www.asp.net/hosting/hostingprovider/details/953). Their service is ranked the highest top #1 spot in several European countries, such as: Germany, Italy, Netherlands, France, Belgium, United Kingdom, Sweden, Finland, Switzerland and other European countries.


IHostAzure.com :: New Released .Net Framework 4.6

Microsoft has released the newest version of Visual Studio, Visual Studio 2015 Preview, along with .NET Framework 4.6. The newer version of the .NET Framework was introduced 12-13 of Nov 2014. The old version of .NET 4.5.3 will be updated to 4.6 before the final version ships. The .NET Framework 4.6 is highly compatible in comparison to the older version like .NET Framework 4, .NET Framework 4.5, .NET Framework 4.5.1, .NET Framework 4.5.2.

We would like to suggest that this preview version of .NET Framework 4.6 and Visual Studio 2015 is currently available for testing and feedback purposes only but very shortly it will be released as a final release, so before installing this version, please do remember that this preview version is not intended for use on a production computer.

New Features with .NET Framework 4.6

The following are the new features of the .NET Framework 4.6:

  • Changes in the Base Class Library
  • Resizing in Windows Forms controls
  • Support for code page encodings
  • Open-source .NET Framework packages
  • Improvements to event tracing
  • .NET Native
  • Changes in Base Class Library

So many new APIs have been added to this new .NET Framework to enable key scenarios, especially for the Cross-Platform environment. Microsoft has made the following changes:

The CultureInfo.CurrentCulture and CultureInfo.CurrentUICulture properties are now read-write rather than read-only. If you assign a new CultureInfo object to these properties, the current thread culture defined by the Thread.CurrentThread.CurrentCulture property and the current UI thread culture defined by the Thread.CurrentThread and CurrentUICulture properties also change.

The preceding program the gets error that we can’t make the assignment, it is read only but in the .Net Framework 4.6 it’s not an error because this property is now read write.

Additional collections implement ReadOnlyCollection<T> such as Queue<T> and Stack<T>. It implement System.Collections.ObjectModel.ReadOnlyCollection, including System.Collections.Generic.Queue and System.Collections.Generic.Stack.

Additional members support the task-based asynchronous pattern (TAP) such as Task.CompletedTask and NamedPipeClientStream.ConnectAsync.

Resizing in Windows Forms controls

The .NET Framework 4.6 expanded some namespaces that enable us to resize Windows Forms forms, so we need to include the following namespace to enable this feature, in other words:

System.Windows.Forms.DomainUpDown, System.Windows.Forms.NumericUpDown, System.Windows.Forms.DataGridViewComboBoxColumn, System.Windows.Forms.DataGridViewColumn and System.Windows.Forms.ToolStripSplitButton types.

This is an opt-in feature. To enable it, set the EnableWindowsFormsHighDpiAutoResizing element to true in the application configuration (app.config) file. Example code:

<add key="EnableWindowsFormsHighDpiAutoResizing" value="true" />

Support for code page encodings

The core .NET Framework  primarily supports Unicode encodings and by default it provides limited support for code page encodings. We can add support for code page encodings that are available in the .NET Framework but unsupported in .NET Core by registering code page encodings with the Encoding.RegisterProvider method. So we will use the namespace System.Text.CodePagesEncodingProvider. So to make these code pages available to .NET Framework 4.6 Preview use these additional code pages, do the following assemblies reference to our project.

  • Add a reference to the System.Text.Encoding.CodePages.dll assembly to your project.
  • Retrieve a CodePagesEncodingProvider object from the static Instance property.
  • Pass the CodePagesEncodingProvider object to the Encoding.RegisterProvider method.

The .NET Framework for the Windows Desktop supports a large set of Unicode and code page encodings. On the other hand, .NET Framework 4.6 Preview supports only the following encodings:

  • ASCII (code page 20127)
  • ISO-8859-1 (code page 28591)
  • UTF-7 (code page 65000)
  • UTF-8 (code page 65001)
  • UTF-16 and UTF-16LE (code page 1200)
  • UTF-16BE (code page 1201)
  • UTF-32 and UTF-32LE (code page 12000)
  • UTF-32BE (code page 12001)

Open-source .NET Framework packages

Some great .NET packages such as the Immutable Collections and SIMD APIs are now available, open source, on GitHub. To access the code, see NetFx on GitHub. For information on how to contribute to these packages, see the .NET Home Page on GitHub.

Where Immutable Collection is a common approach to use an immutable state that can be passed freely among multiple threads. Immutable collections are different from read-only collections in the sense that unlike read-only collections, they cannot be changed by the provider or consumer of the collection. For example, if you are enumerating a read-only collection, there is a possibility that the collection can be changed on another thread, causing data corruption. This scenario can’t occur if you are using an immutable collection. With an Immutable Collection you can do the following.

GitHub is a repository that contains the foundation libraries that make up the .NET Core development stack as in the following:

  • Share a collection in such a way that its consumer can be assured that the collection will never change.
  • Provide implicit thread safety in multi-threaded applications. No locks required to access collections.
  • Follow functional programming practices.
  • Modify a collection during enumeration, while ensuring that the original collection does not change.
  • Improvements to event tracing
  • An EventSource object can now be constructed directly and you can call one of the Write() methods to emit a self-describing event.
using System.Diagnostics.Tracing
//Assembly: mscorlib (in mscorlib.dll)
public void Write<T>(
string eventName,
T data

In the above example code:

T is the type that defines the event and its associated data. This type must be an anonymous type or marked with the EventSourceAttribute attribute, eventName is  the name of event and data is the object of type T

.Net Native

It is a pre-compilation technology for building and deploying Windows Store apps. It compiles apps that are written in managed code (Like Visual C#) and that target the .NET Framework to native code. It is quite different from Just-In-Time (JIT) as well as the Native Image Generator (NGEN). Basically the .Net Native tool chain converts source code to native code at compile time while JIT is responsible for compiling the IL code to native code (machine specific code). Let’s see the brief comparison with JIT and NGEN as well.

The .NET Native tool chain begins execution when the C# compiler has finished compilation of a Windows Store app. In another words, we can say that the input for the .NET Native is the Windows Store app built by the C# compiler. .NET Native compiles an entire application to a native application. It does not allow you to compile a single assembly that contains a class library to native code so that it can be called independently from managed code. The NGEN compiles assemblies to native code and installs them in the native image cache on the local computer, whereas .NET Native produces native code.


In this article we saw the new features of the .NET version with details. In a future article we will explore the other new features introduced in #vsconnect();

WordPress 401 Hosting - HostForLIFE

HostForLIFE.eu Proudly Launches WordPress 4.0.1 Hosting

European leading web hosting provider, HostForLIFE.eu announced the support for WordPress 4.0.1 hosting plan due to high demand of WordPress 4.0.1 users in Europe. HostForLIFE.eu is a popular online WordPress hosting service provider catering to those people who face such issues. The company has managed to build a strong client base in a very short period of time. It is known for offering fast, fully-managed and secured services in the competitive market.

HostForLIFE.eu hosts its servers in top class data centers that is located in Amsterdam (NL), London (UK), Paris (France) and Seattle (US) to guarantee 99.9% network uptime. All data center feature redundancies in network connectivity, power, HVAC, security, and fire suppression. All hosting plans from HostForLIFE.eu include 24×7 support and 30 days money back guarantee. All hosting plans from HostForLIFE.eu include 24×7 support and 30 days money back guarantee. The customer can start hosting their WordPress 4.0.1 site on their environment from as just low €3.00/month only.

WordPress 4.0.1 patches a critical cross-site scripting vulnerability affecting comment boxes on websites running the content management system software. An attacker would need only to inject malicious JavaScript into a comment that would infect a reader viewing it on the webpage or an admin in the management dashboard.

The update also addresses three other cross-site scripting vulnerabilities, a cross-side request forgery flaw, a denial-of-service bug related to password checks, server-side request forgery issues, and what WordPress called “an extremely unlikely hash collision” that could lead to account compromise. WordPress said it also invalidates links in a password reset email if the user remembers their password and logs in and changes their email address.

WordPress 4.0.1 addresses an additional eight security issues, including three other XSS vulnerabilities that can be exploited by a contributor or an author, a cross-site request forgery (CSRF) that can be leveraged to trick a user into changing his/her password, and a denial-of-service (DoS) bug.

HostForLIFE.eu is a popular online Windows based hosting service provider catering to those people who face such issues. The company has managed to build a strong client base in a very short period of time. It is known for offering ultra-fast, fully-managed and secured services in the competitive market. Their powerful servers are specially optimized and ensure WordPress 4.0.1 performance.

For more information about this new product, please visit http://hostforlife.eu/European-WordPress-401-Hosting

About us:

HostForLIFE.eu is awarded Top No#1 SPOTLIGHT Recommended Hosting Partner by Microsoft (see http://www.asp.net/hosting/hostingprovider/details/953). Their service is ranked the highest top #1 spot in several European countries, such as: Germany, Italy, Netherlands, France, Belgium, United Kingdom, Sweden, Finland, Switzerland and other European countries. Besides this award, they have also won several awards from reputable organizations in the hosting industry and the detail can be found on their official website.