Premium Flight & Charter Packages

Accommodation stories highlight the profound impact of where we live, ranging from desperate, long-term temporary housing to the relief of finding stable, specialized care or community, such as in.

These personal narratives often involve overcoming crises like homelessness, navigating tight student housing, or finding "home away from home

Description

It looks like you are running into the classic ASP.NET WebForms designer disconnect. Coming from an MVC Core environment, these sudden cascading errors can feel like a jump scare.

When every single control suddenly "does not exist in the current context," it almost always means Visual Studio has lost the link between your frontend markup (create-tour.aspx) and your code-behind (create-tour.aspx.cs), or a background compilation error is preventing the parser from reading the controls.

Here is how to fix this, starting with a specific naming mismatch in your code that might be triggering the cascade, followed by the standard WebForms connection fixes.

1. Fix the Control ID Mismatch
There is a naming mismatch between your markup and code-behind that is causing at least one fatal error.

In your create-tour.aspx.cs file, inside the ddlcategory_SelectedIndexChanged method, you are attempting to clear an HTML editor:

C#
else
{
dvServiceDescription.Visible= false;
lblserviceDescription.Text = "";
ServiceDescp.Html = string.Empty; // <-- The issue is here[cite: 2]
}
However, in your create-tour.aspx file, the ID for that DevExpress control is actually declared as ExtraServiceDescp:

HTML

The Fix: Change ServiceDescp.Html = string.Empty; to ExtraServiceDescp.Html = string.Empty; in your code-behind. Sometimes, fixing a hard compiler error like this forces Visual Studio to re-parse the file and restores IntelliSense for the rest of the controls.

2. Check the @Page Directive (CodeFile vs. CodeBehind)
If fixing the typo doesn't restore the other controls, the issue lies in how the page is wired up.

At the top of your ASPX file, your @Page directive uses CodeFile:

HTML
<%@ Page Title="Create Tour" Language="C#" MasterPageFile="~/admin/manage/cpx.master" AutoEventWireup="true" CodeFile="create-tour.aspx.cs" Inherits="CreateTour" ValidateRequest="false" %>[cite: 1]
CodeFile is meant for older Web Site Projects (where ASP.NET compiles the code dynamically at runtime).

If your project is actually a Web Application Project (which requires pre-compilation and uses .designer.cs files), this attribute needs to be changed to CodeBehind.

The Fix: Try changing CodeFile="create-tour.aspx.cs" to CodeBehind="create-tour.aspx.cs"[cite: 1].

3. Regenerate the Designer File
If you are working within a Web Application Project and the create-tour.aspx.designer.cs file is missing, corrupted, or simply out of sync, your code-behind won't know the controls exist.

The Fix:

Right-click on create-tour.aspx in the Visual Studio Solution Explorer.

Select "Convert to Web Application".

This forces Visual Studio to scan your markup and regenerate the .designer.cs file, instantly restoring all the control definitions.

4. The "Turn it off and on again" Approach
If the files are linked correctly but Visual Studio's cache is just corrupted:

Save all your files.

Go to Build > Clean Solution.

Close the .aspx and .aspx.cs tabs.

Go to Build > Rebuild Solution.

Reopen the files.