Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In Visual Studio 2008 Team System, this is my warning:
Different checksum values given for '<some folder>' ...\Visual Studio 2008\Projects\...
\Debug\...\SomeFile.g.cs
The offending line in the SomeFile.g.cs file is:
#pragma checksum "..\..\..\..\..\..\...\SomeFile.xaml" "{406ea660-64cf-4c82-b6f0-42d48172a799}" "A18BC47B27EC4695C69B69F1831E3225"
I deleted all of the *.g.cs files in the Solution and rebuilt and all of the warnings came back. What the hell is this?
It looks like Visual Studio doesn’t handle very long paths correctly when generating GUIDs. I confirmed this by adding two different files into a long path and reproduced the behavior you are seeing. If you look in the offending SomeFile.g.cs files you will notice that the guids for the two files are the same. Apparently Visual Studio only checks the first x characters of the file path when generating this GUID.
From the .g.cs files:
As for a solution, I guess you could either shorten your paths or (more likely) ignore these warnings. 🙂