Visual Web Developer 2005 Express

Re: The name xxx Does Not Exist in the Current Context

MargaritaRosa — Sat, 14 Nov 2009 22:04:53 GMT

Thank you jcevans this worked for me

Re: The name xxx Does Not Exist in the Current Context

sumanabk — Thu, 29 Oct 2009 16:15:43 GMT

Thank you so much for this post. I spent a good deal of time trying to figure out the problem before

I check on the forums. How silly of me..hehee..I had the back up copy too. Once I excluded everything

else worked fine. :)

Re: The name xxx Does Not Exist in the Current Context

UptownGirl — Thu, 08 Oct 2009 10:57:16 GMT

Read all the entries about duplicates in back up files and thought that's embarressing and was certain that wasn't my problem!

Do a find of the entire project to make sure!! Even though the name in the solution explorer is different, it doesn't change it in the code behind file.

Re: The name xxx Does Not Exist in the Current Context

ravensensei — Fri, 28 Aug 2009 15:03:14 GMT

the other thing I noticed after wrestling with some of the suggested solutions is that if I don't open it as a project and I open it as a website in VS2008, it runs fine.

Re: The name xxx Does Not Exist in the Current Context

CodePartizan — Thu, 27 Aug 2009 17:38:41 GMT

Well, this problem seems to have a multitude of problems and solutions. Here's another one that may be indicative of others and hasn't been mentioned yet.

If you add a control IN something.aspx where something.aspx.designer.cs also exists, you have to add the control in something.aspx.designer.cs in the following manner

protected global::System.Web.UI.WebControls.Label labelName;

of course replacing the control type with what you need.

(at least this works for me on VS2005 SP1)

Cheers,

Partizan

Re: The name xxx Does Not Exist in the Current Context

hellobiswa2001 — Thu, 27 Aug 2009 14:29:26 GMT

The id of the lbl cotrol must be different therefor it shows the error, to find this go to the code behind page and type the lebel name , it must nit be displayed..

Re: The name xxx Does Not Exist in the Current Context

jcevans — Wed, 26 Aug 2009 03:05:39 GMT

Hi,

I was correct, same problem but for a totally different reason. So, incase someone else runs into this issue, I will share what I learned.

I was on the right track that the issue was due to the FileUpload control being inside the DetailsView Control. This made it so that my code could not directly access the FileUpload. But, i was wrong, i could not fully qualify the name of the control to access it like I used to in VB (VB2 through VB6). I needed to use the FindControl Method. For this, in my code behind, I created a new Control of the type FileUpload and set it equal to the one in my web page. Here is the csharp code i used

FileUpload FileLogo2Upload = (FileUpload)dvEventInformation.FindControl("fupEventLogo");

The syntax for including the control type in ( ) seemed a bit odd to me, but it works.

Now, in my code behind, whenever I needed info about the original control, I accessed it from FileLogo2Upload

I also had RadioButtons in the template in the DetailView, so I created a new control for each of them, using Find Control so i could access the info from the new control to see which was checked.

Hope this helps someone

Jon

Re: The name xxx Does Not Exist in the Current Context

jcevans — Wed, 19 Aug 2009 05:23:56 GMT

Well, I am getting the same error message, but for a different reason.

- I tried the first suggestion above, change the build options. That did not work.

- I do not have any other copies of pages with the same names, so that rules that out.

I am reasonable certain my problem is because the upload control i am using (the control that generates the error message) is buried so far down in the templates of my GridView that simply putting the control name in the code behind does not fully address it. When i put the fileupload, with this name outside of the GridView it works fine. But, when it is in the InsertItem template of one of the Fields, it generates this message.

I am hoping i just need to learn how to address the control properly in the code behind. Perhaps

instead of

fupEventLogo.enabled = true;

I need something like

gvEventInformation.Field6LogoUploadFilename.InsertItemTemplate.fupEventLogo.enabled = true;

or close to that. (This example does not work, but i'll bet it is moving in the right direction!)

I will just keep trying variations until I get it or i successfully address in the controls collection

If you have any suggestions, i would love to hear them!

Jon

Re: The name xxx Does Not Exist in the Current Context

hellowahab — Mon, 17 Aug 2009 05:47:19 GMT

Let see if it works for me!

Re: The name xxx Does Not Exist in the Current Context

hellowahab — Mon, 17 Aug 2009 05:41:23 GMT

Let see if it works for me!

Re: The name xxx Does Not Exist in the Current Context

jtaylorwehco — Wed, 01 Jul 2009 20:54:45 GMT

Brad,

I found out that if you rename the .aspx and the .aspx.cs file, rebuild web site, and rename the files back to the originals, the error goes away.

- jtaylorwehco

Re: The name xxx Does Not Exist in the Current Context

Ramya N — Wed, 13 May 2009 14:00:12 GMT

Check if you are pointing the same code behind file in two different apsx forms, i found this answer in another forum and solved my problem, when faced similar one.

Re: The name xxx Does Not Exist in the Current Context

konic — Thu, 07 May 2009 00:24:20 GMT

Gewgala:
Do you clean your project prior to building it?

I cleaned project and deleted all folders in the ..\roor\" folder.
And still have to use casting just to be able to compile the code.
...
P.S. OK, the mystery is solved. By mistake I deleted Default.aspx.designer.cs file,
which contains definitions of all class members.

Re: The name xxx Does Not Exist in the Current Context

Gewgala — Wed, 06 May 2009 23:39:43 GMT

Do you clean your project prior to building it?

Re: The name xxx Does Not Exist in the Current Context

konic — Wed, 06 May 2009 21:07:27 GMT

OK, this is not the whole picture.
As for me (VS2005), I had only one pair of Default.aspx and Default.aspx.cs
just for some testing purpose. It worked OK until certain moment.
I did something and since then started to get this compilation error.
Yes, casting thing like:
Label lb = (Label)Page.FindControl("form1")... does work, but nothing else.
And then by accident I discovered that VS2005 by default generates DLLs
and put them in some folder like: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\ccd7038d\1778aef7\assembly\dl3\8d7ee5d1\de6c8a4c_8acec901\ (!?)
Maybe that was because I did not deploy my site(pages) onto the server.
Anyway, the point is that sometimes DLLs are not rebuilt, and
I found the whole bunch of these DLLs under the ..\root\ folder!
Can anyone comment on this?