Base solution for your next web application
Open Closed

Which IDE? #5712


User avatar
0
[email protected] created

Hi,

I am curious to know what IDE and setup people are using for ASPNETZERO running with .NET CORE and jQuery. We are running VS 2017 Enterprise with Resharper with the application hosted in IIS. My PC is in i7 with 32GB and an SSD.

The development experience is VERY slow and laggy. Also, the solution takes roughly 1 minute to build and usually fails due to VS not being able to access the application pool. I then have to restart the application pool and build again.

Now, I am not suggesting that this is the fault of ASPNETZERO, but I am curious as to what over devs are using, whether they have had speed issues with the solution and what tricks they have used to increase the responsiveness and speed of the writing and debugging code.

Thanks in advance.


3 Answer(s)
  • User Avatar
    0
    [email protected] created

    Hi,

    If nobody in the community is able to assist with the query, I would like to know what environment the developers are using when working with the ASP.NET ZERO repo?

    Thanks in advance.

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi @sduffy

    We most of the time run the project using CTRL + F5 and don't have such a problem. But, probably you have more pages (css & js files) than we do. So bundling process might take longer time for you.

    You can try to remove bundling code from *.Mvc.csproj file here https://github.com/aspnetzero/aspnet-zero-core/blob/dev/aspnet-core/src/MyCompanyName.AbpZeroTemplate.Web.Mvc/MyCompanyName.AbpZeroTemplate.Web.Mvc.csproj#L85. But in that case, you need to remember when to re-build your bundles.

  • User Avatar
    0
    alexanderpilhar created

    Hi @sduffy

    Until a few weeks ago I had a similar setup as you, only less RAM (8 GB). Currently I'm on a Intel Xeon E3-1225 V2 and 32 GB.

    Never had any issues running ASPNETZERO (Core + Angular).

    Executing 'npm run hmr' is still pretty slow (the '92% after chunk asset optimization'-part), but that's the only 'problem' there is so far.