{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 姐就是有狂的资本 的问题《Visual Studio warning: “Some of the properties ass》','https://www.manongdao.com/q-179225.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
When I open my solution, I get a dialog with this warning. The solution (one web app, one class project) builds without errors.
How can I determine what properties are causing the problem, and resolve the error?
相关问题
- How to know full paths to DLL's from .csproj f
- Importing NuGet references through a local project
- Visual Studio 2019 - error MSB8020: The build tool
- 'System.Threading.ThreadAbortException' in
- VS2017 RC - The following error occurred when tryi
相关文章
- How to show location of errors, references to memb
- Suppress “Circular dependency detected” suppress w
- How to track MongoDB requests from a console appli
- Visual Studio Hangs on Loading UI Library
- How to use Mercurial from Visual Studio 2010?
- Copy different file to output directory for releas
- Edit & Continue doesn't work
- “Csc.exe” exited with code -1073741819
For me the problem was empty spaces (due to copy-paste) at the end of each line. By removing them I didn't get the error again.
I just fixed a similar issue in VS2012 with 44 projects.
The cause was a combination of a duplicated
GlobalSection(TeamFoundationVersionControl)section (a la Boycs' answer), but I also had several projects duplicated--as well as a few references to projects which had been recently removed--within theGlobalSection(TeamFoundationVersionControl)section that I kept.Once I had ensured that all of the referenced projects corresponded 1:1 with actual projects in my solution, the warning went away.
Aside: I suspect that the majority of these issues could have been avoided with closer attention paid to the .sln during branch and commit merges, but who knows what VS is thinking sometimes...