~masterurl/default.master / 2000 item limitation

Aug 22, 2008 at 2:34 AM
Since the Dynamic token "~masterurl/default.master" is not replaced until run time - what is the recommended practice for design time layout of pages?

On a side note, started reading the documentation tonight - found the "Design of the Training Management Application | Architectural Decisions | SharePoint Lists versus Database Tables" and the 2,000 item limitation to be very valuable (important) to know; the link to performance test excellent information!  Particularly when it can take 30 to 80 seconds to delete a record....   Data has a way of accumulating rapidly and it would be bad to figure these things out when your sitting at the 3,500 mark (and still growing).  

Where Training Management requirements are covered under lists will there be something on the horizon for those of us that will have to store data in a custom database?

Aug 22, 2008 at 4:01 PM
Edited Aug 22, 2008 at 4:04 PM

yeah, we know that there is a definite limitation there with using the default.master page. this is something we're looking into to see if there was an easy way of doing. one workaround would be deploy the solution and then use sharepoint designer. not a very good solution, but if the look and feel was critical, you could use this method.

we currently don't have a use case where we're actually accessing a custom database. but you can still follow the repository pattern we're using for the accounting management stub included in the reference implementation. You'll notice that inside the AccountingManagement project, there is a dataset class that populates itself with dummy data. you can you use the same approach, but instead call out to a real data base. for our reference, we did not want to include any database scripts and such for ease installation.