![](/static/61a827a1/assets/icons/icon-96x96.png)
![](https://hexbear.net/pictrs/image/2c4e08c9-7864-4b30-8012-7ffb79b949f6.jpeg)
2·
16 days agoFahrenheit does have a wider range of whole numbers to express the temperatures in our daily climate. Unfortunately the digital thermostats I had for years, even one in Shanghai, would step in 0.5 deg increments regardless of it being in F or C. I assume it was using K internally throughout the system, so keeping it in F meant more granularity (68, 68.5, 69 being more specific temps than 20, 20.5, 21 could dial in). And it was noticeable enough to where I’d keep it in F (except one time when I was sick and wanted in between the two possible F setpoints).
Sorry ASP.NET sucks so bad. The VS solution might already have an applicable Publish Profile if it was cloned from another within the organization. Because it’s Microsoft and so old, there’s a lot of ways to have an existing site configured that can cause issues.
The compiled app should be able to be dropped onto the web server and registered as an application under a new or existing “Site”. Sites have virtual hostnames registered within IIS manager, I think they call them “Bindings”. The
applicationHost.config
XML file for the IIS hosting environment makes it easier to find values than IIS Manager but don’t get in the habit of making complicated edits without testing. This might be like dev-product.company.local ordev-product.company.net
or whatever and should probably be reachable on whatever network you’re on.Once the app is registered to a Site, within IIS manager you can right click the app and hit Browse and it’ll open in Internet Explorer probably. If the app has a different initial URL for actually doing something you might have to navigate to it (eg web browser will open to
dev-product.company.net/WebApplication-Portal/
but you have to go todev-product.company.net/WebApplication-Portal/Dashboard
)Also worth checking the Event logs in Windows for errors, but with 404s you could also have a file system permission problem. Usually it’ll actually throw a 403 if the IIS service account couldn’t access the folder containing files/webapp though.
Oh and make sure the app is in one of the “app pools” and check the pool it’s in is Started.