tag:help.appveyor.com,2012-11-13:/discussions/problems/1743-problems-with-microsoftcommoncurrentversiontargetsAppVeyor: Discussion 2018-10-19T08:17:04Ztag:help.appveyor.com,2012-11-13:Comment/362434992015-03-10T12:34:33Z2015-03-10T12:34:33ZProblems with Microsoft.Common.CurrentVersion.targets<div><p>Hi guys,</p>
<p>I'm having trouble compiling my project.</p>
<p>I think it's a well known problem, but I tried everything and
didn't even come close to a solution:</p>
<p>C:\Program Files
(x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(1697,5):
warning MSB3245: Could not resolve this reference. Could not locate
the assembly "WebGrease". Check to make sure the assembly exists on
disk.</p>
<p>The same error occurs with other references as well:
Raven.Client.Lightweight.</p>
<p>Nuget package restore is enabled for solution. The project that
is a submodule also has NUget restore enabled. I also added nuget
restore just to make sure. But in the top, all packages are
installed.<br>
Nuget.exe is updated to latest version.</p>
<p>Thanks,<br>
Mark</p></div>marktag:help.appveyor.com,2012-11-13:Comment/362434992015-03-10T15:26:16Z2015-03-10T15:26:16ZProblems with Microsoft.Common.CurrentVersion.targets<div><p>So it's probably sub-modules? Git submodules are not checked out
by default. Take a look at this
<a>article: http://www.appveyor.com/docs/how-to/private-git-sub-modules</a></p>
<p>In addition to that - now it's possible to see project public
SSH key on its General tab, so the "easiest" way (less secure but
maybe just to see if everything works) to allow access to
sub-module repositories is to move repository SSH key under account
on GitHub.</p>
<p>-Feodor</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/362434992015-03-10T15:45:09Z2015-03-10T15:45:09ZProblems with Microsoft.Common.CurrentVersion.targets<div><p>Hi Feodor,</p>
<p>Thanks for getting back to me so fast. Yes, it is a private
submodule. I followed that guide and added the ssh key. The build
log also implies, that the project is available and found, but it's
not only related to that specific project. A project inside the
original repository and VS solution also throws.</p>
<p>I've attached a log with some modifications ;)</p></div>marktag:help.appveyor.com,2012-11-13:Comment/362434992015-03-10T15:54:05Z2015-03-10T15:54:05ZProblems with Microsoft.Common.CurrentVersion.targets<div><p>Try enabling detailed logging to see paths msbuild "considers"
while trying to resolve those references. Wrong versions could be
referenced there or absolute paths. Check .csproj contents for
reference paths as well.</p>
<p>-Feodor</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/362434992015-03-11T10:16:22Z2015-03-11T10:16:22ZProblems with Microsoft.Common.CurrentVersion.targets<div><p>Thanks, Feodor. You pointed me in the right direction. There
were serverel issues with references into other projects bin folder
and some that were unnecessary.<br>
After some package reinstalls, updates etc, it works now.</p>
<p>Thanks :-)</p></div>mark