Skip to main content

Missing And New Features In ASP.NET Core

Hi all, before starting with ASP.NET Core, we must know what are the new things that are added in it and what features are eliminated from it.

 This is the most repeated question everyone is asking me: What is the difference between MVC5 and CORE MVC?

Let me share my thoughts on it below.

We should expect some changes when advanced technology is released with existing technology.
Similarly, in CORE we might be surprised to find some items are missing.

Firstly, we shall look at New Features,
  1. App_start
    This folder previously contained start up processes and settings such as configurations and routing. But now in .NETCore this item is replaced with startup.cs. Now we can all the settings, configuration and routing details in startup.cs.
  2. App_data
    This folder contains application data such as local database and log files. This folder in not included in Core version, but you have a chance to add it back to your project.
  3. Global.asax
    This file is not required because all startup functionality has been placed in startup.cs.
  4. Web Config
    This web.config file also been deleted from core version. Now all application settings are found in appsettings.json.
  5. Scripts
    Scripts directory used to store the js files has a home of scriptings, now in core all the files reside under wwwroot/js as static resource.

    In Core MVC, both MVC Controllers and WEB API controllers use the same routes and controller base class.
Let have a look at the root folder; there are many new files and folders in the project as shown below.

Let’s explore and understand their purpose in the project,

  1. SRC
    The root folder of the project is src folder, we call it source folder.

    This folder is used to identify the source code of the project.
  2. wwwroot

    The wwwroot folder is used by the host to serve static resources. Sub-folders also include js, css, images and libraries. The lib folder contains third party js libraries added via nugetpackage manager.
  3. Dependencies
    In Core MVC, more package management options are available, this version included bower and NPM Support, which we can configure by GUI.

    Additionally we can manage configuration by their respective json files.

  1. project.json
    The project.json file describes the application and its .NET dependencies. Unlike prior versions of MVC, you can add and remove .NET dependencies for your application using the project.json file.

    These dependencies are resolved through NuGet, and full intellisense is enabled within the file; simply begin typing the desired NuGet package name, and suggestions will appear on-the-fly. You can also configure cross-platform compilation and build scripts here.
  2. appsettings.jsonThe appsettings.json file is the primary replacement for the Web.Config. In this file, you'll specify application settings such as connection string, email endpoints and more. The new configuration model supports the JSON format which is used throughout ASP.NET Core MVC.
Thanks for reading my blog.Sharing is Caring :)
#RathrolaPremKumar (MVP)


Popular posts from this blog

ERROR: Cannot resolve the collation conflict between SQL_Latin1_General_CP1_CI_AS and Latin1_General_CI_AS_KS_WS in the equal to operation

ERROR: Cannot resolve the collation conflict between SQL_Latin1_General_CP1_CI_AS and Latin1_General_CI_AS_KS_WS in the equal to operation
dont get panic if u get the following error while in your joinings, there is a simple way to solve this.
it is because of collation settings on two columns we are doing joinings. it is because of collation settings on two columns we are doing joinings
First step is to figure out what are two colaltion that cause for conflicts. Let us assume that collation has not been set at the column level and instead at db level, then we have to execute two simple statements as below.

Statements: Select DATABASEPROPERTYYEX('DB1',N'Collation') Select DATABASEPROPERTYYEX('DB2',N'Collation')
One more thing, make a note that if you are on sharepoint you will get error as below
Latin_General_CI_AS_KS_WS. if you are on most any other database and use the dafault settings you may get this SQL_Latin_General_CP1_CI_AS.
Now we have to do some…

How To Create The Data Adapter Object Using ADO.NET by #RathrolaPremKumar

By reading this article, you will learn key points in ADO.NET, as given below. What is Data Adapter?Primary Data Adapters for the databases.Data Adapter properties.Methods used by Data Adapter.How to create Data Adapter with an example? Let’s start our demo with a Data Adapter introduction. Actually, we use Data Adapter object to establish the connection to the data source and manage the movement of date to and from the database. What is Data Adapter? A data adapter aobject serves as a bridge between a data set object and Data Source such as a database to retrieve and save the data. Data adapter contains a set of database commands and a database connection, which we use to fill a dataset object and update the Data Source. Primary data adapters for databases? .NET makes two primary data adapters available for use with the databases. Other data adapters can also be integrated with Visual Studio .NET. Primary Data Adapters are mentioned below. OleDbData Adapter, which is suitable for use wi…

'#Resolve' To export a list, you must have a Microsoft SharePoint Foundation-compatible application.

Searching this error message easily finds the root of the problem. There is a problem with the Office 64 bit version. It doesn’t work with SharePoint. These solutions generally tell you to uninstall your 64 bit office and install a 32 bit version. Happily there is a much easier solution.
Despite the error message the export actually works! Notice the yellow bar at the bottom of your browser. Simply save the .iqy file normally and open it with Excel. It’s that simple. The error message is certainly a nuisance but does not actually stop the export.
Thanks for ready my blog :)