This project is read-only.

VS2013 generating new MyModule.dll.config files ?

Topics: Customizing Orchard, Troubleshooting, Writing modules
Oct 26, 2013 at 10:51 AM
It is new with VS2013, I just noticed this when publishing using wen_deploy.
Many more.config files that are not transformed, may be they don't need.

Does any body knows the reason of theses files, they seem to contain a dedicated assembly environement for each produced .dll ?
With razor, aspnetPage, MVC versions.

Is there a way to avoid it ?
Oct 29, 2014 at 1:34 AM
Seems to be the equivalent of an app.config but for a dll. So, the dll can use it's own appSettings, assemblies versions...

Because I saw that MyModule.dll.config is the exact copy of /MyModule/web.config, I tried to delete this web.config file
This prevents the generation of MyModule.dll.config, and all seems to be ok : generation, dynamic and razor compilation...

The only thing I lost is razor intellisense, but it came back by re-using this web.config but in the /MyModule/Views folder
Not sure it's a good solution, maybe sometimes we need a specific web.config that resides in the /MyModule folder

Have you found a better way ?