Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
Cannot build VSIX package in Visual Studio 2017
Options
Previous Topic Next Topic
PeterGerrard
#1 Posted : Wednesday, March 22, 2017 3:12:56 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 3/22/2017(UTC)
Posts: 2
Location: United Kingdom

Was thanked: 1 time(s) in 1 post(s)
Hi,

I have an issue when building a VSIX package in Visual Studio 2017

Reproduction Steps:
NCrunch Version: 3.6.0.2
Visual Studio 2017: 15.0.0+26228.9

- Create a new VSIX package project
- Let NCrunch build it
Visual Studio can build it

Expected Outcome:
It Builds

Actual Outcome:
Get Error Message
Quote:

..\..\..\..\..\..\..\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Microsoft\VisualStudio\v15.0\VSSDK\Microsoft.VsSDK.targets (90, 5): The "ValidateVsixManifest" task failed unexpectedly.
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Setup.Common, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.VisualStudio.Setup.Common, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
at Microsoft.VsSDK.Build.Tasks.ValidateVsixManifestUtilities.ValidateVsix(TaskLoggingHelper log, String manifestToValidate, String vsixSchemaPath, Boolean validateEverything, String& name, String& id)
at Microsoft.VsSDK.Build.Tasks.ValidateVsixManifest.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()


Any help on getting this sorted. would be appreciated.
Nb. This is different to the main error I'm getting in my main solution, but I can't reproduce that simply with the current issue.




Peter Gerrard
Back to top
Remco
#2 Posted : Wednesday, March 22, 2017 10:08:50 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,145

Thanks: 960 times
Was thanked: 1290 time(s) in 1196 post(s)
Hi Peter,

This looks to be an error thrown by a VSIX validation step in your build process. Probably this step isn't needed for NCrunch to run tests over the assembly, so it may be worth disabling it by specifying a condition on the <Import> used to include it in your build system, for example:

<Import Project="PathToVSSDK\Microsoft.VsSDK.targets" Condition="'$(NCrunch)' != '1'" />

It may also be possible to get this working by turning on the 'Copy referenced assemblies to workspace' setting for the projects involved, though I'd recommend avoiding this if possible as it will inhibit your performance.
Back to top
PeterGerrard
#3 Posted : Thursday, March 23, 2017 1:03:34 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 3/22/2017(UTC)
Posts: 2
Location: United Kingdom

Was thanked: 1 time(s) in 1 post(s)
Hi,

Including
Code:
<Import Project="PathToVSSDK\Microsoft.VsSDK.targets" Condition="'$(NCrunch)' != '1'" />
has worked around the issue for now. And the tests have successfully run in NCrunch.


Thanks,



Peter
Back to top
1 user thanked PeterGerrard for this useful post.
Remco on 3/23/2017(UTC)
Remco
#4 Posted : Thursday, March 23, 2017 10:18:53 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,145

Thanks: 960 times
Was thanked: 1290 time(s) in 1196 post(s)
Great to hear. This will also improve your build performance under NCrunch.
Back to top
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.038 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download