Asp.Net core Web app

3 posts, 0 answers
  1. Nicolas
    Nicolas avatar
    1 posts
    Member since:
    Oct 2015

    Posted 08 Jul Link to this post

    Since the new release of Asp.Net core 1.0.0, I'm no longer able to create or open a new Asp.Net core Web application. As soon as the solution opens, dotnet.exe process stop working because of an error caused by JustMock. If I disable profiler, everything works fine. Is this a known issue ?
  2. Paul
    Paul avatar
    12 posts
    Member since:
    Apr 2015

    Posted 11 Jul Link to this post

    2 days, no reply although its been a weekend.

    Been through the same thing on this here. 

    https://github.com/aspnet/Tooling/issues/629#issuecomment-231368231

    Will wait and see what Telerik say.

     

  3. DevCraft R3 2016 release webinar banner
  4. Svetlozar
    Admin
    Svetlozar avatar
    269 posts

    Posted 11 Jul Link to this post

    Hi,

    I am really sorry for the inconvenience!

    Yes, this is a known issue. JustMock can't attach itself to dotnet.exe. It is a known issue, already logged in our system.

    When you have the profiler enabled, it tries to attach itself to every .NET process. Unfortunately it fails to attach to dotnet.exe. That being said, we suggest you keep the profiler enabled only for testing sessions and disable it when you are done.

    There is a another workaround - we have blacklist configuration with processes that JustMock shouldn't attach itself to. You can add dotnet.exe to 

    "C:\Program Files (x86)\Telerik\JustMock\Libraries\CodeWeaver\32\ImageBlacklist.cfg"
    "C:\Program Files (x86)\Telerik\JustMock\Libraries\CodeWeaver\62\ImageBlacklist.cfg"


    Once again, I am really sorry for the inconvenience!

    Regards,
    Svetlozar
    Telerik by Progress
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top