Commit 3e26080
Fixed an issue where CodeDom would be disabled post-upgrade
Fixes #7213
A two step process was put in place to disable CodeDom compilation before its upgrade and re-enable it aftewards. This was implemented in #6455
However when upgrading from-to the same version, something did not go right and no changes were detected upon the last step of that process. With this PR the change detection appears to be fixed and the web.config saves after the second XmlMerge.
I have tested upgrades from 10.2.4 and 10.3.0 as well as a clean install and the web.config is fine after each of those scenarios.
This PR includes the changes from #7221 as I could not build without it, so merging the other first will make this one easier to review.1 parent 3db13b3 commit 3e26080
1 file changed
Lines changed: 11 additions & 1 deletion
File tree
- DNN Platform/Components/Microsoft.CodeDom.Providers.DotNetCompilerPlatform
Lines changed: 11 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
33 | 33 | | |
34 | 34 | | |
35 | 35 | | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
36 | 44 | | |
37 | 45 | | |
38 | 46 | | |
| |||
194 | 202 | | |
195 | 203 | | |
196 | 204 | | |
197 | | - | |
| 205 | + | |
| 206 | + | |
| 207 | + | |
198 | 208 | | |
199 | 209 | | |
200 | 210 | | |
| |||
0 commit comments