Go 4 Sharepoint

Search:

Welcome: Guest!

Sharepoint Forum

Home » Forum » Sharepoint

Ask a question

RSS Feeds

Conflict between GAC and Bin dlls

Asked By: Harshit Guha Date: Jul 29, 2009 Category: Sharepoint Views: 588

I'm customizing a SharePoint application, and I am referencing in my
Visual Studio project a dll that also exists in the GAC. The project
builds just fine, but when I hit the page I get the following error:

An error occurred during the processing of .
c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
Files\root\bef9a111\5466e63c\App_Web_welcomelinks.aspx_-1775745042.a7euki4f.0.cs\
(128):
error CS0433: The type
'Microsoft.SharePoint.Publishing.PublishingLayoutPage' exists in both
'c:\WINDOWS\assembly\GAC_MSIL\Microsoft.SharePoint.Publishing\12.0.0.0__71e9bce1\
11e9429c\Microsoft.SharePoint.Publishing.dll'
and 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
Files\root\bef9a111\5466e63c\assembly\dl3\4f0b8d4e\c81e2802_6788c901\PPM.DLL'

Any ideas on how to resolve this conflict? I can't uninstall the dll
from the GAC due to some dependencies, and I can't build my project
without the reference.

Tagged:conflict between gac and bin dlls

1 Answer Found

Answer #1 Answered By: Yogendra Zarapkar Answered On: Jul 29, 2009

Just delete the one in the temporary files. The Microsoft.SharePoint namespace
files shouldn't be anywhere other than the GAC on the server anyway. Are you by
any chance working on a local workstation where you have manually installed the
dlls for development?

Didn't find what you were looking for? Find more on Conflict between GAC and Bin dlls Or get search suggestion and latest updates.

Your Answer

Answer should be atleast 30 Characters.
Please put code inside [Code] your code [/Code].

Please login to post comment

Previous: View URL's removed from search results

Next: CSS not being applied

Go4Sharepoint, is a Microsoft Featured Community. Microsoft, Windows, Sharepoint, Sharepoint logo, Windows logo, etc are trademarks of the Microsoft Corporation. All product names, logos, copyrights, and trademarks mentioned are acknowledged as the registered intellectual property of their respective owners. This site is not in any way affiliated with, nor has it been authorized, sponsored, or otherwise approved by, Microsoft Corporation.