You searched for the word(s): userid:109004

More Search Options

RSS Available

• Re: Web forms designer problem after conversion

  The Visual Studio web designer doesn’t support hosting custom controls that extend from System.Web.UI.HtmlControls.HtmlControl, that probably lead to the NullReferenceException. Given the change to extend from System.Web.UI.WebControls.Panel, you should remove the DesignerAttribute specified (that points to ContainerControlDesigner) and use the default System.Web.UI.Design.WebControls.PanelContainerDesigner provided for the Panel. For controls explicitly/manually added to the Toolbox, any changes

  Posted to Migrating from Visual Studio .NET 2003 to Visual Studio 2005 (Forum) by ibrahimm on 3/17/2006

• Re: Web forms designer problem after conversion

  Do you've a callstack for this NullReferenceException? If not, could we get access to the migrated web project for further investigation? Visual Studio automatically instantiates toolbox items only for controls in an associated control library project (present within the same solution). However, it doesn't automatically create toolbox items for controls exposed from code directories and other Bin or dependent assemblies. Thanks, - Ibrahim

  Posted to Migrating from Visual Studio .NET 2003 to Visual Studio 2005 (Forum) by ibrahimm on 3/16/2006

• Re: VS2005 HTML page slowdowns and freezeups

  Could you please try the following and let us know of any corresponding perf impact: - Turn off HTML validation - Turn off auto save and recovery (under Tools | Options | AutoRecover) - Turn off HTML pretty formatting (under Tools | Options | Text Editor | HTML | Format) - Close the property grid. - Close any anti-virus software. Thanks! - Ibrahim

  Posted to Visual Studio 2005 (Forum) by ibrahimm on 2/20/2006

• Re: Adding custom control from toolbox crashes VS 2005 - any ideas?

  This would cause a StackOverflowException , since the custom control invokes RenderControl from its RenderContents override. webcontrollibrary2.dll!WebControlLibrary2.TrackDropDownList.RenderContents(System.Web.UI.HtmlTextWriter output = {System.Web.UI.Design.DesignTimeHtmlTextWriter}) System.Web.dll!System.Web.UI.WebControls.WebControl.Render(System.Web.UI.HtmlTextWriter writer = {System.Web.UI.Design.DesignTimeHtmlTextWriter}) System.Web.dll!System.Web.UI.Control.RenderControlInternal(System.Web

  Posted to Web Forms (Forum) by ibrahimm on 2/10/2006

• Re: CompositeControl descendants do not appear in ToolBox - bug?

  This is a known bug in Whidbey when automatically creating such toolbox items derived from a base abstract class. A workaround for now would be to explicitly add/pick these controls using the "Choose Toolbox Items" dialog. Thanks! - Ibrahim

  Posted to Visual Studio 2005 (Forum) by ibrahimm on 1/30/2006

• Re: Finding Control at a location (x,y) in javascript...

  document.elementFromPoint returns the HTML element for the given client coordinates. http://msdn.microsoft.com/library/default.asp?url=/workshop/author/dhtml/reference/methods/elementfrompoint.asp - Ibrahim

  Posted to Visual Web Developer 2005 Express (Forum) by ibrahimm on 12/6/2005

• Re: Problem is displaying my control properties in Properties window

  The Visual Studio property grid only displays the public, browsable properties associated to the selected object(s). Since the above referenced objects are not in the inheritance chain, you could wrap and expose such contained properties from the main control. - Ibrahim

  Posted to Hosting Open Forum (Forum) by ibrahimm on 11/28/2005

• Re: Associating the Masterpage.master with the Default.aspx page when building a website

  In Default.aspx, make sure to remove the HEAD and BODY tags, since all contents must be contained within <asp:Content> controls. In other words, content pages should have only instances of the <asp:Content> control that appropriately replace the corresponding default master content. Please refer to the following MSDN article for more detailed information on Master-Content pages: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/html/masterpages.asp Thanks, - Ibrahim

  Posted to Visual Web Developer 2005 Express (Forum) by ibrahimm on 11/26/2005

• Re: Associating the Masterpage.master with the Default.aspx page when building a website

  All properties marked as "read-only" are denoted in the property grid with a disabled (greyed-out) rendering. However, the corresponding attributes could indeed be edited/set in source view, even if unavailable in intellisense & validation identifies it as an invalid attribute (say, r/o properties exposed by server controls). The only reason to mark MasterPageFile as r/o in design view is because of the lack of support to represent such changes in design view. Given this, I agree that there could

  Posted to Visual Web Developer 2005 Express (Forum) by ibrahimm on 11/23/2005

• Re: VS problem with MasterPage set in Web.Config

  The designer in Visual Studio 2005 doesn't support Master page file associations defined in web.config. A reasonable design-time only workaround would be to add an empty MasterPageFile attribute (MasterPageFile="") to the Page directive. Although this doesn't lead to "true" Master-Content based intellisense, validation and preview of the existing/default Master content, it should, say, provide intellisense for <asp:content> tags along with a design-view experience for any customized content

  Posted to Visual Studio 2005 (Forum) by ibrahimm on 11/23/2005