-
Notifications
You must be signed in to change notification settings - Fork 58
Move web.config to root #115
Comments
@BillHiebert FYI |
A hair of guidance for RC2-nightly folks ...
... of course, mirror changes in [EDIT] Add |
@guardrex what changes did you need to make in app code? |
@Tratcher ... None ... there is some debate right now on JabbR whether or not I'm playing with a full deck of cards. The "he's not" group is in the majority! 😄 When I said "app code," I only meant in the project ... I didn't mean actual "application code." Sorry. When you see the 🍺 emoji, that means you should take me even less seriously than usual. Good news is that these configuration changes went great this evening. All apps are smiling 😄 and working just fine. |
Does this affect templates as well? I remember adding wwwroot to the content section in project.json just to make sure that web.config is copied. Now we should probably leave it to the user because by default we will not have anything to copy so we should not add wwwroot to the content section in project.json. /cc @rustd Also the publish iis tool looks for the config file in the wwwroot folder and create one wwwroot folder if one does not exist. We also should no longer set the path to the application base. |
Yes, this would impact templates. @JunTaoLuo should send a PR there once we have this ready. |
@davidfowl you have been nominated by @Tratcher to write the announcement for this change. |
In order to make us more reliable on IIS we are going to move the web.config into the root of the published output instead of the web root.
@muratg
The text was updated successfully, but these errors were encountered: