2

Closed

Package Restore ignores BizTalk projects (*.btproj)

description

Enabling NuGet package restore on a solution containing BizTalk projects that consume NuGet packages does not enable package restore.

Expected:
  • NuGet.targets get imported in btproj file
  • The following MSBuild properties are added to the btproj file:
<SolutionDir Condition="$(SolutionDir) == '' Or $(SolutionDir) == '*Undefined*'">..\</SolutionDir>
<RestorePackages>true</RestorePackages>
Actual:
  • none of the expected :)
Closed Feb 5, 2013 at 6:12 PM by dotnetjunky
by design

comments

dotnetjunky wrote Feb 5, 2013 at 6:12 PM

bizTalk projects are not supported.

XavierDecoster wrote Feb 5, 2013 at 6:34 PM

any particular reason why this is the case?
seems relatively easy to support the extension and treat it as a .NET class library.

NuGet package restore works when manually adding the nuget.targets import statement (and related msbuild properties).

dotnetjunky wrote Feb 6, 2013 at 6:00 PM

We have a whitelist of supported projects. We didn't know that BizTalk project exists. Every time we want to support a new project, we need to do testing. It looks like not many people have BizTalk projects and not many packages support those either.

Is there anything special about BizTalk projects? Is it just a normal class library?

XavierDecoster wrote Feb 6, 2013 at 6:41 PM

I know about the whitelist, understand the testing argument.

Just hit this customer wanting to distribute some custom made BizTalk components using NuGet, and to be honest, it works fine after tweaking pkg restore into it, using net40 as target platform for the packages. It seems to behave as a normal class library so far.

I'm not a BizTalk expert at all, so don't know if there are any particularities about the project type. Would need confirmation from someone who knows this better. I'm sure Microsoft must know a guy :)
If it happens to be a quick win, it's one more compatibility issue to scratch from the list.