locked
Referencing net standard library in classic asp.net projects (.net framework 4.6.1) crashes iisexpress.exe RRS feed

  • Question

  • User2097043994 posted

    In every classic asp.net projects that references some net standard library every rebuild causes iisexpress.exe to crash.

    Application: iisexpress.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an internal error in the .NET Runtime at IP 73A39FFD (739A0000) with exit code 80131506.
    Faulting application name: iisexpress.exe, version: 10.0.14358.1000, time stamp: 0x574fc56b
    Faulting module name: clr.dll, version: 4.7.3163.0, time stamp: 0x5b58fbbe
    Exception code: 0xc0000005
    Fault offset: 0x00099ffd
    Faulting process id: 0x457c
    Faulting application start time: 0x01d44f3dacea0183
    Faulting application path: C:\Program Files (x86)\IIS Express\iisexpress.exe
    Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
    Report Id: 053f0094-64f0-4aab-8396-48575a1feaed
    Faulting package full name: 
    Faulting package-relative application ID:
    Exception thrown at 0x73A39FFD (clr.dll) in iisexpress.exe: 0xC0000005: Access violation reading location 0x0000001C.

    It is annoying that on every rebuild I must restart iis express.

    Tool: Visual Studio Community 2017, Version 15.8.4

    https://github.com/dotnet/standard/issues/873

    Wednesday, September 26, 2018 12:53 PM

All replies

  • User283571144 posted

    Hi daliborsoftad,

    According to your description, I have created a net standared project and referenced it in the classic asp.net projects (.net framework 4.6.1), it works well.

    The IIS doesn't show any error message.

    My VS version is as below:

    My test demo 

    Net standared class library:

        public class Class1
        {
            public string create() {
                return "create";
            }
        }

    MVC:

            public ActionResult Index()
            {
                Class1 class1 = new Class1();
                String re = class1.create();
                return View();
            }

    Result:

    Best Regards,

    Brando

    Thursday, September 27, 2018 2:32 AM
  • User2097043994 posted

    Hi Brando,

    Have you tried to run your application form visual studio without debugging (Ctrl + F5)? And while application is running change something in net standard class library. For example:

        public class Class1
        {
            public string create() {
                return "createChanged";
            }
        }

    After that try to run your MVC application without debugging again (Ctrl + F5).

    In my case this second application running with changes kill my iis express process. Also my net standard library using entity framework core to communicate with mssql database and bunch of other stuffs from net core DI, logging, configuration etc.

    Thursday, September 27, 2018 8:25 AM
  • User283571144 posted

    Hi daliborsoftad,

    According to your description, I have created a test demo on my side and run with crtl+F5.

    It also work well.

    Result:

    Could you please share the project on the github or the onedrivew for me to reproduce the issue on my local side?

    Best Regards,

    Brando

    Monday, October 1, 2018 1:58 AM
  • User2097043994 posted

    Hi Brando,

    Never mind,

    It is a private project of my company so I am not allowed to share source code in public.

    I can only tell you that my asp.net mvc project using Umbraco as presentation layer, but all other layers (services, repositories, common utilities and helper libraries) are separated projects in netstandard.

    We are using net standard for other layers because in the future we are planning to switch presentation layer with some netcore CMS. Currently we cannot find any good one netcore CMS to replace Umbraco.

    This problem only happens in development when same instance of IISExpress try to reload old dlls with new one. This is not problem in production.

    Monday, October 1, 2018 11:08 AM
  • User283571144 posted

    Hi daliborsoftad,

    I suggest you could try to use different VS version to try again.

    If this issue is still exists, I suggest you could use VS help tag to send feedback to VS team.

    Best Regards,

    Brando

    Tuesday, October 2, 2018 6:09 AM