Re: Problems with codebehind and inherits
From: JeTmAn (JeTmAn_at_discussions.microsoft.com)
Date: 09/16/04
- Next message: Greg Reynolds: "Re: passing information from webpage textbox to sql select stateme"
- Previous message: Hermit Dave: "Re: ASP and ASP.NET question"
- In reply to: Hermit Dave: "Re: Problems with codebehind and inherits"
- Next in thread: Hermit Dave: "Re: Problems with codebehind and inherits"
- Reply: Hermit Dave: "Re: Problems with codebehind and inherits"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 16 Sep 2004 13:31:03 -0700
Thanks for your reply. The reason why I don't think re-installing will work
is because it has always done this on all installs of VS.NET I've ever done
(that includes 2002 and 2003 on multiple machines). Additionally, I loaded
my co-worker's application using the exact same machine where I'm having the
problems with my application, and his application worked flawlessly, exactly
like it does on his machine. So I think it's got to basically be a systemic
problem having to do with the way I create projects in VS.NET.
One of the only differences between the way my co-worker creates his
projects and the way I create mine is that he creates his on the localhost of
his own computer (and just copies the files over to the server when he wants
to host it) whereas I am creating mine directly off the server (more or
less). What I am going to do is to try installing IIS 6 on my local machine
and then starting a project locally and seeing if that makes a difference.
"Hermit Dave" wrote:
> firstly the codebehind is for Visual studio to interpret. it will continue
> working when you change it to src cause run time understands src attributes
> and that causes the file to compile when accessed first time.
> Regaring the namespace and Page issues, I feel that for some reason VS.NET
> isnt installed / working correctly.
>
> Consider re-installing visual studio. If that doesnt sort the problem out, i
> would suggest going a step further and unistalling both vs.net & the
> framework.
> then install vs.net from start.
>
> if all that doesnt work. just rebuilt the box. its the easiest of the
> options.
>
> --
>
> Regards,
>
> Hermit Dave
> (http://hdave.blogspot.com)
> "JeTmAn" <JeTmAn@discussions.microsoft.com> wrote in message
> news:1DC26D60-3A3B-4527-9B9B-3CA37FD945C0@microsoft.com...
> > Hi all, first time poster here. For some reason, the default codebehind =
> > "blahblah.aspx.vb" statement that ASP.NET inserts into a new .aspx file
> has
> > never worked for me, and I don't know why. I can only get my page to
> > recognize the .vb file if I change "codebehind=Blahblah.aspx.vb" to
> > "src=Blahblah.aspx.vb".
> >
> > Also, by default ASP.NET has my pages inherit from Namespace.Class,
> > Namespace being my project name, and Class being whichever Class
> corresponds
> > to that file in the .vb section. This doesn't work either, and gives me
> and
> > error, saying that that class can't be found. However, if I change it to
> just
> > reference the class name itself, without the Namespace., it works fine.
> >
> > After I've done all of this, my pages do load, but next time I load up
> > visual studio and try to bring up my pages, it won't load the GUI part, so
> I
> > can't see what my page should look like. I'm forced to go into the code
> part
> > of the .aspx file, cut and paste the entire <%@ Page line out of the code,
> > reload it, and then put that code back in. Then I get the GUI and the
> > functionality. But I have to do this every time I load a different page.
> >
> > It seems like I have problems in general with referencing class
> definitions
> > within my own applications and I don't know why. I loaded the application
> of
> > a co-worker and he didn't have a single one of these problems, so I'm not
> > sure what I'm doing wrong. I was deleting the global.asax file and not
> using
> > it, but I didn't think that made a difference. I'm not using any compiled
> > components (dlls) in my bin directory, or at least not any dlls compiled
> from
> > code I've actually written (I've got dlls for things like Crystal Reports
> in
> > there).
> >
> > Anyways, if anyone has heard of things like this happening or perhaps
> knows
> > a common solution, I'd really appreciate hearing it.
> >
>
>
>
- Next message: Greg Reynolds: "Re: passing information from webpage textbox to sql select stateme"
- Previous message: Hermit Dave: "Re: ASP and ASP.NET question"
- In reply to: Hermit Dave: "Re: Problems with codebehind and inherits"
- Next in thread: Hermit Dave: "Re: Problems with codebehind and inherits"
- Reply: Hermit Dave: "Re: Problems with codebehind and inherits"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
