Microsoft MVP Logo

    <p>[via <a href="">FitzBlog</a>]</p>
    <p>He talks about FrontPage&rsquo;s importance in <a title="" href="" target="_blank">SharePoint</a> v3 and why ghosting isn&rsquo;t as much of a problem in the new version&hellip; some thoughts:</p>
    <p>I am still not sold on why FrontPage is the development tool over VS <a title="" href="" target="_blank">.NET</a>.&nbsp; My understanding is VS.NET is the central IDE of choice.&nbsp; The only off-shot I&rsquo;ve seen from this is SQL 2005 which uses the VS.NET framework, but it has it&rsquo;s own separate version.&nbsp; I can buy into that and understand why.&nbsp; But why FrontPage?&nbsp; Yes, this app is better than it used to be.&nbsp; But why can&rsquo;t we have something like an add-in to deal with SharePoint sites like we do with Web Parts, <a title="Microsoft Content Management Server" href="" target="_blank">MCMS</a>, and InfoPath just to name a few.&nbsp; I don&rsquo;t buy it&hellip; I don&rsquo;t like it&hellip; and I don&rsquo;t understand it.&nbsp; I&rsquo;m going to dig on this one&hellip; <a href="">like the O12 UI</a>, the more you understand the &ldquo;why&rdquo; about a decision, the more you understand and potentially like it.</p>
    <p>The other thing Fitz touched on is ghosting.&nbsp; It&rsquo;s arguably one of the biggest issues in SharePoint&hellip; something that <a title="" href="" target="_blank">MSFT</a> has failed to really get out in front and educate developers/implementers of the <a href="">dangers of FrontPage, SharePoint, and the effect unghosting a page has on a site</a>.&nbsp; The implementation of ASP.NET 2.0&rsquo;s caching engine and master pages should help quite a bit.&nbsp; I&rsquo;m sure most of the stuff we want to accomplish can be done using the ASP.NET 2.0 engine/features/master pages&hellip; I was hoping to see ghosting disappear in SharePoint v3&hellip; oh well&hellip; maybe it&rsquo;s mitigated enough.</p>
    <p>&raquo; <a href="">Ghosting, Schmosting!</a></p>
Comments powered by Disqus