How to upload a file from Angular 6 to ASP.NET Core 2.1 Web API Application step by step

This post talks about how to upload a file from Angular 6 to ASP.NET Core 2.1 Web API.  First thing first, let’s create an Angular 6 app with Visual Studio 2017. To do that, open Visual Studio 2017  community edition , hit Ctrl+Shift+N and select the ASP.NET Core Web Application (.NET Core) project type from the templates. When you click Ok, you will get the following prompt, Make sure to select “ASP.NET Core 2.1” from the version dropdown and choose Angular. The Visual Studio will create an ASP.NET Core 2.1 based project with Angular 6 configured. This should create an Angular 6 app. You should run the app to make sure that there are no errors. Create Upload API in ASP.NET Core To support uploading on the server, add a Web API controller named UploadController in the Controller folder. This controller has the API to upload the file and store it at a location. Add the controller with the following code. using Microsoft.AspNetCore.

Getting Started Build Angular 6 Web Application step by step

In this article we will be building an Angular 6 application step by step from scratch with sample example. We will be generating our Angular 6 hello world application using angular CLI and then modify it to have a user management project where there will be a login screen for an admin and post login he can perform CRUD operations such as create, read, update and delete user with the sample REST API exposed using HttpClientModule. We will also be using RouterModule to have routing enabled. Also, at the end we will be integrating material designing with our Angular 6 app. Table of Contents     1. Angular 6 Highlights 2. Generating Angular 6 Project 3. Angular 6 Project Structure 4. Angular CLI Useful Commands 5. Angular 6 Routing 6. Spring Boot Implementation 7. Service in Angular 6 Application 8. Creating Components in Angular 6 9. Testing Angular 6 Application 10. Adding Material Design in Angular 6 App Angular 6 Release Highlights Angular v6 is the first release

Creation of the virtual directory failed issue whle opening the older version projects in VS2017[solved]

I attempted to load the new VS2015 project in VS2017, but it immediately failed to load.and i am getting below error popup Creation of the virtual directory http://localhost:32999/ failed with the error: Filename: redirection.config Error: Cannot read configuration file there are two solution for this issue 1) Renaming applicationhost.config :     Close VS2017     Go into folder %userprofile%\Documents\IISExpress\config     Rename applicationhost.config     Restart VS and load the solution/project     VS should have recreated applicationhost.config, and project should load 2) Copy config files to IISExpress directory copy all files from     C:\Program Files\IIS Express\config\templates\PersonalWebServer to     %userprofile%\Documents\IISExpress\config any of above solution will resolve your problem..

Security Exception in ASP.NET on shared hosting environment [solved]

When i was trying to host my newly developed website on shared server and i stuck with following exception Security Exception in ASP.NET [SecurityException: Request failed.] System.Security.CodeAccessSecurityEngine.ThrowSecurityException(RuntimeAssembly asm, PermissionSet granted, PermissionSet refused, RuntimeMethodHandleInternal rmh, SecurityAction action, Object demand, IPermission permThatFailed) +165 System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Object assemblyOrString, PermissionSet granted, PermissionSet refused, RuntimeMethodHandleInternal rmh, SecurityAction action, Object demand, IPermission permThatFailed) +100 System.Security.CodeAccessSecurityEngine.CheckSetHelper(PermissionSet grants, PermissionSet refused, PermissionSet demands, RuntimeMethodHandleInternal rmh, Object assemblyOrString, SecurityAction action, Boolean throwException) +284 System.Security.CodeAccessSecurityEngine.CheckSetHelper(CompressedStack cs, PermissionSet grants, Per

writing clean code matters for better maintenance of application

Clean code — a term first coined by Robert C. Martin in his book 'Clean Code: A Handbook of Agile craftmanship' — is very relevant in today's fast-paced, highly complex software development and lifecycle management environments. It makes it easier to evolve or maintain a finished product. Compare it, if you will, to the work of an electrician; a cabinet of tidy wires and connectors, all clearly organized and labeled, will make future changes that much easier and faster, with fewer risks of error and maybe even reduced costs over time. Part of clean code is also being considerate of others. Writing code that everyone understands, that the developer is confident is error-free and supported by clear documentation is being respectful of other team members. 'Do as you would be done by' is an applicable motto here; code that breaks once beyond the experimentation stage is likely to annoy colleagues, be embarrassing for the developer and even damage his or her reputati