Blog de Eduardo Osorio Armenta

The meta:progid attribute on the Page directive is necessary if the page will ever be opened in SharePoint Designer. You should include this as site pages are supposed to support customization and thus, be opened in SharePoint Designer. If you don't want to allow pages to be opened and customized in SharePoint Designer, then you should do that through permissions, not at the page level. Using ASP.NET 2.0 Code Behind Files in SharePoint v3 Sites SPFile.ProgID gets a string that identifies the application in which the file was created. That's all the meta:progid is about. It's a identifier for SharePoint and you probably should not use other attributes, they might cause run-time error. Ref: msdn forum thread explanation

Serie de Webminars gratis que dará el MVP Asif Rehmani User Interfaces of SharePoint 2010 (level 100) Make the Best use of SharePoint Designer 2010 (level 200) How and where to deploy InfoPath 2010 Forms (level 200)

SharePoint Developers MSDN Webcast: SharePoint Server 2010 (Part 1 of 8): What's New for Developers (Level 100) MSDN Webcast: SharePoint Server 2010 (Part 2 of 8): Developing Rich Solutions in Silverlight (Level 400) MSDN Webcast: SharePoint Server 2010 (Part 3 of 8): Customizing Search Results (Level 200) MSDN Webcast: SharePoint Server 2010 (Part 4 of 8): Building Business Applications with Silverlight 4 and SharePoint 2010 (Level 100) MSDN Webcast: SharePoint Server 2010 (Part 5 of 8): Developing for SharePoint 2010 on Windows 7 (Level 100) MSDN Webcast: SharePoint Server 2010 (Part 6 of 8): Developing with the New User Interface Features in SharePoint 2010 (Level 100) MSDN Webcast: SharePoint Server 2010 (Part 7 of 8): Developing with SharePoint 2010 Sandboxed Solutions (Level 100) MSDN Webcast: SharePoint Server 2010 (Part 8 of 8): Developing with Data Technologies in SharePoint 2010 (Level 100) Note: SharePoint Webcasts from Microsoft PDC 2009: SharePoint S...