Paket install removes assembly bindings in app.config
See original GitHub issueIn my Windows app with .NET Framework 4.6.2:
When I throw away the packages folder to start fresh and then run paket install
, the assembly bindings get removed from the app.config file of each project.
I manually have to undo all changes to the app.config files before checking them in. Otherwise my application throws a big fat error because of invalid assembly references.
Issue Analytics
- State:
- Created 6 years ago
- Comments:20 (9 by maintainers)
Top Results From Across the Web
Assembly binding added in compiled output (app.config)
Is there any way, to check why the assembly binding is added automatically? ... 2) then delete any bindredirect on the app.config file....
Read more >The paket.dependencies file
This option tells Paket to create Assembly Binding Redirects for all referenced libraries. This option only instructs Paket to create and manage binding...
Read more >Binding Redirect being added to every app.config
When I build Package A helper with references to Package A version 5.0.0.0 then all the bindingRedirects don't get auto-populated in every app....
Read more >The located assembly's manifest definition does not match ...
Bcl.AsyncInterfaces, I have bindingRedirect set in app.config. ... Remove binding redirects from target.
Read more >Migration basics from NuGet to Paket - The Cockney Coder
Simply adding the line redirects: on to your dependencies file instructs Paket to figure out any required binding redirects, and then add them ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If you don’t care about your app.config getting a little bit messy, you can add
redirects: force
to the group, then redirects will be added for all packages, regardless of whether they are actually needed or not.famous last words 😉 TBH exactly the issues around nuget and redirects made us build paket in the first place