mandelbrot Posted March 14, 2007 Posted March 14, 2007 Dear All, Could anyone tell me what the, apparently unused, designerPlaceholderDeclaration is used for, please? Microsoft seem to want us to leave it intact, but I've tested code with it included and excluded, and it doesn't seem to make the slightest bit of difference... Many thanks in advance Paul. Quote
Leaders snarfblam Posted March 14, 2007 Leaders Posted March 14, 2007 Just venturing a guess, here, but judging by the name designerPlaceholderDeclaration, I would say that this is a place holder to support the designer. I don't know if there is any more signifigance to it, because I don't program with ASP.NET, but I would guess its just there to help the designer sort things out (which is why it woudn't make a difference if it is excluded in the end product). Quote [sIGPIC]e[/sIGPIC]
mandelbrot Posted March 15, 2007 Author Posted March 15, 2007 Well doesn't that strike you as rather odd, however, bearing in mind that the Windows development side of things doesn't require a placeholder?... Also, I've tested the designer both with it and without it, and there seems to be no difference either way. Quote
Leaders snarfblam Posted March 15, 2007 Leaders Posted March 15, 2007 Like I said, it was a guess. Just curious, does the designer re-generate the placeholder when the file is re-opened? Quote [sIGPIC]e[/sIGPIC]
mandelbrot Posted March 15, 2007 Author Posted March 15, 2007 It doesn't appear to regenerate, or rather, in my limited manipulations of the page through the designer, it doesn't appear to. I did read something on MSDN explaining how to force FxCop to ignore the declaration, but can't find anything anywhere to explain exactly what it is used for. Oh well, never mind - I'll try writing apps with and without it and see what happens... Thanks for your help, Marble... Paul. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.