Error using public class in App_Code: BC30002: Type 'xxx' is not defined

nqsousa · November 4th, 2009, 03:02 PM

Hi,

I am experiencing a problem when deploying a website to IIS 7.0. I have no problem when running the website in VWD 2008 Express Edition (localhost).

The error occurs when I try to view a page which uses a code-behind file containing a reference to a public class(defined under a code file under App_Code folder).
page7.aspx uses page7.aspx.vb as its code-behind page
Contents of page7.aspx.vb page are:

Quote:

Imports Class2
Partial Class Page7
Inherits System.Web.UI.Page

Protected Sub LinkButton3_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles LinkButton3.Click
Response.Redirect("Default.aspx")
End Sub

Protected Sub LinkButton2_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles LinkButton2.Click
Dim class2_api As New Class2
class2_api.displayalert(TextBox1.Text)
End Sub
End Class

There's a file named Class2.vb in the App_Code folder that contains:

Code:

Imports Microsoft.VisualBasic
Imports System.Web.UI.Page

Public Class Class2
    Inherits System.Web.UI.Page
    Sub displayalert(ByVal msg As String)
        MsgBox(msg)
    End Sub
End Class

I am using the Copy Web Site functionality in VWD2008 Exp to deploy the website to a subfolder in inetpub (IIS 7.0) folder.

I have other test pages in website which work fine as long as there is no reference to a public class.

Any help would be greatly appreciated.

jbenson001 · November 4th, 2009, 05:14 PM

What is the exact error message?

I believe the problem is that you are using a MsgBox(). MsgBox and MessagBox() will only display on the server, not the client pc. It works locally, because your PC is both the client and the server.

nqsousa · November 6th, 2009, 06:20 PM

Hi jbenson001,
The problem occurred no matter what specific procedures or functions were inside the public class that I was trying to use.
In the meantime I solved it by doing the following:

a) I changed the location where I was deploying the site in IIS 7.0: before I had the site apart from the Default Web Site. I now have the site as a sub-folder of the Default Web Site. The website is also now defined as an Application (running under the DefaultAppPool)
b) I stopped the IIS server (stopped WorldWideWeb service), and changed start mode to manual
c) I restarted the machine
d) I deleted all files under folder C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temp orary ASP.NET Files\ (I couldn't delete all until server had stopped) - this included some compiled files from the Visual Studio 2008 development testing
d) I changed WWW Service mode back to Automatic and restarted IIS Server
e) restarted Visual Studio 2008, built site, and published site to new location (under c:\inetput\wwwroot\<applicationfoldername>
The problem did not recur.

I think the issue was that for some reason the compilation of the website files upon publishing was not done properly when the site was defined in paralell with Default Web Site (as opposed to nder). It was probably in the configuration of the site itself. When you put the site working under the Default Web Site we benefit from all the inherited configurations that exist for the Default Web Site.
I also found useful deleting the temporary asp.net files. Later I did experience other error messages where it seems that the compiled files from opening the site from Visual Studio 2008, conflicted with the dlls from the compilation of the site into the IIS deployment and those errors would be solved by simply stopping the server, deleting temp files and restarting server.

nqsousa · December 8th, 2009, 05:27 AM

jbenson001,
after tinkering a few more days with the problem occurring and me getting annoyed at the solution i had pointed in prior post (which required stopping server and cleaning temp files), the problem was that I had several vb. code-behind files containing the same Partial Class name and **** and this was the problem **** with the same procedures and function names inside the partial class.
This occurred because I did copy/paste to some files (and respective vb code-behind) and left them on the solution without editing the partial class name.
The compiler was simply unable to load the class properly when it had the same procedure/function in more than one location in a partial class with the same name.
Tracking this was not so easy because - I think - the compilation of the components of the partial class only occur when the specific page is involved in a request.

Hopefully this is helpful in future cases of this error.

aguilaez · December 13th, 2009, 02:34 AM

I have the same situation. The difference of what I did is I put all .vb files in web root. My .aspx page can call function in page7.aspx.vb just fine. But when importing a file like Class2.vb in page7.aspx.vb, the .aspx won't recognize the class type in Class2.vb and throws error like

BC30002: Type 'Class2' is not defined

I even added Namespace in Class2.vb as suggested by other forum. Not working either. It seems the page7.aspx.vb is not able to find Class2.vb, because renaming the imports statement to something doesn't exist

Imports Class2
to
Imports Class2blah

resulting into same error too. It seems this is some sort of config error. Class2.vb needs to be linked to page7.aspx.vb in some ways. I'm NOT using MS Studio. Anybody knows a way to make this work without MS studio?