I have just started a couple of projects with Umbraco 9 and 10, but when I'm trying to run the site through VS19 without debug, it keeps resetting the IIS Express, which results in a connection reset.
The projects have both been installed through the dotnet templates and has no external packages installed. The only thing that has been created so far is a couple of nodes, some documenttypes and a few custom data types.
Any ideas? This doesn't happen to other projects than Umbraco 9/10
What worked for me was changing the 'Build And Run' settings in VS19.
Tools -> Options -> Projects and Solutions -> Build And Run.
Here i changed 'On Run, when projects are out of date' from 'Always build' to 'Never build'. This however means that I have to manually build everytime I make changes. Beats not being able to run the project.
Not sure why a start without debugging would trigger an out of date event though.
VS19 keeps resetting IIS Express
I have just started a couple of projects with Umbraco 9 and 10, but when I'm trying to run the site through VS19 without debug, it keeps resetting the IIS Express, which results in a connection reset.
The projects have both been installed through the dotnet templates and has no external packages installed. The only thing that has been created so far is a couple of nodes, some documenttypes and a few custom data types.
Any ideas? This doesn't happen to other projects than Umbraco 9/10
I have now updatet to VS22 - this is still an issue.
Anyone?
Same issue for me - have not yet found a fix for this...
Everything running ok for me.
is it resetting after a certain time? Are you changing anything in the backoffice when it resets?
What worked for me was changing the 'Build And Run' settings in VS19.
Tools -> Options -> Projects and Solutions -> Build And Run.
Here i changed 'On Run, when projects are out of date' from 'Always build' to 'Never build'. This however means that I have to manually build everytime I make changes. Beats not being able to run the project.
Not sure why a start without debugging would trigger an out of date event though.
Odd, mine is set to 'Always build'
This is the version I have running Microsoft Visual Studio Professional 2022 (64-bit) - Current Version 17.2.6
is working on a reply...