broken link between aspx file and aspx.cs file

anonymous_at_discussions.microsoft.com
Date: 05/17/04 

Date: Mon, 17 May 2004 05:53:50 -0700

It seems to have caught up with itself now - still, if you
want to criticise VS .NET - don't let me stop you ;) Any
theories about this glitch, I would love to know.

>-----Original Message-----
>I used 'save as' on my aspx.cs file, which broke the link
>between it and it's aspx file. Restoring everyting to
it's
>previous state and checking the 'codebehind' properties
of
>the aspx file have not fixed it. changing the namespace
>names also did not help - is this a known bug? Everything
>should be ok but it's not - any suggestions?
>
>Dan
>.
>

Relevant Pages

  • Re: BC30466: Namespace or type cannot be found - different approach!
    ... If you are using source file in the /code directory ... new components are added, compiles them. ... > Namespace MyTest ... > I now want to import this class into an aspx file. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: namespace not allowed in script code declaration block?
    ... > definition generated by ASP.NET from the ASPX file. ... > See how the namespace nests inside the class definition? ... >> public class ShowItemToCust ... >> int InItemId, string InOnlineId, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Global application Masterpages and Intellisense
    ... this is a known bug in Visual Studio 2005. ... Added a .master file with 3 contentplaceholder controls. ... Added an aspx file with the @Page directive parameter ... I couldnt get the intellisense work for my .aspx pages and the ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Bug In Visual Studio.NET
    ... If you don't stick the script tag into the aspx file, ... >> The Bug, ... >> inside it insert a field required validator and a textbox, ... >> on button click set the tables visible property to true. ...
    (microsoft.public.vsnet.general)
  • Re: broken link between aspx file and aspx.cs file
    ... Check the Init section of the code behind file and make sure the ... > previous state and checking the 'codebehind' properties of ... > the aspx file have not fixed it. ... changing the namespace ...
    (microsoft.public.dotnet.languages.csharp)