compilation error

venkatad · February 6th, 2009, 10:28 AM

Hi Here I get compilation error when i run asp.net 2.0 application on Widnows server 2000. Could please give me some insight into this problem. I tried to add system.drawing from the visualstudio 2005, but no use.

Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: CS0012: The type 'System.Drawing.Color' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.

Source Error:

Line 18: <td colspan="2" style="border-bottom: olive thick solid; height: 1px; background-color: #003399">
Line 19: <img align="absmiddle" src="Images/logo.gif" style="border-left-color: olive; border-left-style: none; border-right-width: thick; border-right-color: olive; width: 87px; height: 97px;" />
Line 20: <asp:SiteMapPath ID="SiteMapPath1" runat="server" ForeColor="FloralWhite" style="vertical-align: top">
Line 21: <NodeStyle BackColor="#80FFFF" />
Line 22: <CurrentNodeStyle ForeColor="Blue" />

Lee Dumond · February 6th, 2009, 12:04 PM

I would try this:

Code:

<asp:SiteMapPath ID="SiteMapPath1" runat="server" style="vertical-align: top; color: #fffaf0;">

venkatad · February 10th, 2009, 01:26 PM

Quote:

Originally Posted by Lee Dumond

I would try this:

Code:

<asp:SiteMapPath ID="SiteMapPath1" runat="server" style="vertical-align: top; color: #fffaf0;">

Tried but no use...Its frustrating me this error even i dont find any references online regarding this specific error

dparsons · February 10th, 2009, 03:19 PM

Did you use the code EXACTLY as Lee posted it? It seems to me that .NET does not like the color you have supplied for the ForeColor attribute of your SiteMap.

hth.
-Doug

Old Pedant · February 10th, 2009, 05:12 PM

The problem is simple: The color "FloralWhite" is defined (I'm pretty sure in an enumeration) in (as the error message says) System.Drawing.Color.

Now, why that DLL is not included in his build and not loaded to the production server, I dunno. But either using a <STYLE> as Lee suggested *OR* (I believe) using a number instead of a name should get rid of the dependency on the DLL.

And while Lee's suggestion of using a <STYLE> should get him past that one line 20, he will then run into the line

Code:

Line 22:                         <CurrentNodeStyle ForeColor="Blue" />

and there's no good way to use a <STYLE> for that. (This might be what he meant when he said he'd tried Lee's suggestion and it didn't work. He is being very reticent in supplying us with details.) So I'd suggest just using color numbers. Perhaps

Code:

<CurrentNodeStyle ForeColor="#0000FF" />

I'm not sure that will do the job. Possibly the compiler will still assume it needs that DLL just because of the ForeColor= reference. But it's worth a stab.

venkatad · February 12th, 2009, 12:23 PM

Quote:

Originally Posted by Old Pedant

The problem is simple: The color "FloralWhite" is defined (I'm pretty sure in an enumeration) in (as the error message says) System.Drawing.Color.

Now, why that DLL is not included in his build and not loaded to the production server, I dunno. But either using a <STYLE> as Lee suggested *OR* (I believe) using a number instead of a name should get rid of the dependency on the DLL.

And while Lee's suggestion of using a <STYLE> should get him past that one line 20, he will then run into the line

Code:

Line 22:                         <CurrentNodeStyle ForeColor="Blue" />

and there's no good way to use a <STYLE> for that. (This might be what he meant when he said he'd tried Lee's suggestion and it didn't work. He is being very reticent in supplying us with details.) So I'd suggest just using color numbers. Perhaps

Code:

<CurrentNodeStyle ForeColor="#0000FF" />

I'm not sure that will do the job. Possibly the compiler will still assume it needs that DLL just because of the ForeColor= reference. But it's worth a stab.

OK let me try this way and i will put back if any errors, but this time i will give you a complete picture..

Lee Dumond · February 12th, 2009, 02:14 PM

Umm... just an idea...

The error message says that you haven't referenced the System.Drawing assembly. So, why not just ADD the reference?

In web.config:

Code:

<compilation>
   <assemblies>        
      <add assembly="System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
   </assembies>
</compilation>

If that doesn't work, you have a bigger issue that you would just be covering up by using the RGB codes. It means the System.Drawing assembly is missing from your server, and that's not good.

Old Pedant · February 12th, 2009, 06:01 PM

Well, in his first post he said

Quote:

I tried to add system.drawing from the visualstudio 2005, but no use.

so I (perhaps foolishly) assumed he had already done that. I guess we'll find out.