ansaurus

Question

Compile Error CS0433 on pre-compiled ASP.NET 2.0 site.

Answer 1

+1 A:

For me, closing the IDE, shutting the web site (IIS or Cassini), deleting all of my temporary asp.net files, launching the IDE and doing a full compile does the trick.

domus.vita 2009-01-14 13:42:05

Well, sure, but that's not the root cause of it. All I have to do is hit F5 a several times, and the site WILL come back... It's like a cache issue more than anything...

LarryF 2009-01-14 20:09:05

This happens to me all the time, and clearing things out does the trick. Would love to know if someone actually knows the root cause other.

JD Conley 2009-01-15 00:43:13

Answer 2

A:

The cause MIGHT be that some other DLL's you are referencing might be referencing the older/newer version of the specified assembly. So different parts of the app are referencing different versions of the assembly. I ran into an issue like this as well. In order to resolve it, I forced the app to use the new version:

I changed all of my references in the web.config to point to the newer version. In my case it was the System.Web.Extensions assembly that was causing problems. I changed all of them from 1.0.60125.0 to 3.5.0.0

Next, I added these lines to my web.config, which basically tells your application to "forward" all references to the old version of the assembly, to the new one:

<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <probing privatePath="bin;sitefinity\admin\bin" />
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="Telerik.Security" publicKeyToken="dfeaee0e3978ac79" />
        <bindingRedirect oldVersion="3.2.1598.2" newVersion="3.5.1747.2" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="Telerik.Cms.Web.UI" publicKeyToken="dfeaee0e3978ac79" />
        <bindingRedirect oldVersion="3.2.1598.2" newVersion="3.5.1747.2" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="Telerik.Web.UI" publicKeyToken="121fae78165ba3d4" />
        <bindingRedirect oldVersion="2008.1.515.20" newVersion="2008.2.1001.20" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>

I did not come up with this solution, but found it somewhere that I can't remember. However, I don't think I've ever seen an explanation of exactly why this happens either!

SkippyFire 2009-02-13 14:45:38

Answer 3

+1 A:

in IIS you need to restart it by opening the command prompt and typing iisreset then hit enter, however if your using the build in Visual Studio web server (Cassini) then this wont solve your problem. You can terminate all running Cassini instances by typing (exactly like this because its Case Sensitive): taskkill /f /im "WebDev.WebServer.exe" and hitting enter. You will then see the following message: SUCCESS: The Process "WebDev.WebServer.EXE" with PID <some #> has been terminated.

2009-03-02 16:18:01

Answer 4

A:

To fix this bug, it's fairly simple, but requires some rarely used declarations (hard part was digging through the right documentation ;).

See ECMA-334, Section, 16.3 "Extern alias directives"

If you control "your" source and are linking to another assembly "their" binary, yet you can not change (or do not want too change:) the namespace/type specifiers (e.g. BOTH of you declare System). I actually ran into this a fair amount lately, with all the Beta/Alpha/Version updates to the CLR/DLR, MS has been churning a lot in their published namespace's.

When you import assembly "their", typically the compiler will set it up into the global (reserved) namespace. In MSVC, you go to properties on the assembly reference, go to where it say's "Aliases", you can then specify a new name, other than global. Or actually a few names.

Let's say you use the imaginative name of "global2".

You then goto your source files and at the TOP before any namespace declarations, you place;

extern alias global2;
using global2::System;

Your code can then use the types from global2, like "Int32" or whichever, you can still rename it via;

extern alias global2;
using global2::System;
using orig = System;

RandomNickName42 2009-05-31 20:54:06

Answer 5

A:

I just had this problem. It turns out that, I accidentally drag-&-dropped files from one project to another, which created a duplicate. It took me a while to find the problem, because the files were hidden within the Properties folder (which I never look into).

In any case, what helped me solve the problem was going into the file that was throwing the error, r-clicking on the erroneous line and "going to definition". Being in the definition, you can see which physical file you are looking at. If it isn't what it is supposed to be, then you found your problem.

I know this is trivial, but it wasted me around 1 hour of time, so hope this info would be useful to anyone.

niaher 2009-11-21 06:51:39

Answer 6

+1 A:

killing Cassini instances as above didn't work for me. ScottGu posted about this issue

setting the batch="false" attribute on the compilation section in web.config worked for me.

<configuration>

   <system.web>
       <compilation debug="false" batch="false"></compilation>
   </system.web>

</configuration>

This tells ASP.NET to dynamically compile individual .aspx/.ascx files into separate assemblies. This avoids the circular reference issue that triggers the exception.

Justin Moore 2010-05-20 22:47:52

thanks this fixed it for me when restarting Cassini did not.

fearoffours 2010-08-18 13:39:50

Answer 7

A:

btw, CodeBehind isn't old and not used!

CodeBehind= is for pages in Web Application (with .Designer.cs files) and CodeFile= is for page in Web Site (dynamically compiled assemblies so without .Designer.cs files)

abatishchev 2010-05-20 22:51:56

ansaurus

tags:

views:

answers:

Compile Error CS0433 on pre-compiled ASP.NET 2.0 site.

related questions