You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By the way the target framework is .net 9.0, I'm building with .net sdk 9.0.100 and I can build in my development machine without any issues. Also I can use nbgv get-version without any error in azure devops or local machine.
Edit: The commit with 30b07c3f71f16fee9b6073fbf8831458ae0ebf11 is corresponding with symbolic link of a folder. When I delete symbolic link and move the actual folder, it can build. But I need to use symbolic link.
The text was updated successfully, but these errors were encountered:
The commit with 30b07c3f71f16fee9b6073fbf8831458ae0ebf11 is corresponding with symbolic link of a folder. When I delete symbolic link and move the actual folder, it can build. But I need to use symbolic link.
Are you saying that that commit added a symbolic link to the tree? Can you describe what you did to add it?
Does it only fail when you try to build something within that symbol folder?
then commited it. After this error occured, I've deleted SymLinkFolder, moved RealFolder to symlinked location, then pushed force(amend) on git, and it worked.
In short:
Error with git commit has:
Hi,
As stated in the document, I made
fetchDepth:0
to use this package on Azure Devops, but I still get the following error during the build phase:The head of the pipeline file looks like this:
And
Directory.Packages.props
file looks like this:By the way the target framework is .net 9.0, I'm building with .net sdk 9.0.100 and I can build in my development machine without any issues. Also I can use
nbgv get-version
without any error in azure devops or local machine.Edit: The commit with 30b07c3f71f16fee9b6073fbf8831458ae0ebf11 is corresponding with symbolic link of a folder. When I delete symbolic link and move the actual folder, it can build. But I need to use symbolic link.
The text was updated successfully, but these errors were encountered: