Skip to main content

Creating First ASP.NET Core 3.0 App with Visual Studio 2019 Preview

The first public preview of Visual Studio 2019 and .NET Core 3.0 is out. I expect both to be a major release with lots of new features and some code breaking changes. The biggest change with .NET Core 3.0 is support for desktop applications and ASP.NET Core 3.0 will only run on .NET Core. In this post, we’ll see how to install .NET Core 3.0 and Visual Studio 2019 preview, new features of visual studio 2019 and also creating first ASP.NET Core 3.0 app with Visual Studio 2019. Read More

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.
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.
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”.
Read More