CODEWITHSUNDEEP
c#asp.net.netcsc
AndreaNobili
AndreaNobili

Reputation: 42957

Why does C# encounter this error as to the CSC file?

I am pretty new in C# development and I have the following problem.

When I try to build the application on which I am working I obtain the followings errors message:

Error   2   Source file 'Log\LogUserManager.cs' could not be found  C:\Develop\MyFramework4.0\MyManagerCSharp\CSC   MyManagerCSharp
Error   8   Source file 'AntiPhishing.cs' could not be found    C:\Develop\EarlyWarning\public\Implementazione\Ver2\UnitTestProject\CSC UnitTestProject

It seeams to me that these errors appeared after an SVN update.

Why? What exactly means? If I click on the error line it don't take me to the code line where the error appear. What is the CSC file? How can try to fix this issue?

Tnx

Upvotes: 51

Views: 97393

Answers (12)

Hoodlum
Hoodlum

Reputation: 1503

I ran into this problem after converting a VB.Net project to C#. The issue was in the .csproj file as stated in a couple of the answers above. For the issue I had specifically, there were 2 properties where the value was being used. In comparing with the .vbproj I could see one of the properties wasn't in the vb file. Deleting that property from the .csproj file fixed the issue. The removed property was call "DocumentationFile"

enter image description here

Upvotes: 0

Đăng Hoàng Nguyễn
Đăng Hoàng Nguyễn

Reputation: 21

It is error in csproject file. Sometimes user delete files but visual studio did not update csproject file. You can search :

Log\LogUserManager.cs

AntiPhishing.cs

then delete that 2 lines and save csproject file. This work for me.

Upvotes: 0

tvb108108
tvb108108

Reputation: 408

My issue was this in my csproject file:

<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
<WarningsNotAsErrors>SA0001</WarningsNotAsErrors>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|AnyCPU'">
    <TreatWarningsAsErrors>true</TreatWarningsAsErrors>
    <WarningsNotAsErrors>SA0001</WarningsNotAsErrors>
</PropertyGroup>

I deleted both of them and I was able to build with no issues.

Upvotes: 0

Abdul Martinez
Abdul Martinez

Reputation: 81

After trying almost everything this is what I found:

The root cause of the problem is garbage in the .csproj or Project file. In order to find the problem do the following:

  1. Right click and Unload the project file
  2. Right click and Edit the project file
  3. Search on the text for the reference that is giving you errors, probably will be in a
  4. Delete it or fix the entry.
  5. Right click and Reload Project.

Upvotes: 8

Chris997422
Chris997422

Reputation: 11

Cleaning the solution helped resolve some of my dll not found errors, in the CSC file. Not sure your specific error but cleaning/rebuilding might be helpful to try if you haven't already.

Upvotes: 1

JohnWrensby
JohnWrensby

Reputation: 2842

TFS: Get latest version. Fixed it for me.

Upvotes: 0

Nicolas Coombs
Nicolas Coombs

Reputation: 335

For posterity, it is also worth noting that if you enabled the XML documentation file in Visual Studio (project properties > Build > Output), set an absolute path to it, and then push it to your code repository of choice, anyone pulling your code and not verifying this will encounter a particularly unspecified error in the CSC file. Should this be the case, even doing a clean build will produce the error in all individuals who pulled your code (assuming the path does not exist on their system).

In this scenario, the path should be removed from this and only the filename should be left.

I do not know if other compilers will encounter this issue, but it is worth looking into as well.

Upvotes: 1

Running Buffalo
Running Buffalo

Reputation: 1323

I got this error after deleting a controller. I had already removed all references, but Visual Studio was still looking for the file.

After running the clean command, unloading, and reloading the project, VS showed the reference to the missing file in the solution explorer. I right-click > deleted the file (again).

The project ran fine after that.

Upvotes: 0

bonkmaykr
bonkmaykr

Reputation: 104

CSC is the references/dependencies. Since DLLs are technically compiled already there's not much you can do to fix them, that is, if they were broken.

One possible reason for your issue is that your references are not actually where the IDE expects them to be. AKA, the dependencies can't actually be found. This might be the case, even if the IDE's file browser(s) say otherwise.

It's also possible that you had the error at some point in YOUR code, then fixed it, and then VS decided to act retarded and tell you something is wrong with your "CSC" files. Trust me, that just happened to me, and it confused me so bad I spent over half an hour trying to fix a bug that didn't exist.

Don't worry, if that's the case, just restart VS and re-open your project, then it should work just fine. If it doesn't fix the issue then try checking that all your dependencies are *actually there*.

Upvotes: 0

Dan
Dan

Reputation: 2167

This can also happen if you renamed your startup class, but didn't update the startup object in your project settings.

Upvotes: 10

Daniel King
Daniel King

Reputation: 142

This question occurred a long time ago, but for others that view this, make sure that the c# files are on your hard drive. Sometimes the Solution Explorer shows that they are there, but they aren't.

Upvotes: 10

Padrus
Padrus

Reputation: 2053

These are not errors in the code but errors in the references of your project. Check that the references are indeed located where they point.

It is possible that when doing your SVN update, some source files have been moved but you didn't update your .csproj containing the references to these files.

Upvotes: 56

Related Questions