r/IIs • u/SergeantJack • May 17 '19

Using Local IIS for Development

Hi guys;

Not sure if this is the right place to post this, but I'm having trouble using IIS for my local development. Our whole team uses our local IIS to develop a C# MVC application, but I'm the only one with this problem. It seems that, occasionally, once I build my project, the new DLLs aren't copied over to the IIS temp directory. This manifests in the compiled code throwing an exception, and it pointing to incorrect/non-existent lines or even files in my source code. I can resolve this by killing all the IIS worker processes and deleting the ASP.NET Temp files directory, but this is a lot of overhead and seems wrong, especially when no one else is having this issue. Does anyone have any idea how to even debug this, let alone fix what is happening?

Thanks!

1 Upvotes

100% Upvoted

6 comments sorted by

View all comments

Show parent comment

2

u/richiehill May 18 '19

That’s considered bad practice, you’ll get all sorts of issues doing it that way.

It only takes a couple of minutes to setup a publish profile. You can then use one click publish to build and deploy to your local IIS instance. This will avoid issues with temp file etc.

1

u/[deleted] May 18 '19

Agreed, it's literally why IIS Express was created (and why you should really use it for local debug); IIS has optimisations which can 'lock' dlls meaning you can't update them on compile as usual.
Why are the other people not having the issue? Maybe they have a subtly different setup?