Last post Jun 06, 2016 01:54 PM by hpkierspel
Jun 05, 2016 01:51 PM|hpkierspel|LINK
I get HTTP Error 502.3 when I try to start a brand new ASP.NET core application (RC2) from within Visual Studio. I can start this application with "dotnet run". Im also able to start "old" RC1 ASP.NET 5 applications from within Visual Studio.
Jun 05, 2016 02:02 PM|Janshair Khan|LINK
Try to update ASP.NET Core for Visual Studio from
Jun 05, 2016 03:44 PM|hpkierspel|LINK
Thanks for your prompt Response! Using your link I took the following steps:
- Download and install "NuGet.Tools.vsix"
- Uninstall "Microsoft .NET Core 1.0.0 RC2 - SDK Preview 1 (x64)" and "Microsoft .NET Core 1.0.0 RC2 - VS 2015 Tooling Preview 1"
- Download and install "DotNetCore.1.0.0.RC2-VS2015Tools.Preview1.exe"
Unfortunately I still have the same issue, I cannot start an ASP.NET core application from within Visual Studio.
Jun 05, 2016 04:01 PM|maherjendoubi|LINK
Examine the arguments attribute on the <aspNetCore> element in web.config to confirm that it is either (a).\my_applciation.dll for a portable application; or (b) not present, an empty string (arguments=”“),
or a list of your application’s arguments (arguments=”arg1, arg2, ...”) for a self-contained application.
Jun 05, 2016 06:58 PM|hpkierspel|LINK
I am using a complete unmodified ASP.NET core project generated by "File - New - Project... - ASP.NET Core Web Application (.NET Core) - OK - Web Application - OK" and then started by "Debug - Start Debugging / Start Without Debugging".
The <aspNetCore> element is unmodified and has the form:
By the way, this element is marked as an invalid child element of the element <system.webServer>
Jun 05, 2016 07:48 PM|Radomir|LINK
Anything in Application event log? If the module can't start dotnet it would be logged there. Also you don't have bitdefender by any chance?
Jun 06, 2016 08:28 AM|hpkierspel|LINK
In the application event log I only find:
Process '3792' failed to start. Port = 31572, Error Code = '-2147023829'.
On the error page of my application I find:
I also tried to start the application with disabled firewall in bitdefender but this makes no difference.
Jun 06, 2016 11:38 AM|Radomir|LINK
Last two post in that link have more info... try uninstalling Bitdefender and see if that resolves the issue...
Jun 06, 2016 01:54 PM|hpkierspel|LINK
Yes! You are perfectly right! Bitdefender is back again!
Fortunately it is still sufficient to disable "BrowserLink" to make the application run within Visual Studio again.
Thanks for the great help from all!