daniel
Mon Jan 17 17:01:01 CST 2005
You also will lose catalogs, such as the Web Part catalog at
http://localhost/_catalogs/wp/Forms/AllItems.aspx if you remove it from the
template.
I am planning on realeasing an article and SDK for site definitions in the
coming weeks... watch www.portalbuilder.org for details.
Daniel
"Daniel Larson (www.portalbuilder.org)" wrote:
> Hey Bil
>
> You can get that sucker pretty slim... but you start removing the ability to
> create content through lists and doc libraries when you remove those
> definitions. You should be able to get it down to just the default page and
> the onet.xml file if you want to go that far.
>
> I am currently working on a project where we've removed just about
> everything but I did opt to leave in the document library template, although
> we'll probably pull that.
>
> Sidenote: The question always comes up about where to put additional files
> that you may need in a site definition after creation... but after a little
> thought, that is why the _layouts application is there... you can add files
> such as RSS support, xslt files and whatnot in that directory....
>
> Daniel Larson
>
http://www.portalbuilder.org
>
>
> "Bil Simser [MVP]" wrote:
>
> > Anyone know how slim you can get the site definition down to? I'm trying
> > to build a sitedef with basically a single page and very little
> > configuration.
> >
> > Basically a wss starter that would create a valid site but nothing much
> > but a single page and some sharepoint properties. I've been trying
> > various approaches like taking the STS one and removing bits and pieces
> > but every once in awhile the whole thing blows up.
> >
> > I'm thinking something along the lines of just having ONET.XML and a
> > default.aspx page (and the WEBTEMPxxx.XML file) but not sure what that
> > looks like and what's mandatory as far as the schema goes (and it's a
> > PITA to keep resetting IIS to see if I have enough).
> >
> > Thanks.
> >
> > --
> > Bil Simser
> >
http://weblogs.asp.net
> >
> >
> >