Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>UPDATE (1/21/2010): Good news: after more investigation, it turns out that this issue was fixed in VS2010. The fix was made post Beta 2, so it will be part of the next public build. I don't have an exact date, but it should not be too far out.</p> <hr> <p>Yes, I seem to recall this coming up before, and indeed some scenarios involving nester master pages and CompilationMode="Never" are broken.</p> <p>Looking at an old mail thread, I think it only happens for certain combinations. It looks like it’s broken for (where NoCompile means compilationMode=never):</p> <ol> <li>NoCompile Page / Compile Master / NoCompile Master</li> <li>NoCompile Page / NoCompile Master / Compiled Master</li> </ol> <p>At the time, we did not fix this because the fix was non trivial and the scenario is not common.</p> <p>Note that when it comes to NoCompile pages, most of the benefit is using it for end node aspx pages, and not master pages. Generally, NoCompile pages run a bit slower than compiled pages. Their benefit is that they don't have a first time compile hit, and they use less memory. Also, they can be fully unloaded under memory pressure. That's why they make good sense when you have a super large number of end point pages (Sharepoint uses them). But on master pages (where most apps only have a small number shared by many pages), that benefit would be minimal. And of course you can't have code in NoCompile pages, which is the main reason that few people use them.</p> <p>So the quick summary is: you're right, it's a bug! :) And the recommended workaround is to avoid CompilationMode=never for master pages.</p>
    singulars
    1. This table or related slice is empty.
    1. POASP.NET nested masters pages with CompilationMode="Never", a recepie for disaster? Bug in ASP.NET?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDavid Ebbo
    1. USDavid Ebbo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POASP.NET nested masters pages with CompilationMode="Never", a recepie for disaster? Bug in ASP.NET?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COIn the ASP.NET road map, are there any plans to fix this? Our use case involves really large amount of master pages, which are treated as end points as in SharePoint. I've sent you an email with details.
      singulars
      1. PO
      1. USIvan Zlatanov
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload