search

JoelHT-Landmark / NuGet-PackageNPublish

Project template and packaging targets file to allow easier Package'n'Publish integration with TFS (or other CI) builds.
Other
13 stars 12 forks source link

Fixing the issue 5 where the .mm.dll files were breaking the testing #6

Closed JamesTryand closed 11 years ago

JamesTryand commented 11 years ago

The following changes since commit 5c94dc2c122158980f244194818a91bc1fe5bc4a:

Added link to getting started screencast (2012-11-14 12:30:01 +0000)

are available in the git repository at:

https://github.com/JamesTryand/NuGet-PackageNPublish.git Issue-5-Hotfix

for you to fetch changes up to fe08cc4616fdb68eb6b7327aedb0a824f241afd9:

Fixing the issue 5 where the .mm.dll files would be included in being copied to the bin folder and project output, thus causing autotest/mightymoose to go into a recursive loop and never finish testing. (2012-12-12 09:45:03 +0000)

James Tryand (1): Fixing the issue 5 where the .mm.dll files would be included in being copied to the bin folder and project output, thus causing autotest/mightymoose to go into a recursive loop and never finish testing.

.../Package/content/_MSBuild/NuGetPackageAndPublish.targets | 4 ++-- .../_MSBuild/NuGetPackageAndPublish.targets | 4 ++-- .../_MSBuild/NuGetPackageAndPublish.targets | 4 ++-- _MSBuild/NuGetPackageAndPublish.targets | 4 ++-- 4 files changed, 8 insertions(+), 8 deletions(-)

The change was the same against all the targets and was : 

 <Target Name="CopyAssembliesToLibDirectories">
   <ItemGroup>
JoelHT-Landmark commented 11 years ago

This is a good quick fix for the MM issue.

I think I need to come up with a better way of specifying what dlls get included in the package tho' as this is related to Bug #3 - https://github.com/JoelHT-Landmark/NuGet-PackageNPublish/issues/3

JamesTryand commented 11 years ago

Thanks :-)