tag:help.appveyor.com,2012-11-13:/discussions/problems/10053-vs-2017-image-problemsAppVeyor: Discussion 2018-08-25T02:25:01Ztag:help.appveyor.com,2012-11-13:Comment/441100872017-11-22T22:10:41Z2017-11-22T22:10:42ZVS 2017 image problems?<div><p>Hi AppVeyor Team! Hope everything is going well.</p>
<p>We've just started seeing an odd warning:</p>
<blockquote>
<p>warning MSB4078: The project file "example\Sample\Sample.csproj" is not supported by MSBuild and cannot be built.</p>
</blockquote>
<p>in our <code>dotnet</code> projects in <a href="https://github.com/serilog/serilog-filters-expressions">https://github.com/serilog/serilog-filters-expressions</a>. I don't believe we've made changes that would trigger this - wondering if a new build image has been rolled out?</p>
<p>The build is: <a href="https://ci.appveyor.com/project/serilog/serilog-filters-expressions/build/1.0.31">https://ci.appveyor.com/project/serilog/serilog-filters-expressions...</a>, with configuration: <a href="https://github.com/serilog/serilog-filters-expressions/blob/dev/appveyor.yml">https://github.com/serilog/serilog-filters-expressions/blob/dev/app...</a> and build process <a href="https://github.com/serilog/serilog-filters-expressions/blob/dev/Build.ps1">https://github.com/serilog/serilog-filters-expressions/blob/dev/Bui...</a>.</p>
<p>Any suggestions or pointers to possible causes greatly appreciated :-)</p>
<p>(BTW, we've had a bit of GitHub/AppVeyor flakiness that let a PR through without having been built - see, e.g. <a href="https://github.com/serilog/serilog-filters-expressions/pull/18">https://github.com/serilog/serilog-filters-expressions/pull/18</a> - if we can send any info that would help track this down, let me know).</p>
<p>Thanks!</p></div>Nicholas Blumhardttag:help.appveyor.com,2012-11-13:Comment/441100872017-11-22T23:24:37Z2017-11-22T23:25:07ZVS 2017 image problems?<div><p>Yes, it was build worker image update on weekend. However what looks strange for me is that it does not seem (from build logs) that your <code>appveyor.yml</code> is being respected. I do not see that you set <code>ignore appveyor.yml</code> so I wonder if this can be connected to GitHub authorization. Can you please try to open <a href="https://ci.appveyor.com/account">https://ci.appveyor.com/account</a>, revoke GitHub access and then authorize GitHub again and run build after that and see if <code>Build.ps1</code> was started? Please let us know what you found.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/441100872017-11-22T23:29:16Z2017-11-22T23:29:16ZVS 2017 image problems?<div><p>Thank you, Ilya. I've re-authorised AppVeyor on GitHub and this seems to<br>
have resolved the issue:<br>
<a href="https://ci.appveyor.com/project/serilog/serilog-filters-expressions">https://ci.appveyor.com/project/serilog/serilog-filters-expressions</a><br>
Strangely, GitHub was shown as "not authorised", so perhaps<br>
something expired?<br>
Appreciate the help, I'll loop back here if we see any more issues.</p>
<p>Best regards,<br>
Nick</p>
<p><em>Nicholas Blumhardt</em> Seq — structured logs for .NET apps <a href="https://getseq.net">https://getseq.net</a> · @getseq_net[1]</p></div>Nicholas Blumhardttag:help.appveyor.com,2012-11-13:Comment/441100872017-11-22T23:31:36Z2017-11-22T23:31:36ZVS 2017 image problems?<div><p>Sometimes OAuth token get "stale". Sorry for non-scientific term and luck of full understanding :) We plan to make token "refresh" easier.</p></div>Ilya Finkelshteyn