I have this repoon github: https://github.com/fgaravaglia/Umbrella.Infrastructure.Firestore
project A is published on nuget
project B.Tests is referencing ProjectA locally (not by nuget)
during CI build, I got error Ambiguous project name when restoring test project.
any suggestion?
I already changed PackageId tag on source proejct and rechange during CI build, but it didn't worked
Related
Scenario: We wanted to move some code over to a new repo (NewSln), so we created that new repo, and then added the code back as a submodule in the original repo (OldSln). Had to modify a few references to point to the new version, but was able to get the build to work locally.
Issue: After doing this, the Azure Devops build failed on the msbuild building step due to
Error : This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105
The missing file is ..\..\..\packages\Fody.6.5.2\build\Fody.targets. and other similar issues. We had not made any changes to those references
I noticed that the restore step was restoring the packages to the submodule directory. For example, I saw this line
2022-02-10T23:52:45.1474898Z Adding package 'AcisExtensionSDK.1.0.4.1061' to folder 'C:__w\1\s\NewSln\packages'
I confirmed that this submodule is only used by the larger repo and not the submodule, yet it is being restored to \NewSln\packages\ rather than \packages\
Debugging effort so far: I can see the references that are showing up as missing on the build locally, and the build is working locally, with nothing obvious to me as why it fails on dev ops. I also see various stack overflow posts about the opposite issue, where the nuget restore doesn't import the references for the submodule repo, but I found nothing for the case where only the submodule repo is restored.
Is there anything that could cause this and what would be the way to route the packages being restored back to the appropriate package?
I am developing a multimodules maven project on eclipse.
I would like commit on gitlab project. The project has 1 parent module and 3 childs modules.
First I cloned a empty gitlab project, then I created the maven project under my git folder on local pc.
I tried a commit and on stage section there is whole project modules,parents and child. The parents module contains the sources of the child modules.
How can I commit my project on gitlab?
It is possible select the file to commit on the project tree?
Thank you....
I have a CoreApp project (CoreApp) and a Project1 that depends on the CoreApp Project. Thanks to someone from MSFT on SO, previously I was able to get this compiled with VSTS git using the (CoreApp)submodule under Project1. However, now in Project1, whenever I reference a model in the CoreApp Project (eg., a AppUser class), I get the build error - "The type or namespace name 'AppUser' could not be found (are you missing a using directive or an assembly reference?)" error. I read some SO posts and changed not only the folder name but also the CoreApp Model namespace in the CoreApp project, and now I got a different error - "The type or namespace name 'CoreAppModels' does not exist in the namespace 'CoreAppApp' (are you missing an assembly reference?) [d:\a\1\Project1\Project1.csproj]. I also continue to get the previous error. It seems to me that the build process is not picking up the CoreApp assembly, or the updated code, but I did see that the CoreApp project was pulled down during the build process.
All of this works and builds fine on my PC. I verified that on VSTS, I have the CoreApp file with the hash, and the .gitmodules with the entry -
[submodule "Project1/CoreApp"]
path = Project1/CoreApp
url = https://name.visualstudio.com/_git/CoreApp
Again, I do see that the CoreApp is pulled down during the build -
Copying file from "obj\Release\CoreApp.dll" to "bin\CoreApp.dll".
CoreApp -> d:\a\1\s\Project1\CoreApp\bin\CoreApp.dll
Does the build process on VSTS pull down the latest submodule code when doing a build? Does anyone know what I am doing wrong? I am pulling my hair out and any help is appreciated. Thank you!
Please check your VSTS build definition:
In Get source step -> show the advanced settings -> make sure the Checkout submodules is selected -> Save.
Then build your project1 again, the Project1\CoreApp\bin\CoreApp.dll will be found from submodule.
To update sumodules in main repo, you can add a Command Line task after Get sources step:
Tool: git
Arguments: submodule foreach "git pull origin master"
I am moving from VS2015 to VS2017. I keep a local NuGet repository of stuff I'm working on that is used in other projects in a folder "D:\Development\ZNugetFeed".
I'm having to do a restore packages, and under VS2017 even though the file is there in the correct folder, and VS2017 is configured to use it as a repository, I keep getting an error "Unable to find version 'x.x.xxxx.xxxxx' of package 'y'." It then shows all the locations it says it didn't find it, including the folder it is in.
Has anyone seen this type of problem?
We solved the problem by installing IIS and the Nuget app, and then pointing VS2017 to the app.
I am trying to create an Eclipse project from a cloned Git repository
I've cloned the repository from here:
https://github.com/nazgee/AndEnginePhysicsBox2DExtension
I have an existing project AndEnginePhysicsBox2DExtension and I want to create one called AndEnginePhysicsBox2DExtension-nazgee with the newly cloned repository.
When I try File -> Import -> Projects from Git and I select the new repository, I am unable to. I get this message:
Some or all projects cannot be imported because they already exist in the workspace.
I have the directories:
C:....AndEnginePhysicsBox2DExtension
C:....AndEnginePhysicsBox2DExtension-nazgee
Then I edit the .project file, changing:
AndEnginePhysicsBox2DExtension
to:
AndEnginePhysicsBox2DExtension-nazgeee
Also edited build.xml, adding -nazgee to project name
With this the error is now:
Invalid project description org.eclipse.egit.ui
Invalid project description org.eclipse.core.resources
I'd do it the other way around: rename your existing project in Eclipse and import the new one as you did.