Hi there

Is there a viable workflow for continued development of an existing ASP dot NET Web Forms application just using the command line, a text editor and a web browser, without running Visual Studio (at least not all the time)?

Since Web Forms do not run on dot Net Core, a Windows machine (physical or virtual) is required. The work is being done on a non-Windows machine, and connecting in to the Windows machine via Remote Desktop to run Visual Studio is not a preferred option (though it may be the only viable one, and is what I am doing currently).

In principle working via the terminal, some form of file sync or share, and a browser is possible and I have done it with SSH, MSBuild.exe and IIS Express, but what is missing is all the output from the Output window of Visual Studio. There are various ways of logging that could be set up, but what I like about the Output window is it tells exceptions, as well as debug messages, and I am pretty lost without it.

Any recommendations, other than give up, and keep using Visual Studio?

​Hi there Is there a viable workflow for continued development of an existing ASP dot NET Web Forms application just using the command line, a text editor and a web browser, without running Visual Studio (at least not all the time)? Since Web Forms do not run on dot Net Core, a Windows machine (physical or virtual) is required. The work is being done on a non-Windows machine, and connecting in to the Windows machine via Remote Desktop to run Visual Studio is not a preferred option (though it may be the only viable one, and is what I am doing currently). In principle working via the terminal, some form of file sync or share, and a browser is possible and I have done it with SSH, MSBuild.exe and IIS Express, but what is missing is all the output from the Output window of Visual Studio. There are various ways of logging that could be set up, but what I like about the Output window is it tells exceptions, as well as debug messages, and I am pretty lost without it. Any recommendations, other than give up, and keep using Visual Studio?  Read More

​