Fix for missing xml comment for publicly visible type or member asp.net core

Fix for “missing xml comment for publicly visible type or member” in ASP.NET Core

This warning cs1591 missing xml comment for publicly visible type or member, you may get while building the application or Visual studio will also display red squiggle in your code at all places where XML comments are missing. The warning can be ignored, but that red squiggle in code is quite annoying. So in this short post, find out how to fix/disable this warning cs1591 in ASP.NET Core projects.
(more…)

Read More

Where is Package.json in ASP.NET Core Project?

ASP.NET Core prefers JSON over XML for configuration and earlier I posted about all different JSON files present in new ASP.NET Core solution. And one of the JSON configuration file is Package.json and it is the place for npm modules. But when you won’t find this file in solution explorer for your ASP.NET Core project, as by default, this file is hidden. In this short post, you will find various way to make this file visible in Solution explorer.
(more…)

Read More

Difference between “dnx run” and “dotnet run”

Earlier I posted about dotnet cli, which is a new command line tool which is going to replace DNX commands and it will be part of ASP.NET 5 RC 2 release. Since ASP.NET 5 is now ASP.NET Core 1.0, so not quite sure what would be the release name now but irrespective the name, it is expected to release this month only. I was playing with dotnet commands and noticed that dotnet run command is different from dnx run command. So in this post, you will see the difference between “dnx run” and “dotnet run”. (more…)

Read More

Fix for dnx project start up error in VS 2015

How to fix “dnx project start up error in VS 2015”

While working with ASP.NET 5 application using Visual Studio 2015, you may encounter an dnx project start up error in VS 2015 when you try to open a project. The error message says “The following error occurred attempting to run the DNX design time process (dnx-clr-win-x86.1.0.0-rc1-update1). No connection could be made because the target machine actively refused it [::ffff:127.0.0.1]:63106”.
(more…)

Read More