-
We were looking to move to using Cake.Frosting in DNN Platform, and thought we fairly successfully did that migration. However, after tweaking the few differences that cropped up, we ended up with an MSBuild error that we can't resolve when running in Azure Pipelines. We've tried adding the UseDotNet task to make sure everything works and adjusting the framework the Frosting project is built with, but are getting these weird errors from a project targeting .NET Standard 2.0:
Has anyone run into these? Any ideas of what might be missing in our Azure Pipelines environment? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 6 replies
-
On first glance I don't see anything directly related to Cake which can cause this. You have this issue only while running on Azure Pipelines? Do you build also on other CI systems? Some ideas how to analyze further:
|
Beta Was this translation helpful? Give feedback.
-
Our build is working fine before using Cake.Frosting, and then using the
same build logic with the Frosting runner we see this error. The
configuration is the same in either case.
Our current theory is that when the runner downloads .Net 5 SDK during
bootstrapping it messes with the config for other steps (though that
doesn't seem to get happening locally). It's still pulling in an RC version
of the SDK, could that be an issue?
I've seen suggestions to set MSBuildSDKsPath, but most of them ended with
Microsoft folks saying to revert that change because they had fixed
whatever underlying issue. So, we would use the UseDotNet task to restore
to a certain location and then set that environment variable to the same
location?
We don't build on any other CI system.
Thanks!
|
Beta Was this translation helpful? Give feedback.
-
@pascalberger Can you explain in a bit more details what we need to adjust to do so ? |
Beta Was this translation helpful? Give feedback.
@pascalberger Can you explain in a bit more details what we need to adjust to do so ?