WindowsASPNETHosting.in VS IndiaLinks – Which one is The Best ASP.NET Core 1.0 Hosting in India ?

CheapWindowsHostingReview.com |Best and cheap ASP.NET Core 1.0 hosting. If you are searching for the best web hosting service online, read all our updated Web Hosting Reviews & Comparison 2017 to ensure you make a well informed decision. On this page we have investigated and reviewed all the major web hosting companies so you can easily differentiate features, pricing, support, service uptime and customer feedback. Every review was taken around the last 6 months and each hosting provider is reviewed on regular basis. If you have any experience with these website hosts services please feel free to write your own review of their service to help other people to find the best web hosting service for their online business. Our web hosting comparisons and reviews include customer support, features, pricing, value for money, security and reliability. All the best and we hope we help you to find your perfect hosting partner.

To choose the best Windows hosting for your websites, we will compare two of this India Windows hosting providers in the industry. This WindowsASPNETHosting.in VS IndiaLinks comparison is about to make clear that who is a better option ASP.NET Core 1.0 Hpsting in India.

India Windows Hosting Review

Item	WindowsASPNETHosting.in	IndiaLinks
Price	*****	***
Features	*****	*****
Uptime	*****	****
Speed	*****	****
Technical Support	*****	****

WindowsASPNETHosting.in is the India’s #1 Windows hosting provider that offers the most reliable world class Windows hosting solutions for customers. WindowsASPNETHosting.in provides high quality affordable India’s Windows hosting services for personal and companies of all sizes. You can host your website with an innovative, reliable, and a friendly India’s Windows hosting company who cares about your business.

Indialinks Founded in 1997 Based in Mumbai, India Industry Leader in Managed Hosting Solutions. They are providing now web hosting on Linux, Window, Window reseller hosting, Linux Reseller hosting, VPS Hosting. They also treat their costumer as family member and costumer’s trouble as their own trouble.

WindowsASPNETHosting.in VS IndiaLinks: Pricing & Features

WindowsASPNETHosting.in releases four plans called Personal, Developer, Business and Expert at the prices of INR 159.99/month 35% OFF , INR 299.99/month 35% OFF , INR 679.99/month 35% OFF andINR 1099.99/month 35% OFF . Three billing cycles with different prices are available in WindowsASPNETHosting.in best India Windows hosting package. You can choose between 3-months, 1-year, 3-years and 5-years payment methods. WindowsASPNETHosting.in also supports 30-days money back guarantee. On the contrary, IndiaLinks offers several kinds of India Windows hosting plan starting from $149.99/mo in regular time. IndiaLinks only provide the costumers yearly payment method.

In below, we create a feature-comparison table of this two best India Windows hosting companies:

Item	WindowsASPNETHosting.in	IndiaLinks
Domain	Unlimited	1
Bandwidth	30 GB	16 GB
Disk Space	3 GB	8 GB
Windows Server	Version 2008/2012	Version 2008
IIS Version	IIS 7/7.5/8.0/10	IIS 7
ASP.NET Version	ASP.NET v. 5/4.6/4.5.2/4.5.1	ASP.NET v. 2.0 /3.0/4.0
ASP.NET MVC Version	ASP.NET MVC v. 5.1.1/5.15.2/ 5.1.2/6.0	ASP.NET MVC v. 2.0/3.0
MSSQL Version	MSSQL 2008/2012/2014	MSSQL 2008/2012
Complete Features	MORE INFO	MORE INFO

From the above comparison list, both of them are fully ASP.NET compatible. However, WindowsASPNETHosting.in and IndiaLinks are different from each other in many features. They both support the .NET technology, like Windows Server, IIS, isolated application pool, LINQ, AJAX, Silverlight, Full Trust, URL rewrite module. But WindowsASPNETHosting.in supports almost all version of Windows Server, ASP.NET, ASP.NET MVC, IIS and MSSQL database. WindowsASPNETHosting.in also supports ASP.NET Core 1.0 hosting with affordable price. What’s more WindowsASPNETHosting.in also provides unlimited domain while IndiaLinks still limit their domain. From the above table, we can conclude that WindowsASPNETHosting.in has more rich-featured India Windows hosting that what IndiaLinks has offered.

WindowsASPNETHosting.in VS IndiaLinks: Uptime & Speed

To ensure uptime and speed, both WindowsASPNETHosting.in and IndiaLinks have been investing much money and time. WindowsASPNETHosting.in leverages best-in-class connectivity and technology to innovate industry-leading, fully automated solutions that empower enterprises with complete access, control, security, and scalability. They own and operate three world-class data centers strategically located in Mumbai (India), London (UK) and Washington D.C.(US). WindowsASPNETHosting.in promise you in delivering 99.9% uptime. When it comes to IndiaLinks, they also located their data center in Chennai, Tamil Nadu and promise 99.9% uptime guarantee. However, most of IndiaLinks’s costumers are disappointed because of their slow speed website.

WindowsASPNETHosting.in VS IndiaLinks: Technical Support

WindowsASPNETHosting.in offers 24/7 support through tickets, e-mail and contact form. When we contacted the their support representatives via e-mail, we got responses from WindowsASPNETHosting.in within an average of 5 minutes. In the other hand, IndiaLinks only provide phone call for their costumer. We’ve tried to call their support but they always show the busy tune. We do believe that WindowsASPNETHosting.in has more responsive support team.

Conclusion: WindowsASPNETHosting.in VS IndiaLinks?

From the combination of high performance, responsive support, rich-featured hosting and reasonable pricing, we conclude that WindowsASPNETHosting.in is better in serving India Windows hosting. It is clear that WindowsASPNETHosting.in is a more favorable choice due to its cost-effective features and considerate customer service.

Deploy ASP.NET Core to IIS & How ASP.NET Core Hosting Works

CheapASPNETHostingReview.com | Best and cheap ASP.NET Core 1.0 hosting. In this article, we will review how to deploy an ASP.NET Core application to IIS. Deploying an ASP.NET Core app to IIS isn’t complicated, but ASP.NET Core hosting is a little different than ASP.NET.

How to Configure Your ASP.NET Core App For IIS

The first thing you will notice when creating a new ASP.NET Core project is they are actually console applications. Your project now contains a Program.cs file just like a console app would have and it contains the following code:

 public class Program
{
    public static void Main(string[] args)
    {
        var host = new WebHostBuilder()
            .UseKestrel()
            .UseContentRoot(Directory.GetCurrentDirectory())
            .UseIISIntegration()
            .UseStartup()
            .Build();

        host.Run();
    }
}

public class Program

{

public static void Main(string[] args)

{

var host = new WebHostBuilder()

.UseKestrel()

.UseContentRoot(Directory.GetCurrentDirectory())

.UseIISIntegration()

.UseStartup()

.Build();

host.Run();

}

What is the WebHostBuilder?

All ASP.NET Core applications require a WebHost object that essentially serves as the application and web server. WebHostBuilder is used to configure and create the WebHost. You will normally see UseKestrel() and UseIISIntegration() in the WebHostBuilder setup code.

What do these do?

UseKestrel() – This registers the IServer interface for Kestrel as the server that will be used to host your application. In the future, there could be other options, including WebListener which will be Windows only.
UseIISIntegration() – This tells ASP.NET that IIS will be working as a reverse proxy in front of Kestrel. This then specifies some settings around which port Kestrel should listen on, forwarding headers, and other details.

If you are planning to deploy your application to IIS, UseIISIntegration() is required

What is AspNetCoreModule?

You may have noticed that ASP.NET Core projects create a web.config file. This is only used when deploying your application to IIS. It registers the AspNetCoreModule as an HTTP handler.

Default web.config for ASP.NET Core:

If you are planning to deploy your application to IIS, UseIISIntegration() is required

Default web.config for ASP.NET Core:

&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;configuration&gt;
  &lt;system.webServer&gt;
    &lt;handlers&gt;
      &lt;add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified"/&gt;
    &lt;/handlers&gt;
    &lt;aspNetCore processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" forwardWindowsAuthToken="false"/&gt;
  &lt;/system.webServer&gt;
&lt;/configuration&gt;

<?xml version="1.0" encoding="utf-8"?>

<system.webServer>

</handlers>

</system.webServer>

</configuration>

AspNetCoreModule handles all incoming traffic to IIS and acts as the reverse proxy that knows how to hand the traffic off to your ASP.NET Core application. You can view the source code of it on GitHub. It also ensures that your web application is running. It is responsible for starting your process up.

Install .NET Core Windows Server Hosting Bundle

Before you deploy your application, you need to install the .NET Core hosting bundle for IIS. This will install the .NET Core runtime, libraries, and the ASP.NET Core module for IIS.

After installing it, you may need to do a “net stop was /y” and “net start w3svc” to ensure all the changes are picked up for IIS.

Steps to Deploy ASP.NET Core to IIS

Before you deploy, you need to make sure that WebHostBuilder is configured properly to use Kestrel and IIS. Your web.config should also exist and look similar to our example above.

Step 1: Publish to a File Folder

Step 2: Copy Files to Preferred IIS Location

Now you need to copy your publish output to where you want the files to live. If you are deploying to a remote server, you may want to zip up the files and move to the server. If you are deploying to a local dev box, you can copy them locally.

For my example, I am copying the files to C:\inetpub\wwwroot\AspNetCore46

You will notice that with ASP.NET core there is no bin folder and it potentially copies over a ton of different .NET dlls. Your application may also be an EXE file if you are targeting the full .NET Framework. My little sample project had over 100 dlls in the output.

Step 3: Create Application in IIS

First, create a new IIS Application Pool. You will want to create one under the .NET CLR version of “No Managed Code“. Since IIS only works as a reverse proxy, it isn’t actually executing any .NET code.

Second, create your new application under your existing IIS Site, or create a new IIS site. Either way, you will want to pick your new IIS Application Pool and point it at the folder you copied your ASP.NET publish output files to.

Step 4: Load Your App!

At this point, your application should load just fine. If it does not, check the output logging from it. Within your web.config file you define how IIS starts up your ASP.NET Core process. Enable output logging by setting stdoutLogEnabled=true and you may also want to change the log output location as configured in stdoutLogFile. Check out the example web.config before to see where they are set.

Advantages of Using IIS with ASP.NET Core Hosting

Microsoft recommends using IIS with any public facing site for ASP.NET core hosting. IIS provides additional levels of configurability, management, security, logging, and many other things. Check out my blog post about Kestrel vs IIS to see a whole matrix of feature differences. It goes more in depth about what Kestrel is and why you need both Kestrel & IIS.

One of the big advantages to using IIS is the process management. IIS will automatically start your app and potentially restart it if a crash were to occur. If you were running your ASP.NET Core app as a Windows Service or console app, you would not have that safety net there to start and monitor the process for you.

ASP.NET Core Identity Tables Customization With Visual Studio 2017

CheapASPNETHostingReview.com | Best and cheap ASP.NET Core 1.0 hosting. In this article, we will use Visual Studio 2017 and Entity Framework Core step by step to learn how we can:

Change Identity table names.
Change Identity table property names.
Change Identity table datatype of primary key.

When you decide to use ASP.NET Core Identity it will generate some tables used to store data for users and other things.

Prior to it, let’s take a brief definition about ASP.NET Core Identity.

Released on 2016 and from the name we can say it’s all about identity of the users, you can manage login and Logout functionality, create an account also you can use external login providers such as Facebook, Google, Microsoft Account and Twitter. In other words, you can say, it gives you the ability to make an authentication and an authorization.

Let us see it in action

Open your Visual Studio 2017

I am using an Enterprise edition but you can use any edition, which is available to you.

File > New > Project

Click ASP.NET Core Web Application and give it a name, as shown below.

Select Web Application.

Click Change authentication, select an individual user account and click OK, as shown below.

Now, we have an Application but we need to make migration and we have several ways to achieve it. We will use Package Manager, as shown below

Now, you need to create the database. Go to appsettings.json file and edit your connection string, if you want. I am using SQL Server 2016, so this is my appsettings.json file and it looks, as shown below.

{  
  "ConnectionStrings": {  
    "DefaultConnection": "Server=localhost;Database=aspnet-IdentityConfig;user id =sa;password=123456;MultipleActiveResultSets=true"  
  },  
  "Logging": {  
    "IncludeScopes": false,  
    "LogLevel": {  
      "Default": "Warning"  
    }  
  }  
}

{

"ConnectionStrings": {

"DefaultConnection": "Server=localhost;Database=aspnet-IdentityConfig;user id =sa;password=123456;MultipleActiveResultSets=true"

"Logging": {

"IncludeScopes": false,

"LogLevel": {

"Default": "Warning"

}

Now, in Package Manager console, write Add-migration command, followed by the name of this migration command like this and wait for some seconds.

Now, update the database and click enter.

Now, go to the database and refresh it. You will find aspnet-IdentityConfig database with some tables created by default like AspNetUsers table.

We will use this table to achieve our goal.

Now, how can we change this table name from AspNetUsers to AspUsers as example.

It’s database stuff, so we can achieve this from ApplicationDbContext class.

To be specific from OnModelCreating method into this class, we can customize our ASP.NET Identity model and override the defaults like change table name, property name and others.

We will change the table name now from AspNetUsers to AspUsers by this code inside OnModelCreating method. Proceed, as shown below.

    protected override void OnModelCreating(ModelBuilder builder)  
    {  
        base.OnModelCreating(builder);  
      
        builder.Entity&lt;ApplicationUser&gt;().ToTable("AspUsers");  
    }

protected override void OnModelCreating(ModelBuilder builder)

{

base.OnModelCreating(builder);

builder.Entity<ApplicationUser>().ToTable("AspUsers");

}

Note- After any customization in the tables, you should make database migration and update it to reflect the changes.

First, write add-migration. Subsequent to the migration, update the database.

Now, refresh the database and you will find the name changed to AspUsers.

Change Identity table property name

We need to change as an example Email to EmailAddress in AspUser table

It’s very similar to what we did before, just we will add the code to the OnModelCreating

builder.Entity&lt;ApplicationUser&gt;(b =&gt;  
{  
    b.Property(u =&gt; u.Email).HasColumnName("EmailAdress");  
});

builder.Entity<ApplicationUser>(b =>

{

b.Property(u => u.Email).HasColumnName("EmailAdress");

});

In this code we told entity to get Email property and change this column name to EmailAddress

Now you should make a migration to reflect your changes on Database and we will use it as usual

Add-Migration command then Update-Database

Now it’s time to look in the database

Change Identity table datatype of primary key

We will need to make some changes in ApplicationUser class so go to this class and open it

public class ApplicationUser : IdentityUser  
{  
}

public class ApplicationUser : IdentityUser

{

}

ApplicationUser class contains all the custom information I want to store about a user, also inheritance here from IdentityUser gives me all essentials like username ,id, password property or Email, that means if I want to add any property, I will add it here in ApplicationUser class

By default the primary key is string

Because IdentityUser has the primary key we want to pass our new primary key datatype.

Where will we pass this new datatype? Look to the picture below

As you can see we need to pass our primary key as example int datatype to IdentityUser<int> .

The code will look like this

public class ApplicationUser : IdentityUser&lt;int&gt;  
{  
}

public class ApplicationUser : IdentityUser<int>

{

}

And because every user has roles we will need to make this change in roles also by creating new class ApplicationRole which will inherit from IdentityRole class and pass the new datatype to it, and the code will look, as shown below.

public class ApplicationRole:IdentityRole&lt;int&gt;  
{  
}

public class ApplicationRole:IdentityRole<int>

{

}

Afterwards, we will make some change in our ApplicationDbContext class in order to open it.

public class ApplicationDbContext : IdentityDbContext&lt;ApplicationUser&gt;

1	public class ApplicationDbContext : IdentityDbContext<ApplicationUser>

We need to add our new role and datatype IdentityDbContext to the class. It will look, as shown below.

public class ApplicationDbContext : IdentityDbContext&lt;ApplicationUser,ApplicationRole,int&gt;

1	public class ApplicationDbContext : IdentityDbContext<ApplicationUser,ApplicationRole,int>

In the last step, we will need to reconfigure ConfigureServices method in the startup class.

We need to make some changes in these lines.

services.AddIdentity&lt;ApplicationUser, IdentityRole&gt;()  
    .AddEntityFrameworkStores&lt;ApplicationDbContext&gt;()  
    .AddDefaultTokenProviders();

services.AddIdentity<ApplicationUser, IdentityRole>()

.AddEntityFrameworkStores<ApplicationDbContext>()

.AddDefaultTokenProviders();

We need to replace IdentityRole class to our role ApplicationRole class and add our new datatype to AddEntityFrameworkStores<ApplicationDbContext,int>

The code will look, as shown below.

services.AddIdentity&lt;ApplicationUser, ApplicationRole&gt;()  
    .AddEntityFrameworkStores&lt;ApplicationDbContext,int&gt;()  
    .AddDefaultTokenProviders();

services.AddIdentity<ApplicationUser, ApplicationRole>()

.AddEntityFrameworkStores<ApplicationDbContext,int>()

.AddDefaultTokenProviders();

Now, we have all the required changes achieved but the last step will be the migration.

This time, we have some new things like when you run add-migration command; you will see the warning, as shown below.

When you try to run update-database, you will get an error told to you.

To change the IDENTITY property of a column, the column needs to be dropped and recreated.

Thus, we will drop the database and create it again.

Step 1

Drop the database command to remove the database and press Y.

Step 2

Remove all the migrations, which you have in Visual Studio.

Step 3

Run add-migration command.

Step 4

Run update-database command.

Now, go to the database to see our changes.

You see now that id has int datatype and not nvarchar.

Summary

Now, you can change an Identity column name, Identity table name, Identity primary key. I hope this is helpful to you.

TOP LIST Best ASP.NET Core 1.0 Hosting with Special Discount in 2017

CheapASPNETHostingReview.com | Best and cheap ASP.NET Core 1.0 hosting. we had come out a list of the best ASP.NET hosting, which are rated independently based on the ASP.NET frameworks, Microsoft control libraries, databases, Microsoft technical support, and web hosting price.

To choose the best ASP.NET hosting for your ASP.NET websites, we recommend you going with the best ASP.NET hosting as following. You won’t go wrong with them that all of the best ASP.NET hosting services have been truly tested by our ASP.NET developers.

Basic

Rank	1	2	3	4
Provider	ASPHostPortal	HostForLIFE	ASPHostCentral	UKWindowsHostASP
Rating	5.0 of 5	5.0 of 5	4.0 of 5	4.0 of 5
Customer	301 votes	186 votes	75 votes	100 votes
Regular	$4.49/mo 15% OFF	€3.49/Mo 15% OFF	$3.99/mo 35% OFF	£2.99/mo 35% OFF
Discount	$3.81/mo	€2.97/Mo	$2.59/mo	£1.95/mo

Basic

OS	2016 R2	2014 R2	2012 R2	2012 R2
Control Panel	Plesk	Plesk	Plesk	Plesk
Free Domain	No	No	No	No
Backup	Weekly	Daily	Weekly	Weekly
SSD	yes	yes	yes	–
Domain	–	Unlimited	–	50
Hosting Sites	Unlimited	–	Unlimited	–
Bandwidth	60 GB	Unlimited	50 GB	50 GB
Disk Space	5 GB	Unlimited	10 GB	5 GB
Shared SSL	Yes	Yes	Yes	Yes

Programming

ClassicASP	Yes	Yes	Yes	Yes
.NET Frameworks	2.0/3.5SP1/4.5/5/core	2.0/3.5SP1/4.0/4.5/5/core	2.0/3.5SP1/4.5/5/core	2.0/3.5SP1/4.5/5/core
ASP.NET MVC	2/3/4/5/6	1/2/3/4/5/6	2/3/4/5/6	2/3/4/5/6
Silverlight	4/5	4/5	4/5	4/5
SQL Server	2016	2016	2016	2016
MySQL	3	2	2	2
Remote IIS	Yes	Yes	No	Yes
Trust Level	Full	Full	Full	Full
Dedicated App Pool	Yes	Yes	Yes	Yes
WebMatrix	Yes	Yes	Yes	Yes
URLRewrite	Yes	Yes	Yes	Yes
GZip	–	–	–	–
Schedule Jobs	Yes	Yes	Yes	Yes

Support

Service Level	Professional	Professional	Professional	Professional
24×7 Support	Yes	Yes	Yes	Yes
Full trust	Yes	Yes	Yes	Yes
Email	Yes	Yes	Yes	Yes

The Best ASP.NET Core 1.0 Hosting in 2017

ASPHostPortal is a web hosting provider known for its professional ASP.NET hosting plans which are able to meet the demands of nearly all-sized businesses. Over the past 10 years since its reception, ASPHostportal has gained respect from both the developer and business communities.

The ASPHostportal ASP.NET hosting packages all comes with ASP.NET v2/v3.5/v4.6, ASP.NET core 1.0 and supports most versions of the frameworks including MVC, LINQ, AJAX and Silverlight. Also, they allow Full Trust to make sure that ASP.NET websites can run perfectly without the bother of the codes that cannot run. Right now, using this exclusive coupon link for checking out, the Basic hosting plan is $3.81/mo only, 15% off $4.49/mo you get originally.

The customers’ hosting experience is guaranteed by ASPHostportal excellent technical support team which is very helpful, knowledgeable and responsive to phone calls, emails and live chat. In addition, they offer every account with 30 days full money back and anytime post-rate money back guarantee. That makes customers’ ASP.NET hosting risk-free.

ASPHostPortal Statistik Review

To learn more about ASPHostPortal, visit http://asphostportal.com

Why They’re the Best ASP.NET Core 1.0 Hosting

The following 5 checkpoints are main criterias on rating ASP.NET web hosting besides the consideration on the generic Windows web hosting features.

Windows OS: the latest version of Windows OS is the key point of a quality ASP.NET hosting solution. And now, the best choices are Windows Server 2012R2, Windows Server 2012 and Windows Server 2008R2. In fact, all the recommended hosting companies support the mentioned Windows operating systems.
ASP.NET Frameworks: as ASP.NET websites have to run in the corresponding .NET framework, it’s better that the web host can support most of frameworks from v1.1 to v4.0. In this case that you can have maximum flexibility for you websites and keep the possibility upgrading to the higher version.
ASP.NET Trust Level: it’s configured for each website by .net infrastructure. you should know the exact configuration before the payment. in our research, 70% websites can be run only under the fully trust level. if your hosting company doesn’t tell that they support fully trust, you should be careful that your website may not run correctly in the host finally. surely, you can ask for money back but it’s time wasting.
RAM: this is the maximum memory in the server that can be used for your site, which is configured in IIS application pool. Only sufficient RAM allocation can bring the website a reliable hosting condition.
MSSQL Edition: MSSQL makes a big difference to store all data from the website, which is a Windows based database. Note that, the latest version of MSSQL is the SQL Server 2012.
Control Panel: Plesk is the best reliable control panel for asp.net web hostingl and easy-to-use.
Add-on Features: the installation required third party libraries are important when your website depends on then. E.G. Chat controls library, Altas library and more.
knowledge of Microsoft technology support: you can easily call the technical support of the web host and ask some technical questions about ASP.NET website configuration and deployment. This is certainly important especially when you have a problem in the future.

Tips for Building an API in ASP.NET Core

CheapASPNETHostingReview.com | Best and cheap ASP.NET Core 1.0 hosting. These days users expect a fluid, app-like experience on the internet. Thus, the new web is being built with APIs and single-page frontends. This means it’s more important that ever to build APIs that are easy to use, reliable, and scalable. ASP.NET Core makes it easy to build great APIs, but there are a few tips we’ve picked up that can help make your APIs even stronger and more scalable.

1. Set the Default Route for ASP.NET Core MVC

A lot of programmers who start using ASP.NET Core just use the default app.UseMvc(); line in the Configure method of Startup.cs. There are options that you can pass to the UseMvc function, like setting the default routes, which is one of the most overlooked:

app.UseMvc(routes =&gt;
{
    routes.MapRoute(name: "default",
                    template: "api/{controller=Default}/{action=Get}/{id?}");
});

app.UseMvc(routes =>

{

routes.MapRoute(name: "default",

});

This will set the root route of your API to: http://www.mycompany.com/api to call the DefaultController’s Get method.

What this does for you (aside from the obvious) is it sets the tone for a decent RESTful API. It also makes changes to URL strategy easier, including versioning the API in the URL easy to do if you set the URL strategy in one place.

2. Return `IActionResult` from .NET Core Controller Methods

Returning IActionResult from your controller methods affords the ability to take advantage of some of the helper methods and classes to ease returning proper HTTP results. The Ok method on the ControllerBase class will return an OkObjectResult that implements IActionResult and returns a 200 OK HTTP message to the caller. The NotFound method returns an object that sends a 404 NOT FOUND HTTP message.

There are quite a few others, but another extremely helpful one is the CreatedAtAction class that returns not only a 201 CREATED HTTP result but adds a header Location with the URL to access the newly created resource.

3. Use the .NET Async Pattern

Network calls by their very nature are asynchronous. It makes the most sense to create async controller methods that extend that asynchronicity when the controllers need to make database and external API calls.

The fact is, asynchronous support in .NET Core and the supporting libraries is very good these days. Using and creating asynchronous code is easy using async/await and libraries that support the Task pattern. The benefit is more simultaneous requests handled with the same hardware requirements.

Asynchronous code just performs better, and since it is so easy to create, why not do it?

4. Use .NET Attributes

Using attributes to decorate routes helps you to take advantage of some of the power of MVC. This may seem counterintuitive since I just told you to use the default routes. Decorating your methods and controller classes with just enough decoration for that class or method can help you take advantage of things like the CreatedAtAction.

You can also use attributes to help the JSON serializer do its job. You can use the NullValueHandling attribute to tell the serializer that when the value of a property is null, not to even serialize the property. You can change the property name that gets serialized so that you can stick with an internal coding standard and still return standard JSON names (like changing ‘MaxTitleLength’ to ‘maxLength’ when serialized). You can even set the order that properties are serialized so that more important properties are serialized first in the JSON documents.

5. Use Async Result Filters

Using Async Result Filters, you can shape the data in the last moments before it goes back to the caller. Usually, you’d add the properties you want (the way you want them) via an anonymous object. There are two problems with that approach, the first is that you need to do a lot of copying of properties and it violates the single responsibility principle. You could use AutoMapper to combat this property copying, but it doesn’t solve the second problem, which is adding new properties (like hypermedia).

Solution: An Async Result Filter will solve both problems and give you a cleaner, more maintainable code base.

BONUS: Try This Workaround to Improve Serialization of Self-Referencing Object Graphs

One of the problems with traditional .NET Web API serialization, is that it doesn’t handle self-referencing object graphs very well. The fact is, in good object-oriented objects there may actually be some reference loops, so it’s important to handle them gracefully.

In your ConfigureServices method of Startup.cs, change your MVC line from:

services.AddMvc();

1	services.AddMvc();

to :

services.AddMvc().AddJsonOptions(options =&gt; 
{
    options.SerializerSettings.ReferenceLoopHandling = Newtonsoft.Json.ReferenceLoopHandling.Ignore;
});

services.AddMvc().AddJsonOptions(options =>

{

options.SerializerSettings.ReferenceLoopHandling = Newtonsoft.Json.ReferenceLoopHandling.Ignore;

});

In .NET 4.x a reference loop would cause an error. Once the serializer realized that serializing the object graph would cause a reference loop, it would fail and just send a 500 error. However, in .NET Core without the above JSON options added, the serializer serializes the object until it hits a reference loop and simply sends what has been serialized so far, ignoring the rest of the object, even if it could serialize the rest of the object graph easily.

What this line adds is, it tells the JSON serializer to ignore reference loops and continue serializing the rest of the graph. So far, this is just a workaround for the issue. It’s not perfect, but it’s better than just a failure.

The best way to handle this problem is to simply not have the problem. Normally, we would put these objects into DTOs that are not self-referencing and remove the problem altogether.

How To Authentication in ASP.NET Core for your Web API and Angular2

CheapASPNETHostingReview.com | Best and cheap ASP.NET Core 1.0 hosting. In this post we will talking about Authentication in ASP.NET for web API and Angular. Authentication in a single page application is a bit more special, if you just know the traditional ASP.NET way. To imagine that the app is a completely independent app like a mobile app helps. Token based authentication is the best solution for this kind of apps. In this post I’m going to try to describe a high level overview and to show a simple solution.

There are many ways to protect your application out there. The simplest one is using an Azure Active Directory. You could also setup a separate authentication server, using IdentityServer4, to manage the users, roles and to provide a token based authentication.

And that’s the key word: A Token Based Authentication is the solution for that case.

With the token bases authentication, the client (the web client, the mobile app, and so on) gets a string based encrypted token after a successful log-in. The token also contains some user info and an info about how long the token will be valid. This token needs to be stored on the client side and needs to be submitted to the server every time you request a resource. Usually you use a HTTP header to submit that token. If the token is not longer valid you need to perform a new log-in.

In one of our smaller projects, didn’t set-up a different authentication server and we didn’t use Azure AD, because we needed a fast and cheap solution. Cheap from the customers perspective.

The Angular2 part

On the client side we used angular2-jwt, which is a Angular2 module that handles authentication tokens. It checks the validity, reads meta information out of it and so on. It also provides a wrapper around the Angular2 HTTP service. With this wrapper you are able to automatically pass that token via a HTTP header back to the server on every single request.

The work flow is like this.

If the token is not valid or doesn’t exist on the client, the user gets redirected to the log-in route
The user enters his credentials and presses the log-in button
The date gets posted to the server where a special middle-ware handles that request
1. The user gets authenticated on the server side
2. The token, including a validation date and some meta date, gets created
3. The token gets returned back to the client
the client stores the token in the local storage, cookie or whatever, to use it on every new request.

The angular2-jwt does the most magic on the client for us. We just need to use it, to check the availability and the validity, every time we want to do a request to the server or every time we change the view.

This is a small example about how the HTTP wrapper is used in Angular2:

import { AuthHttp, AuthConfig, AUTH_PROVIDERS } from 'angular2-jwt';

...

class App {

  thing: string;

  constructor(public authHttp: AuthHttp) {}

  getThing() {
    // this uses authHttp, instead of http
    this.authHttp.get('http://example.com/api/thing')
      .subscribe(
        data =&gt; this.thing = data,
        err =&gt; console.log(err),
        () =&gt; console.log('Request Complete')
      );
  }
}

import { AuthHttp, AuthConfig, AUTH_PROVIDERS } from 'angular2-jwt';

...

class App {

thing: string;

constructor(public authHttp: AuthHttp) {}

getThing() {

// this uses authHttp, instead of http

this.authHttp.get('http://example.com/api/thing')

.subscribe(

data => this.thing = data,

err => console.log(err),

() => console.log('Request Complete')

);

}

The ASP.NET part

On the server side we also use a, separate open source project, called SimpleTokenProvider. This is really a pretty simple solution to authenticate the users, using his credentials and to create and provide the token. I would not recommend to use this way in a huge and critical solution, in that case you should choose the IdentiyServer or any other authentication like Azure AD to be more secure. The sources of that project need to be copied into your project and you possibly need to change some lines e. g. to authenticate the users against your database, or whatever you use to store the user data. This project provides a middle-ware, which is listening on a defined path, like /api/tokenauth/. This URL is called with a POST request by the log-in view of the client application.

The authentication for the web API, is just using the token, sent with the current request. This is simply done with the built-in IdentiyMiddleware. That means, if ASP.NET MVC gets a request to a Controller or an Action with an AuthorizeAttribute, it checks the request for incoming Tokens. If the Token is valid, the user is authenticated. If the user is also in the right role, he gets authorized.

We put the users role information as additional claims into the Token, so this information can be extracted out of that token and can be used in the application.

To find the users and to identify the user, we use the given UserManager and SignInManager. These managers are bound to the IdentityDataContext. This classes are already available, when you create a new project with Identiy in Visual Studio.

This way we can authenticate a user on the server side:

public async Task&lt;ClaimsIdentity&gt; GetIdentity(string email, string password)
{
    var result = await _signInManager.PasswordSignInAsync(email, password, false, lockoutOnFailure: false);
    if (result.Succeeded)
    {
        var user = await _userManager.FindByEmailAsync(email);
        var claims = await _userManager.GetClaimsAsync(user);

        return new ClaimsIdentity(new GenericIdentity(email, "Token"), claims);
    }

    // Credentials are invalid, or account doesn't exist
    return null;
}

public async Task<ClaimsIdentity> GetIdentity(string email, string password)

{

var result = await _signInManager.PasswordSignInAsync(email, password, false, lockoutOnFailure: false);

if (result.Succeeded)

{

var user = await _userManager.FindByEmailAsync(email);

var claims = await _userManager.GetClaimsAsync(user);

return new ClaimsIdentity(new GenericIdentity(email, "Token"), claims);

}

// Credentials are invalid, or account doesn't exist

return null;

}

And this claims will be used to create the Jwt-Token in the TokenAuthentication middle-ware:

var username = context.Request.Form["username"];
var password = context.Request.Form["password"];

var identity = await identityResolver.GetIdentity(username, password);
if (identity == null)
{
    context.Response.StatusCode = 400;
    await context.Response.WriteAsync("Unknown username or password.");
    return;
}

var now = DateTime.UtcNow;

// Specifically add the jti (nonce), iat (issued timestamp), and sub (subject/user) claims.
// You can add other claims here, if you want:
var claims = new[]
{
    new Claim(JwtRegisteredClaimNames.Sub, username),
    new Claim(JwtRegisteredClaimNames.Jti, await _options.NonceGenerator()),
    new Claim(JwtRegisteredClaimNames.Iat, ToUnixEpochDate(now).ToString(), ClaimValueTypes.Integer64)
};

// Create the JWT and write it to a string
var jwt = new JwtSecurityToken(
    issuer: _options.Issuer,
    audience: _options.Audience,
    claims: claims,
    notBefore: now,
    expires: now.Add(_options.Expiration),
    signingCredentials: _options.SigningCredentials);
var encodedJwt = new JwtSecurityTokenHandler().WriteToken(jwt);

var response = new
{
    access_token = encodedJwt,
    expires_in = (int)_options.Expiration.TotalSeconds,
    admin = identity.IsAdministrator(),
    fullname = identity.FullName(),
    username = identity.Name
};

// Serialize and return the response
context.Response.ContentType = "application/json";
await context.Response.WriteAsync(JsonConvert.SerializeObject(response, _serializerSettings));

var username = context.Request.Form["username"];

var password = context.Request.Form["password"];

var identity = await identityResolver.GetIdentity(username, password);

if (identity == null)

{

context.Response.StatusCode = 400;

await context.Response.WriteAsync("Unknown username or password.");

return;

}

var now = DateTime.UtcNow;

// Specifically add the jti (nonce), iat (issued timestamp), and sub (subject/user) claims.

// You can add other claims here, if you want:

var claims = new[]

{

new Claim(JwtRegisteredClaimNames.Sub, username),

new Claim(JwtRegisteredClaimNames.Jti, await _options.NonceGenerator()),

new Claim(JwtRegisteredClaimNames.Iat, ToUnixEpochDate(now).ToString(), ClaimValueTypes.Integer64)

};

// Create the JWT and write it to a string

var jwt = new JwtSecurityToken(

issuer: _options.Issuer,

audience: _options.Audience,

claims: claims,

notBefore: now,

expires: now.Add(_options.Expiration),

signingCredentials: _options.SigningCredentials);

var encodedJwt = new JwtSecurityTokenHandler().WriteToken(jwt);

var response = new

{

access_token = encodedJwt,

expires_in = (int)_options.Expiration.TotalSeconds,

admin = identity.IsAdministrator(),

fullname = identity.FullName(),

username = identity.Name

};

// Serialize and return the response

context.Response.ContentType = "application/json";

await context.Response.WriteAsync(JsonConvert.SerializeObject(response, _serializerSettings));

This code will not work, if you copy and past it in your application, but shows you what needs to be done to create a token and how the token is created and sent to the client.

Billig Core ASP.NET 1.0 Hosting in Europa mit 15% Rabatt

CheapASPNETHostingReview.com | Beste und billig Core ASP.NET 1.0 Hosting in Europa. Sind Sie auf der Suche nach den besten Kern von ASP.NET 1.0 Hosting oder das Beste Windows Hosting? Ihre beste ASP.NET Core 1.0 Web Hosting Suche ist vorbei! Sparen Sie Zeit und Geld für die besten Windows Hosting Für finden Sie in unserer Top Core ASP.NET 1.0 Hosting Unternehmen mit großen Förderung empfohlene Liste!

Big Deal 15% RABATT billig Core ASP.NET 1.0 Hosting in Europa

HostForLIFE.eu

HostForLIFE wurde als eine der besten asp.net ERKANNT Für Menschen, die mit den Leistungen unzufrieden sind, HostForLIFE bietet eine 30 Tage Geld-zurück-Garantie, so dass die Kunden ihre Konten innerhalb der ersten 30 Tagen zu stornieren und erhalten eine volle Rückerstattung. Wenn es um die Zahlung, zwei Zahlungsmethoden sind verfügbar, einschließlich CC und PayPal, um sicherzustellen, dass jeder Kunde die Dienste auf eine bequeme Weise erreicht.

Empfehlung: Wir empfehlen Ihnen dringend, Ihre asp.net Website oder Anwendung auf Hostforlife.eu Web Hosting zu bewirten. Diese Webseite ist auch gehostet mit HostForLIFE und wir sind sicher, müssen Sie die Geschwindigkeit bemerkt haben. Sie können auch die Vorteile der speziellen Hostforlife’s Angebot und können günstige Asp.net (Windows) Hosting mit unbegrenzte Bandbreite kaufen.

Günstigen Preis für eine Lösung mit hoher Verfügbarkeit

Auf Enterprise-Hardware

24/7/365 Kunden Betreuung und Unterstützung

99,9&Uptime Garantie

Spezielle App Pool

Amsterdam (NL) , London (United Kingdom), Paris (France), Frankfurt (DE) and Seattle (USA) Data Center

Warum diese Hosts bieten ASP.NET Hosting für unbegrenzte

Gut, das ist eine berechtigte Frage. Viele Leute fragen, warum Web Hosting Provider mit unbegrenzten ASP.NET Hosting. Alle Hosts, die billig und Unlimited Web Hosting, um Ihnen zu helfen, Ihre Anwendung auf IT-Test anbieten und wenn Sie zufrieden sind können Sie Ihr Paket auf eine höhere Ebene aktualisieren können. Einige andere will Studenten zu helfen, damit sie ihre Anwendungen entwickeln und testen.

Unlimitations und Einschränkungen der billigen ASP.NET

die meisten Hosting Pakete hosting Pläne kommen mit sehr wenig Speicherplatz und eine begrenzte Bandbreite. Wenn Sie planen, für sie ihr Geschäft Web site oder ein hoher Verkehr Website diese Pläne sind nicht geeignet, weil sie unbegrenzte Anzahl an Domains, Speicherplatz erhalten können auch die Bandbreite.

Top 10 Gründe, mit unseren Top ASP.NET Core 1.0 Hosting Provider Empfehlung auf Host:

.NET Hosting Services von cheapaspnethostingreview.com
Microsoft-recognized .net Hosting Unternehmen
preisgekrönte .NET HOSTING Lösungen
Neueste getestet. NET Hosting Technologien
Beste .NET Hosting Preise
starken Kunden Testimonials
24×7 Telefon- & E-Mail-Support
99,9% Uptime Garantie
Geld-zurück-Garantie

ASP.NET Hosting Anforderungen

Windows Hosting Unternehmen die aktuellste unterstützen sollte. NET-Technologien und die aktuellsten Versionen. Stellen Sie sicher, dass, wenn Sie ASP.NET 4.6 hosting Core/benötigen, IIS 8, MVC 6, MS SQL 2016 Ihr Gastgeber unterstützen Sie. Auch wenn Sie nicht die neuesten Versionen fragen Sie sich, wenn Sie sie in der nahen Zukunft verwenden werden? Auch die Art und Weise Sie ihrer Datenbank Server aufbauen konnte und Website Bereitstellung prüfen. Die meisten der besten ASP.NET Hosts unterstützen die neuesten und innovativen .NET hosting Technologien.

Nutzen Sie die leistungsstarken, on-demand .NET Hosting die Leistung Ihrer IT-Infrastruktur zu steigern. Mehrere Web hosting Pläne zur Verfügung stehen, so dass Sie die nötige Flexibilität, um die Services je nach Ihren Bedürfnissen anpassen. Verlassen Sie sich auf Windows Web Hosting schnell zu skalieren und die Bereitstellung von IT-Ressourcen, wenn Sie sie benötigen, und zahlen für die Ressourcen, die Sie nutzen. Die .NET Web Hosting erhalten Kunden eine zuverlässige Leistung und Kundendienst zu einem erschwinglichen Preis.

How To Using Sessions and HttpContext in ASP.NET Core and MVC Core

CheapASPNETHostingReview.com | Best and cheap ASP.NET core 1.0 hosting. If you’re new to ASP.NET Core or MVC Core, you’ll find that sessions don’t work the way they used to. Here’s how to get up and running the new way.

Add Session NuGet Package

Add the Microsoft.AspNetCore.Session NuGet package to your project.

VERSION WARNING: As you’ll find with most Microsoft.* packages, you should make sure the versions all match. At RTM time as of writing, this means “1.0.0”.

Update startup.cs

Now that we have the Session nuget package installed, we can add sessions to the ASP.NET Core pipeline.

Open up startup.cs and add the AddSession() and AddDistributedMemoryCache() lines to the ConfigureServices(IServiceCollection services)

// Add MVC services to the services container.
services.AddMvc();
services.AddDistributedMemoryCache(); // Adds a default in-memory implementation of IDistributedCache
services.AddSession();

// Add MVC services to the services container.

services.AddMvc();

services.AddDistributedMemoryCache(); // Adds a default in-memory implementation of IDistributedCache

services.AddSession();

Next, we’ll tell ASP.NET Core to use a Memory Cache to store the session data. Add the UseSession() call below to the Configure(IApplicationBulider app, ...)

// IMPORTANT: This session call MUST go before UseMvc()
app.UseSession();

// Add MVC to the request pipeline.
app.UseMvc(routes =&gt;
{
    routes.MapRoute(
        name: "default",
        template: "{controller=Home}/{action=Index}/{id?}");
});

// IMPORTANT: This session call MUST go before UseMvc()

app.UseSession();

// Add MVC to the request pipeline.

app.UseMvc(routes =>

{

routes.MapRoute(

});

Where’s the Session variable gone?

Relax it’s still there, just not where you think it is. You can now find the session object by using HttpContext.Session. HttpContext is just the current HttpContext exposed to you by the Controller class.

If you’re not in a controller, you can still access the HttpContext by injecting IHttpContextAccessor.

Let’s go ahead and add sessions to our Home Controller:

using Microsoft.AspNetCore.Http; // Needed for the SetString and GetString extension methods

public class HomeController : Controller
{
    public IActionResult Index()
    { 
        HttpContext.Session.SetString("Test", "Ben Rules!");
        return View();
    }

    public IActionResult About()
    {
        ViewBag.Message = HttpContext.Session.GetString("Test");

        return View();
    }
}

using Microsoft.AspNetCore.Http; // Needed for the SetString and GetString extension methods

public class HomeController : Controller

{

public IActionResult Index()

{

HttpContext.Session.SetString("Test", "Ben Rules!");

return View();

}

public IActionResult About()

{

ViewBag.Message = HttpContext.Session.GetString("Test");

return View();

}

You’ll see the Index() and About() methods making use of the Session object. It’s pretty easy here, just use one of the Set() methods to store your data and one of the Get() methods to retrieve it.

Just for fun, let’s inject the context into a random class:

public class SomeOtherClass
{
    private readonly IHttpContextAccessor _httpContextAccessor;
    private ISession _session =&gt; _httpContextAccessor.HttpContext.Session;

    public SomeOtherClass(IHttpContextAccessor httpContextAccessor)
    {
        _httpContextAccessor = httpContextAccessor;
    }

    public void TestSet()
    {
        _session.SetString("Test", "Ben Rules!");
    }

    public void TestGet()
    {
        var message = _session.GetString("Test");
    }
}

public class SomeOtherClass

{

private readonly IHttpContextAccessor _httpContextAccessor;

private ISession _session => _httpContextAccessor.HttpContext.Session;

public SomeOtherClass(IHttpContextAccessor httpContextAccessor)

{

_httpContextAccessor = httpContextAccessor;

}

public void TestSet()

{

_session.SetString("Test", "Ben Rules!");

}

public void TestGet()

{

var message = _session.GetString("Test");

}

Let’s break this down.

Firstly I’m setting up a private variable to hold the HttpContextAccessor. This is the way you get the HttpContext now.

Next I’m adding a convenience variable as a shortcut directly to the session. Notice the =>? That means we’re using an expression body, aka a shortcut to writing a one liner method that returns something.

Moving to the contructor you can see that I’m injecting the IHttpContextAccessor and assigning it to my private variable. If you’re not sure about this whole dependency injection thing, don’t worry, it’s not hard to get the hang of (especially constructor injection like I’m using here) and it will improve your code by forcing you to write it in a modular way.

But wait a minute, how do I store a complex object?

How do I store a complex object?

I’ve got you covered here too. Here’s a quick JSON storage extension to let you store complex objects nice and simple

public static class SessionExtensions
{
    public static void SetObjectAsJson(this ISession session, string key, object value)
    {
        session.SetString(key, JsonConvert.SerializeObject(value));
    }

    public static T GetObjectFromJson&lt;T&gt;(this ISession session, string key)
    {
        var value = session.GetString(key);

        return value == null ? default(T) : JsonConvert.DeserializeObject&lt;T&gt;(value);
    }
}

public static class SessionExtensions

{

public static void SetObjectAsJson(this ISession session, string key, object value)

{

session.SetString(key, JsonConvert.SerializeObject(value));

}

public static T GetObjectFromJson<T>(this ISession session, string key)

{

var value = session.GetString(key);

return value == null ? default(T) : JsonConvert.DeserializeObject<T>(value);

}

Now you can store your complex objects like so:

var myComplexObject = new MyClass();
HttpContext.Session.SetObjectAsJson("Test", myComplexObject);

1 2	var myComplexObject = new MyClass(); HttpContext.Session.SetObjectAsJson("Test", myComplexObject);

and retrieve them just as easily:

var myComplexObject = HttpContext.Session.GetObjectFromJson&lt;MyClass&gt;("Test");

1	var myComplexObject = HttpContext.Session.GetObjectFromJson<MyClass>("Test");

Use a Redis or SQL Server Cache instead

Instead of using services.AddDistributedMemoryCache() which implements the default in-memory cache, you can use either of the following.

SQL Server
Firstly, install this nuget package:

"Microsoft.Extensions.Caching.SqlServer": "1.0.0"

Secondly, add the appropriate code snippet below:

// Microsoft SQL Server implementation of IDistributedCache.
// Note that this would require setting up the session state database.
services.AddSqlServerCache(o =&gt;
{
	o.ConnectionString = "Server=.;Database=ASPNET5SessionState;Trusted_Connection=True;";
	o.SchemaName = "dbo";
	o.TableName = "Sessions";
});

// Microsoft SQL Server implementation of IDistributedCache.

// Note that this would require setting up the session state database.

services.AddSqlServerCache(o =>

{

o.ConnectionString = "Server=.;Database=ASPNET5SessionState;Trusted_Connection=True;";

o.SchemaName = "dbo";

o.TableName = "Sessions";

});

Redis Cache
Unfortunately, the redis package does not support netcoreapp1.0 at the moment. You can still use this if you’re using net451 or higher.

"Microsoft.Extensions.Caching.Redis": "1.0.0"

// Redis implementation of IDistributedCache.
// This will override any previously registered IDistributedCache service.
services.AddSingleton&lt;IDistributedCache, RedisCache&gt;();

// Redis implementation of IDistributedCache.

// This will override any previously registered IDistributedCache service.

services.AddSingleton<IDistributedCache, RedisCache>();

Stay up to date

Even though we’ve reached RTM, you should still keep an eye on the ASP.NET Session Repository for any changes.

About Bundling and Minification in ASP.NET Core

CheapASPNETHostingReview.com | Best and cheap ASP.NET Core 1.0 hosting. This post is about Bundling and Minification in ASP.NET Core. Bundling and minification are two techniques you can use in ASP.NET to improve page load performance for your web application. Bundling combines multiple files into a single file. Minification performs a variety of different code optimizations to scripts and CSS, which results in smaller payloads. In ASP.NET Core RTM release Microsoft introduced “BundlerMinifier.Core” tool which will help you to bundle and minimize Javascript and style sheet files. Unlike previous versions MVC, the bundling and minification is happening on development time not in runtime. To use “BundlerMinifier.Core” first you need to add reference of BundlerMinifier.Core in the project.json tools section.

"tools": {
  "BundlerMinifier.Core": "2.0.238",
  "Microsoft.AspNetCore.Razor.Tools": "1.0.0-preview2-final",
  "Microsoft.AspNetCore.Server.IISIntegration.Tools": "1.0.0-preview2-final"
}

"tools": {

"BundlerMinifier.Core": "2.0.238",

"Microsoft.AspNetCore.Razor.Tools": "1.0.0-preview2-final",

"Microsoft.AspNetCore.Server.IISIntegration.Tools": "1.0.0-preview2-final"

}

Now you need to specify the Javascript and stylesheet files for bundling and minification. You can do this by adding “bundleconfig.json” file. The name can be changed, but if the filename is bundleconfig.json, it will bundle command will take it automatically. Here is a minimal bundleconfig.json file.

[
  {
    "outputFileName": "wwwroot/css/site.min.css",
    "inputFiles": [
      "wwwroot/css/site.css"
    ]
  },
  {
    "outputFileName": "wwwroot/js/site.min.js",
    "inputFiles": [
      "wwwroot/js/site.js"
    ],
    "minify": {
      "enabled": true,
      "renameLocals": true
    },
    "sourceMap": false
  },
  {
    "outputFileName": "wwwroot/js/semantic.validation.min.js",
    "inputFiles": [
      "wwwroot/js/semantic.validation.js"
    ],
    "minify": {
      "enabled": true,
      "renameLocals": true
    }
  }
]

[

{

"outputFileName": "wwwroot/css/site.min.css",

"inputFiles": [

"wwwroot/css/site.css"

]

{

"outputFileName": "wwwroot/js/site.min.js",

"inputFiles": [

"wwwroot/js/site.js"

"minify": {

"enabled": true,

"renameLocals": true

"sourceMap": false

{

"outputFileName": "wwwroot/js/semantic.validation.min.js",

"inputFiles": [

"wwwroot/js/semantic.validation.js"

"minify": {

"enabled": true,

"renameLocals": true

}

]

The file is self explantory, you can specify multiple file in the inputFiles element, which will be combined and minified based on the minify element. Now you can combine and minify using “dotnet bundle” command. Here is the output when I run the dotnet bundle command on my MVC project.

You can integrate it to the development lifecycle by adding the dotnet build command in the “precompile” script section in project.json file. If you are using Yo ASP.NET generator, the project template will be using precompile script section in project.json.

"scripts": {
  "precompile": [
    "dotnet bundle"
  ],
  "prepublish": [
    "bower install"
  ],
  "postpublish": [
    "dotnet publish-iis --publish-folder %publish:OutputPath% --framework %publish:FullTargetFramework%"
  ]
}

"scripts": {

"precompile": [

"dotnet bundle"

"prepublish": [

"bower install"

"postpublish": [

"dotnet publish-iis --publish-folder %publish:OutputPath% --framework %publish:FullTargetFramework%"

]

}

There are few more commands also available with dotnet bundle tool.

dotnet bundle clean – Executing dotnet bundle clean will delete all output files from disk.
dotnet bundle watch – To automatically run the bundler when input files change, call dotnet bundle watch. This will monitor any file changes to input files in the working directory and execute the bundler automatically.
dotnet bundle help – Get help on how to use the CLI.

Happy Programming 🙂

Claim NOW Big Promotion From ASPHostPortal.com

How To Handling Error in ASP.NET Core

CheapASPNETHostingReview.com | Best and cheap ASP.NET Core 1.0 hosting. When errors occur in your ASP.NET Core app, you can handle them in a variety of ways, as described in this article.

The developer exception page

To configure an app to display a page that shows detailed information about exceptions, install the Microsoft.AspNetCore.Diagnostics NuGet package and add a line to the Configure method in the Startup class:

public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
{
    loggerFactory.AddConsole();
    env.EnvironmentName = EnvironmentName.Production;
    if (env.IsDevelopment())
    {
        app.UseDeveloperExceptionPage();
    }
    else
    {
        app.UseExceptionHandler("/error");
    }

public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)

{

loggerFactory.AddConsole();

env.EnvironmentName = EnvironmentName.Production;

if (env.IsDevelopment())

{

app.UseDeveloperExceptionPage();

}

else

{

app.UseExceptionHandler("/error");

}

Put UseDeveloperExceptionPage before any middleware you want to catch exceptions in, such as app.UseMvc.

Warning [wp-svg-icons icon=”warning” wrap=”i”]

Enable the developer exception page only when the app is running in the Development environment. You don’t want to share detailed exception information publicly when the app runs in production

To see the developer exception page, run the sample application with the environment set to Development, and add ?throw=true to the base URL of the app. The page includes several tabs with information about the exception and the request. The first tab includes a stack trace.

The next tab shows the query string parameters, if any.

This request didn’t have any cookies, but if it did, they would appear on the Cookies tab. You can see the headers that were passed in the last tab.

Configuring a custom exception handling page

It’s a good idea to configure an exception handler page to use when the app is not running in the Development environment.

public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
{
    loggerFactory.AddConsole();
    env.EnvironmentName = EnvironmentName.Production;
    if (env.IsDevelopment())
    {
        app.UseDeveloperExceptionPage();
    }
    else
    {
        app.UseExceptionHandler("/error");
    }

public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)

{

loggerFactory.AddConsole();

env.EnvironmentName = EnvironmentName.Production;

if (env.IsDevelopment())

{

app.UseDeveloperExceptionPage();

}

else

{

app.UseExceptionHandler("/error");

}

In an MVC app, don’t explicitly decorate the error handler action method with HTTP method attributes, such as HttpGet. Using explicit verbs could prevent some requests from reaching the method.

[Route("/Error")]
public IActionResult Index()
{
    // Handle error here
}

[Route("/Error")]

public IActionResult Index()

{

// Handle error here

}

Configuring status code pages

By default, your app will not provide a rich status code page for HTTP status codes such as 500 (Internal Server Error) or 404 (Not Found). You can configure the StatusCodePagesMiddleware by adding a line to the Configure method :

app.UseStatusCodePages();

1	app.UseStatusCodePages();

By default, this middleware adds simple, text-only handlers for common status codes, such as 404:+

The middleware supports several different extension methods. One takes a lambda expression, another takes a content type and format string.

app.UseStatusCodePages(async context =&gt;
{
    context.HttpContext.Response.ContentType = "text/plain";
    await context.HttpContext.Response.WriteAsync(
        "Status code page, status code: " + 
        context.HttpContext.Response.StatusCode);
});
<!--?prettify linenums=true?-->

app.UseStatusCodePages(async context =>

{

context.HttpContext.Response.ContentType = "text/plain";

await context.HttpContext.Response.WriteAsync(

"Status code page, status code: " +

context.HttpContext.Response.StatusCode);

});

app.UseStatusCodePages("text/plain", "Status code page, status code: {0}");

1	app.UseStatusCodePages("text/plain", "Status code page, status code: {0}");

There are also redirect extension methods. One sends a 302 status code to the client, and one returns the original status code to the client but also executes the handler for the redirect URL.

app.UseStatusCodePagesWithRedirects("/error/{0}");
<!--?prettify linenums=true?-->

1 2	app.UseStatusCodePagesWithRedirects("/error/{0}"); <!--?prettify linenums=true?-->

app.UseStatusCodePagesWithReExecute("/error/{0}");

1	app.UseStatusCodePagesWithReExecute("/error/{0}");

If you need to disable status code pages for certain requests, you can do so:

var statusCodePagesFeature = context.Features.Get&lt;IStatusCodePagesFeature&gt;();
if (statusCodePagesFeature != null)
{
  statusCodePagesFeature.Enabled = false;
}

var statusCodePagesFeature = context.Features.Get<IStatusCodePagesFeature>();

if (statusCodePagesFeature != null)

{

statusCodePagesFeature.Enabled = false;

}

Exception-handling code

Code in exception handling pages can throw exceptions. It’s often a good idea for production error pages to consist of purely static content.

Also, be aware that once the headers for a response have been sent, you can’t change the response’s status code, nor can any exception pages or handlers run. The response must be completed or the connection aborted.

Server exception handling

In addition to the exception handling logic in your app, the server hosting your app will perform some exception handling. If the server catches an exception before the headers have been sent it sends a 500 Internal Server Error response with no body. If it catches an exception after the headers have been sent, it closes the connection. Requests that are not handled by your app will be handled by the server, and any exception that occurs will be handled by the server’s exception handling. Any custom error pages or exception handling middleware or filters you have configured for your app will not affect this behavior.

Startup exception handling

Only the hosting layer can handle exceptions that take place during app startup. Exceptions that occur during app startup can impact server behavior. For example, if an exception happens before you call KestrelServerOptions.UseHttps, the hosting layer catches the exception, starts the server, and displays an error page on the non-SSL port. If an exception happens after that line executes, the error page is served over HTTPS instead.

You can configure how the host will behave in response to errors during startup using CaptureStartupErrors and the detailedErrors key.

ASP.NET MVC error handling

MVC apps have some additional options for handling errors, such as configuring exception filters and performing model validation.

Exception Filters

Exception filters can be configured globally or on a per-controller or per-action basis in an MVC app. These filters handle any unhandled exception that occurs during the execution of a controller action or another filter, and are not called otherwise. Learn more about exception filters in

Tip [wp-svg-icons icon=”pushpin” wrap=”i”]

Exception filters are good for trapping exceptions that occur within MVC actions, but they’re not as flexible as error handling middleware. Prefer middleware for the general case, and use filters only where you need to do error handling differently based on which MVC action was chosen.

Handling Model State Errors

Model validation occurs prior to each controller action being invoked, and it is the action method’s responsibility to inspect ModelState.IsValid and react appropriately.

Some apps will choose to follow a standard convention for dealing with model validation errors, in which case a filter may be an appropriate place to implement such a policy. You should test how your actions behave with invalid model states.

India Windows Hosting Review

WindowsASPNETHosting.in VS IndiaLinks: Pricing & Features

WindowsASPNETHosting.in VS IndiaLinks: Uptime & Speed

WindowsASPNETHosting.in VS IndiaLinks: Technical Support

Conclusion: WindowsASPNETHosting.in VS IndiaLinks?

How to Configure Your ASP.NET Core App For IIS

What is the WebHostBuilder?

What is AspNetCoreModule?

Install .NET Core Windows Server Hosting Bundle

Steps to Deploy ASP.NET Core to IIS

Step 1: Publish to a File Folder

Step 2: Copy Files to Preferred IIS Location

Step 3: Create Application in IIS

Step 4: Load Your App!

Advantages of Using IIS with ASP.NET Core Hosting

Open your Visual Studio 2017

Now, how can we change this table name from AspNetUsers to AspUsers as example.

Change Identity table property name

Change Identity table datatype of primary key

Summary

The Best ASP.NET Core 1.0 Hosting in 2017

Why They’re the Best ASP.NET Core 1.0 Hosting

1. Set the Default Route for ASP.NET Core MVC

2. Return IActionResult from .NET Core Controller Methods

3. Use the .NET Async Pattern

4. Use .NET Attributes

5. Use Async Result Filters

BONUS: Try This Workaround to Improve Serialization of Self-Referencing Object Graphs

The Angular2 part

The ASP.NET part

Big Deal 15% RABATT billig Core ASP.NET 1.0 Hosting in Europa

Warum diese Hosts bieten ASP.NET Hosting für unbegrenzte

Unlimitations und Einschränkungen der billigen ASP.NET

Top 10 Gründe, mit unseren Top ASP.NET Core 1.0 Hosting Provider Empfehlung auf Host:

ASP.NET Hosting Anforderungen

Add Session NuGet Package

Update startup.cs

Where’s the Session variable gone?

How do I store a complex object?

Use a Redis or SQL Server Cache instead

Stay up to date

The developer exception page

Warning [wp-svg-icons icon=”warning” wrap=”i”]

Configuring a custom exception handling page

Configuring status code pages

Exception-handling code

Server exception handling

Startup exception handling

ASP.NET MVC error handling

Exception Filters

Tip [wp-svg-icons icon=”pushpin” wrap=”i”]

Handling Model State Errors

2. Return `IActionResult` from .NET Core Controller Methods