CODEWITHSUNDEEP
c#nugetowin
acostela
acostela

Reputation: 2727

Nuget creates app.config files in multiple projects

I'm starting to use Nuget in my solution to install Owin and some other dependencies in certain projects. I'm reading about Nuget and app.config files here

Why NuGet adds app.config with assemblyBinding to LIBRARY projects during a NuGet package update?

and here

https://msdn.microsoft.com/en-us/library/7wd6ex19.aspx

Now I know why are they used, binding specific versions and so on...

The problem that I'm having is that i.e I have a big solution with 32 projects.

If I install Owin in project C. An app.config file appears in projects A,B,D,F with the following information.

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
          <assemblyIdentity name="Microsoft.Owin" 
              publicKeyToken="31bf3856ad364e35" culture="neutral" />
          <bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" />
      </dependentAssembly>
    </assemblyBinding>
</runtime>

Why I'm getting this? These projects are not using OWIN. Is there any way to avoid this? Or maybe installing it manually without using nuget?

Thank you.

P.S: I'm using VS2015 enterprise

EDIT:

The architecture that we have it's as follow. I Have project WebApi with Owin installed. That project is referenced with the project Connector. That project Connector and all that reference it have the previous app.config file. Is that correct? Why it's necessary if they are not using OWIN?

EDIT2:

I uninstalled all nuget packages from my solution using nuget package manager inside VS2015 and these files with that dependencies are still there.

Upvotes: 4

Views: 3012

Answers (1)

Michael Freidgeim
Michael Freidgeim

Reputation: 28435

I suggest to trust NuGet and leave app.config changes that it does(khellang explained why), but if it is really annoys you, you can skip applying binding redirects

Upvotes: 2

Related Questions