References still have to be manually added

[msjonathan]

When I implemented the abstracted pipeline component I still had to search and add the correct Microsoft dll's.

Maybe we can add the references node to the dll's that we want?

References - https://docs.nuget.org/create/nuspec-reference

<references> 
  <group targetFramework="net45"> 
      <reference file="a.dll" />
  </group> 
  <group targetFramework="netcore45"> 
    <reference file="b.dll" /> 
  </group>
  <group>
    <reference file="c.dll" />
  </group>
</references>

[tomkerkhove]

I think it depends on what you want to achieve and who should be responsible.

Do we want to be responsible of distributing the BizTalk specific DLLs?
If so, we would have to take a look at how we will handle the different versions of BizTalk

[msjonathan]

I am not talking about shiping Microsoft dll's.

Think of if you are shiping a nuget packages that has a dependency to a WPF reference. this does not mean that you will ship it only reference it, because it's already installed by the .Net Fx.

Concerning about the versions, i would keep it easy we'll try to pinpoint it by the .Net Fx version.
your packages depends on a certain dll, installed already with your .Net fx.

Source Wiki:
2010 - BizTalk Server 2010[6](First version to work with Visual Studio 2010 and Microsoft .NET 4.0)
2013 - BizTalk 2013 (First version to work with Visual Studio 2012 and Microsoft .NET 4.5)
2014 - BizTalk 2013 R2 (First version to work with Visual Studio 2013 and Microsoft .NET 4.5.1)

[tomkerkhove]

Ok, I get it and good suggestion.

The only disadvantage I see is that when you're using BizTalk 2013 R2 and you're still on .NET 4.5 it would look for BizTalk 2013 but the default should handle that, right?

[tomkerkhove]

Is this something you want to have a look at?