Geek Answers Handbook

TeamCity: Type or namespace not found, but link exists, and my project compiles locally

I have an ASP.net MVC 3 project. We use TeamCity, and so far everything has been checked in order. Suddenly, I checked today and the TeamCity build failed. He said that I was missing a link to a directive or assembly, and I wrote a compilation error.

The project on my local machine completes successfully. I redid it several times to make sure. I checked the link there too. I checked the .csproj file and there is a link there. I checked the bean; it's over there. I even rdped to the server where our site is deployed, and checked the bean there, and there is also a dll file.

I don’t understand why it doesn’t work, I didn’t change anything in specific files, which, according to him, have no assembly link in weeks, yesterday I had a successful check for TeamCity, the DLL file exists wherever it should, and my project is under construction. I even made a hard reset for the last commit I made, which passed the test successfully, added my changes back (which had nothing to do with the reference problem, all my changes were in the .js file) and checked that in, but I got same compilation error.

Does anyone know what is going wrong, or at least that I can try to solve?

edit: path files are not used here, this file is a DLL file that I added by clicking "Add Link" in the project. I checked the Github repository and the .dll file is in the bin folder

+4
source share
4 answers

iamkrillin made me think that maybe this was a problem of the path, so I opened the csproj file and noticed that the link format is "missing", the file is different from everyone else:

<Reference Include="Ektron.Newtonsoft.json">
  <HintPath>..\..\Custom\bin\Ektron.Newtonsoft.json.dll</HintPath>
</Reference>

// THE "MISSING" FILE
<Reference Include="Smdg.Utils, Version=1.0.0.0, Culture=neutral, processorArchitecture=MSIL">
  <SpecificVersion>False</SpecificVersion>
  <HintPath>..\NEHGS\bin\Smdg.Utils.dll</HintPath>
</Reference>

I checked the Custom \ bin folder and of course was there. The DLL file (although it also existed in NEHGS \ bin), so I got rid of the SpecificVersion tag and changed the path to the user folder. TeamCity was able to verify it.

Why it was suddenly broken when he worked the last 2 months, I have no idea.

+5
source

I only had this because I did not store NUGET packets in VCS (GIT).

, NUGET .

https://blog.jetbrains.com/teamcity/2013/08/nuget-package-restore-with-teamcity/

+2

, TC . , . . tage dll, TC

+1

I hope this helps someone, in my case I had to check the folders in which the dll / nuget reference packages were. Please note that I have already completed the project, but for some reason "SVN" did not check / fix the (local) folders with dll / nuget packages, so I had to go to the folders and check them.

0
source

More articles:


All Articles