Modify Visual Studio 2019 development environment so as to permit run and debug of an existing IIS web site
Budget: $250 – $750 USD
This is a small IIS project. It should take no more than a couple of hours for the right person. The goal is to determine why the development environment for an existing web site fails to run and fix it.
Background: I've inherited an existing IIS project that is currently in use but the client would like to make changes to it. The previous programmer presented me with a virtual machine that was supposed to contain a stand alone development environment that he'd been using to work on this web site prior to deployment. The VM contains a Windows 2008 server OS with IIS, SQL Server, Visual Studio and the web site's source code which was an ASPX.NET C# web application that uses a few 3rd party packages. Contrary to expectations, attempts to run the web site project in the normal fashion fail. The reasons why it doesn't run are the point of this job. I need someone who is well versed in all things IIS on Windows to show me what's wrong and help me fix it.
As stated previously, one would expect that a person learned in the ways of IIS and Visual Studio running an ASPX.NET web site should be able to recognize where the configuration problems lay and educate me in how to fix them. I've verified that the source supplied in the VM is identical to what's in the production server so the failure is likely a matter of user rights, IIS settings, or configuration files but after considerable time trying to track this down I've failed to find the right combination. Time to call in help from someone who knows what they're doing.
Here's how I'd like to approach the problem:
1) Find a good candidate.
2) I'll share the VM's desktop in a limited access fashion and the two of use will investigate it together. I'm in the metro Boston area so the consultant will need to be in a timezone that is compatible.
3) Although I am a very experienced programmer my IIS is at a beginner's level. Educate me as we investigate.
4) The end goal is to get the development VM environment to run the problem web site under VS debugger without changing the source code itself. Modifying the OS, IIS or configuration files is permitted.a
Background: I've inherited an existing IIS project that is currently in use but the client would like to make changes to it. The previous programmer presented me with a virtual machine that was supposed to contain a stand alone development environment that he'd been using to work on this web site prior to deployment. The VM contains a Windows 2008 server OS with IIS, SQL Server, Visual Studio and the web site's source code which was an ASPX.NET C# web application that uses a few 3rd party packages. Contrary to expectations, attempts to run the web site project in the normal fashion fail. The reasons why it doesn't run are the point of this job. I need someone who is well versed in all things IIS on Windows to show me what's wrong and help me fix it.
As stated previously, one would expect that a person learned in the ways of IIS and Visual Studio running an ASPX.NET web site should be able to recognize where the configuration problems lay and educate me in how to fix them. I've verified that the source supplied in the VM is identical to what's in the production server so the failure is likely a matter of user rights, IIS settings, or configuration files but after considerable time trying to track this down I've failed to find the right combination. Time to call in help from someone who knows what they're doing.
Here's how I'd like to approach the problem:
1) Find a good candidate.
2) I'll share the VM's desktop in a limited access fashion and the two of use will investigate it together. I'm in the metro Boston area so the consultant will need to be in a timezone that is compatible.
3) Although I am a very experienced programmer my IIS is at a beginner's level. Educate me as we investigate.
4) The end goal is to get the development VM environment to run the problem web site under VS debugger without changing the source code itself. Modifying the OS, IIS or configuration files is permitted.a