Project Programmability

This blog focuses on customizations and programming for Project Web App, Project Server, Project Professional and Project Standard. Includes User Interface (UI) customizations, Project Server Interface (PSI) and Visual Basic for Applications (VBA) Programming. It also covers Business Intelligence.

  • Project Programmability and Business Intelligence

    New SharePoint 2010 book for developers


    MS Press has just published Inside Microsoft SharePoint 2010, which will also be very useful for Project Server 2010 developers – since, as we all know, Project Server is an application service in SharePoint Server, PWA is a SharePoint application (a somewhat restricted one with a few specialized Project Server Web Parts thrown in), and project sites are pure SharePoint (with some custom lists).

    Although Chapter 11 on Creating and Developing Workflows primarily discusses SharePoint Designer, which we can’t use for Project Server workflows, it does provide a good overview of workflow concepts.

  • Project Programmability and Business Intelligence

    Security in Project Server 2010–What about Custom Permissions?


    SharePoint Server 2010 handles user authentication through claims processing, which is a new feature for SharePoint and Project Server. SharePoint handles both Windows authentication and Forms authentication for Project Server users. For authorization, you can use the ReadResourceAuthorization and SetResourceAuthorization methods in the Resource service of the PSI. Because you probably don’t often change security authorization settings for users, you would normally go to the Manage Users page in Project Web App to select a user and set the global and category permissions.

    The Security business object in Project Server (with programmatic access through the PSI Security service) manages security groups, categories, templates, and the global Project Web App permissions. The Security service can add existing permissions or remove permissions from the sets available for Project Server users. However, the Security service does not have a method for creating a custom permission. For example, if you created a Project Server extension that updates a Siebel CRM system, you might want a custom permission that enabled users to use that extension.

    In Office Project Server 2007, you can create custom global and category permissions by modifying security tables in the Published database. Custom permissions show in the PWA lists of permissions, where Project Server administrators can secure the 3rd-party extension the same way they secure other Project Server features. The Walkthrough: Creating and Using Custom Project Server Permissions article is the only SDK example where an exception is made for changing the Published database. 

    NOTE:  The Project team would like some feedback on the importance of custom permissions. If you need to create custom permissions in Project Server, please respond to this post.

     In Project Server 2010, that process for creating custom permissions still works as it did in Project Server 2007. In future versions of Project Server, no modifications to tables in the Published, Draft, or Archive databases will be supported. Custom permissions and secure links that rely on table modifications still work in Project Server 2010, but that process will be deprecated. As an alternative, you may have to create your own user interface to manage custom permissions, or use claims augmentation in a custom application. For more information, see Claims Provider.


    For more information about Project Server security, including a discussion of global and category permissions, see the Project Server Security Primer in the Project Server 2007 SDK and Security and protection for Project Server 2010 in TechNet.

  • Project Programmability and Business Intelligence

    Who builds the Project 2010 Solution Starters?


    Some of you are asking how and who builds the Solution Starters.

    The Solution Starter specifications were done by the same group of people who design new components of Microsoft Project – the Program Managers inside of Microsoft. The specifications (“specs”) were then handed off to external company who coded, tested and released them into the MSDN Code Gallery.

    The company is called Internet Commerce Corporation (ICC)

    ICC is one of the first companies that started working with Microsoft Project Server 2010 as part of Microsoft's TAP program and continues to gain experience being involved in the development of a number of solution starters for Project Server 2010. Since then, ICC has built strong expertise in building EPM solutions based on the Microsoft Project Server 2010 Platform.

    Major focus areas in Enterprise Project Management for ICC are:

    • EPM Solution Implementation
    • Project Server 2010 deployment and configuration
    • Project Server 2010 customization and custom report development

    If you plan to do a coding project for Project 2010 and you need great developers with vast experience, feel free to consider them too!


  • Project Programmability and Business Intelligence

    A chart for all (Office) reasons


    The Microsoft Office 2010 Developer Map is now available for download. You can view it on a big monitor, or print it full-size on a 3-foot x 2-foot page. It shows the full stack of Office desktop and server applications, technologies, and tools – including mobile and cloud apps.

    For Office 2007, see the Microsoft Office 2007 interactive Developer Map. The Silverlight-based interactive map for Office 2010 is not yet available.

  • Project Programmability and Business Intelligence

    Scrum. Scrum? Scrum Solution Starter for Project 2010!


    Yes – it’s here for few weeks now - Details are here.

    Thanks for all the comments, keep them coming!

  • Project Programmability and Business Intelligence

    Have you tried the Project 2010 Solution Starters yet?


    Looking for tools and way to easily get started building customizations by reusing and modifying code from an existing?

    Then make sure to look at There’s plenty of related resources, including deep dive webcasts. If you have any questions – please check the related discussion.


  • Project Programmability and Business Intelligence

    Thinking about getting your certifications?


    In case you are thinking about taking one or more exams towards your certification - for example the following:

    You might appreciate the Microsoft Certification Pack voucher codes with Prometric -

  • Project Programmability and Business Intelligence

    Project 2010 SDK Update–January 2011



    The Project 2010 SDK is updated for MSDN online. See Project 2010 SDK Documentation. New topics include the following:

    There are also many new and updated descriptions in the Project Server API reference. Plus, the following PSI methods have new code samples, all based on WCF:

    Note:  The update is online only. The Project 2010 SDK Download is still the September 2010 release; the download will be updated within two months, to include the new code samples. For now, you can get the ProjTool sample here

  • Project Programmability and Business Intelligence

    How to: Modify the Ribbon in PWA


    Note:  For the updated article, see How to: Modify the Ribbon in PWA in the Project 2010 SDK. The attached file includes the complete Visual Studio 2010 solution.

    The attached file includes an article that shows how to develop and deploy a SharePoint feature that adds a Close Project button to the Project Details page in Project Web App. You can add a second feature to the same solution that removes, modifies, and disables several buttons and other controls on the Timesheet page, when timesheets are in the single entry mode. The code in the article is based on code samples by Adrian Jenkins and Maria Kouvlaki, Microsoft Corporation.

  • Project Programmability and Business Intelligence

    OLP Sample Code for Project Server 2010


    The Object Link Provider (OLP) in Project Server 2010 enables the management of the Project-specific lists in a project site (issues, risks, deliverables, documents, and custom lists) and integration of the SharePoint lists with Project Server. The OLP  has the same functionality as in Project Server 2007; however, you can use Windows Communication Foundation (WCF) to develop OLP solutions for Project Server 2010.

    The attached code ( is a preview of an example that uses the CreateWebObjectLinks method, to be published in the next update of the Project 2010 SDK. Before you run the sample application, perform the following steps:

    1. Use Project Professional 2010 to create and publish a project with at least one task.

    2. Use Project Web App to open the project site.

    3. Create at least one issue or risk in the Issues or Risks SharePoint list of the project site.

    4. Change the OLP constructor values according to your example.

    5. Add a web service reference to http://localhost/pwa/_vti_bin/Lists.asmx, and name the reference WebSvcLists.

    This example performs the following tasks:

    • Verifies that the project, task, and project site exist and gets their corresponding GUIDs.

    • Links a task and a SharePoint list item (in this case, an Issue).

    • Links a task and a generic object.

    • Gets the list of SharePoint items that are linked to a task and writes the contents of the ObjectLinkProvider dataSet dsLinkedObjects to an XML file.

    • Gets a list of generic items that are linked to a task.

    • Deletes the links to web objects.

    For more information about how the sample code works, see Procedures 1-6 in How to: Use the OLP to Link an Object to a Task.

  • Project Programmability and Business Intelligence

    Preliminary version of the Scrum Solution Starter for Project 2010 is available for download!


    We have published preliminary version of the Scrum Solution Starter for Project 2010 on MSDN Code gallery please participate actively in the Discussion to notify us about any issue you may encounter or post any feedback!

    This solution starter focuses on the Project 2010 desktop client, and on the individual Scrum team experience.

    Scrum is an iterative, incremental methodology for project management often seen in agile software development. Although Scrum was intended for management of software development projects, it can be used to run software maintenance teams, or as a general project/program management approach.

    There are 3 main items in Scrum:

    • Product backlog: A product backlog is dynamic—Items may be deleted or added at any time during the project. It is prioritized—Items with the highest priority are completed first. It is progressively refined—Lower priority items are intentionally course-grained.
    • Sprint backlog: A sprint backlog is a negotiated set of items from the product backlog that a team commits to complete during the time box of a sprint. Items in the sprint backlog are broken into detailed tasks for the team members to complete. The team works collaboratively to complete the items in the sprint backlog, meeting each day (during a daily scrum) to share struggles and progress and update the sprint backlog and burn down chart accordingly.
    • Burn down: The sprint burn down chart is a publicly displayed chart showing remaining work in the sprint backlog. Updated every day, it gives a simple view of the sprint progress. It also provides quick visualizations for reference

    Supported Scenarios:

    A Scrum Master wants to use Project for the basics of running a sprint, including:

    • Collecting and tracking status
    • Managing the product backlog
    • Managing the sprint backlog (and initial iteration planning)
    • Viewing a burn down chart
    • Easily exporting Scrum data to email/other apps


  • Project Programmability and Business Intelligence

    Project Server <—> TFS 2010 Integration (beta)


    The Visual Studio Team Foundation Server (TFS) group has released a beta version of the Feature Pack for integration of TFS 2010 with Project Server. The beta version is a “go live” release. If the user agrees to the pre-release license agreement, the Feature Pack can be installed and will be supported in a production environment. However, it is not the final release, and is still subject to change, so you should first test it in a non-production environment.

    Note   The TFS Feature Pack requires the Microsoft Visual Studio 2010 Ultimate edition, SP1, and TFS 2010 SP1. It can work with either Project Server 2010 or Project Server 2007.

    For an article in the Project team blog, see Announcing Visual Studio Team Foundation Server 2010 and Project Server Integration Feature Pack Beta.

    For an article that describes the major features, benefits, and installation of the TFS-PS Feature Pack, see Brian Harry’s blog: Portfolio Management: TFS <-> Project Server Integration in Beta.

    If you have worked with TFS, you know what a great advantage that is for large development projects – and even for small ones. You already know what an amazing tool Project Server is. The TFS-PS Feature Pack brings together the two best-in-the-world tools for team collaboration on development projects, and enables development-focused and project-focused people to keep working with the tool they know best and to truly combine forces.

  • Project Programmability and Business Intelligence

    The Beta of Visual Studio 2010 SP1


    See Announcing Visual Studio 2010 Service Pack 1 Beta for a download link. General availability will be Thursday, Dec. 9.

  • Project Programmability and Business Intelligence

    Project Server Cache Synchronization


    Microsoft Office Project Server 2007 and Microsoft Project Server 2010 internally manage cache synchronization by tracking revisions to major entities such as projects and maintaining records for deletions of those entities. Although the Draft, Published, and Archive databases in Project Server are not documented, and direct access to those databases is not supported, a basic understanding of cache synchronization in Project Server can be useful in determining issues of performance optimization. (This article was written by Patrick Conlan, Microsoft Corporation.)

    Warning:   The information in this article is applies only to the specified versions of Project Server, and is subject to change without notice.

    In Project Server 2007, we made a series of changes that were designed to improve the scalability and reliability of Project Server, especially when it is under usage stress. One of the most significant changes was the introduction of several caches, specifically:

    • Client side Active Cache, which creates the *.mpc files that Project Professional users can see on their client computers.
    • Server side Published, Statusing and Reporting SQL schema, which are used to store a project plan of record, enable simultaneous status reporting, and help to make server reporting easy.
    • Server side Archive SQL schema, which caches older data and enables fast administrative restore from the Archive database.

    The location of the master copy of data varies by content. Projects use the Draft database; most other data uses the Published database.

    The caches are synchronized during data movement operations such as the following:

    • Project Professional opens a project from Project Server.
    • Publishing a project, where data is copied from the Draft database to the Published database.
    • Publishing to the reporting database, which is implicit in publishing a project.
    • Many metadata operations move data within a database and between databases.

    We use a fairly complicated versioning scheme to work out what data needs to move as part of the synchronization. Some of you may have already worked out some of the versioning processes!

    Depending on the number of project managers who use Project Professional within an organization, there can be hundreds or even thousands of caches - one on every Project Professional desktop plus the caches in the SQL Server databases. Depending on when they were last synchronized, the caches can contain different versions of project entities.

    Each entity has a primary table that controls the entity version number. For example, MSP_Projects is the primary table for projects. When an entity is created and each time the entity is saved, Project Server uses the entity version to aggregate the edit session changes.

    Version Tracking Schema

    The following schema fragment from the MSP_Projects table shows the fields that are used to track changes at the project level:


    The REV_RANK and PROJ_CURRENT_REV_RANK fields are used to signal an archive restore. If synchronization shows a disparity of rank between caches, then Project Server performs a full resynchronization (in effect resetting the REV_RANK field with a revision = 0)

    The REV_NEXT_SEED field contains the next version number to be used for any changes. The PROJ_CURRENT_REV_COUNTER and MOD_REV_COUNTER contain the active version number. There are two numbers to enable us to see when the document was lasted edited by Project Professional or by another application.

    The CREATED_REV_COUNTER field is either 1 or 0, depending on how the project was created. When Project Professional creates a project, CREATED_REV_COUNTER = 1.

    Handling Deletes

    We had two options for handling deletes in the cache coherency model:

    • Flag the existing data as deleted (an update), or
    • Delete the data and record the deletion, so synchronization can propagate the deletion onward.

    Flagging would give better short term performance (less impact on SQL Server), but would quickly cause data bloat within the most important tables. We decided to use the second option of deleting the data and creating a record of the deletion.

    We use shadow tables to record delete operations for tables that are in the cache synchronization scheme. Shadow tables are very narrow tables that contain the minimum data needed to track deletes. Project Server updates the shadow tables when major entities are deleted.

    The following schema is for the project shadow table, MSP_PROJECTS_SHADOW.

    [PROJ_UID] [dbo].[UID] NOT NULL,
    [DELETED_DATE] [datetime] NOT NULL

    When a project is deleted, it uses just 28 bytes of data in a row of the MSP_PROJECTS_SHADOW table (16 bytes for the GUID + 4 bytes for the INT + 8 bytes for the DATETIME value), plus normal SQL Server page overhead.

    Administrators of Project Server installations that have a lot of data churn should maintain an active archive and delete policy to take advantage of the shadow tables and improve performance.

  • Project Programmability and Business Intelligence

    New SharePoint Developer Team Blog


    Because Project Server 2010 is deeply integrated with Microsoft SharePoint Server 2010, SharePoint is a key part of development for Project Server. The new SharePoint Developer Team Blog combines many SharePoint-related blogs into one. To subscribe, the URL is easy to remember:

  • Project Programmability and Business Intelligence

    ProjTool for Project Server 2010


    Note: For the updated article, see Using the ProjTool Test Application in Project Server 2010 in the Project 2010 SDK. The attached file includes the ProjTool application and the complete Visual Studio 2010 solution.

    The ProjTool test application was introduced in the Microsoft Office Project 2007 SDK. Many developers found it useful for creating, examining, and changing data by using the PSI on a test installation of Project Server, and checking actions by impersonating users on a test server. The 2007 release of ProjTool does not work correctly with Project Server 2010.

    ProjTool was originally developed by many different testers on the Project team. In the SDK release, the internal test code has been removed. The download that is attached to this post includes an update of ProjTool for Project Server 2010, along with a draft document on how to use ProjTool. The article and source code will be included in a future update of the Project 2010 SDK.

    The updated ProjTool uses the .NET Framework 3.5; all calls to PSI methods use WCF instead of the ASMX interface. ProjTool now works for Windows authentication, Forms authentication,  multi-authentication (both Windows and Forms on the same Project Web App port address), and impersonation on Project Server 2010.

    Here is an example screenshot from ProjTool, which shows part of the AssignmentDataTable in the ProjectDataSet for one project, after the user has changed the value of the ASSN_PCT_WORK_COMPLETE field in an assignment. When Update Project is clicked, ProjTool shows fields in all of the datatables that have changed as a result.


  • Project Programmability and Business Intelligence

    Free Resources for Developers


    Just in case you don't receive the MSDN Flash Newsletter, there are three top stories this week:

    Free eBook: Moving to Microsoft Visual Studio 2010

    Still using Visual Studio 2008? Oops, you said 2005? Maybe 2003? We're pleased to announce another free offering from Microsoft Press (336 pages).

    31 Days of Windows Phone 7

    Jeff Blankenburg is posting every day in October on Windows Phone 7 development. Check the topics he has covered so far.

    Watch PDC10, Live from the Redmond Campus, October 28 and 29

    Microsoft's Professional Developers Conference (PDC) is sold out, but you can still participate via the live broadcast, starting at 9:00 A.M. Pacific Time.
    Also: Attend a Microsoft PDC near you

  • Project Programmability and Business Intelligence

    New blog–Jan’s Project 2010 blog


    Dear all – I will continue posting developer-related information to this blog, but there was a lot of “other” content that would not fit perfectly here. So I have created a new blog on where I continue posting Project 2010 relevant information and top of mind thoughts Smile Few are there already Winking smile

    If you are interested, please add to your favorite RSS aggregator.



  • Project Programmability and Business Intelligence

    Project Momentum 2010 Barcelona, Spain —an EMEA customer and partner event



    You’re invited to Project Momentum 2010—EMEA, an EMEA customer and partner event, to be held in Barcelona, Spain on November 16 – 18, 2010.


    Key Highlights of Project Momentum 2010—EMEA:

    · Obtain unique insights from customers and partners into how Project 2010 delivers flexible work management solutions

    · Learn about innovative capabilities in Project 2010 that solve your organization's unique and specific needs

    · Share best practices and learn new ways to win in challenging business scenarios

    · Understand how to leverage your investments across related Microsoft technologies

    · 15+ in-depth breakout sessions across business and technical tracks

    · Hands on labs and product demonstrations

    · Thought provoking keynotes and guest speakers

    · Connect and collaborate with industry practitioners, partners, executives, technologists, and the Microsoft Project team

    Called the most significant Project release in more than a decade. Come learn what the buzz is all about.

    To register, please select the “register now” button below.

    Registration for this event is $75.00 (USD).

    clip_image012For more information about Project 2010, please visit

    See you in November! Project Momentum 2010—EMEA Planning Team |

  • Project Programmability and Business Intelligence

    Project 2010 at TechED Europe 2010


    As we announced earlier – Project 2010 will have a great presence at TechEd Europe 2010!

    Christophe has posted more session-related details today and you can check all the session on and start to build your session schedule using the schedule builder!

    Project 2010 Sessions

    • OFS201 - Application Lifecycle Management - Microsoft Project 2010 and Team Foundation Server 2010, Better Together
    • OFS306-IS - Project 2010 Development for SharePoint Developers With Real-World Examples
    • OFS224 - Project 2010 Demo, Demo, Demo - Overview for IT Professionals and Developers
    • OFS305-IS - Project 2010 Deployment And Upgrade - the theory, the myth and the best practices

    Project 2010 Hands-on Lab

    • OFS210-HOL - Project 2010 - End to End Project and Portfolio Management built on SharePoint 2010 – Self Paced Hands-on Lab

    Project 2010 Booth

    As usually we will have a Project 2010 booth staffed with the following experts ready to answer your Project 2010 questions:

    You can also look forward to the Project 2010 T-Shirts and USB keys with the Project 2010 Quick Start Training for offline viewing!

    Looking forward to see you all!


  • Project Programmability and Business Intelligence

    My VBA macro from Project 2007 doesn't work in Project 2010!


    If you have a VBA macro that worked in Project 2007 and doesn't work in Project 2010, here are some things to try.

    There are quite a few members from Project 2007 that are deprecated and hidden in Project 2010. Some of the hidden members still work as they did in Project 2007, some simply do nothing, and using some directly results in an error. If the macro relies on a hidden member that does not work the same way in Project 2010, you can get a variety of errors. For example, the Application.AnswerWizard property and the Office.AswerWizard object are both hidden -- and the AnswerWizard no longer exists. The following macro results in a run-time error 1004 in Project 2010:

    Sub GetAnswerWizard()
        Dim aw As Office.AnswerWizard
        Set aw = Application.AnswerWizard
    End Sub

     To see the hidden members, go the VBE, press F2 for the Object Browser, right-click in the Members pane, and then click Show Hidden Members. The hidden members are in a light gray font. VBA Help does not include documentation of hidden members.

    Check the macro for members that are hidden in Project 2010, and get documentation for any of those from Project 2007 VBA Help on MSDN. Then set a breakpoint to see whether the member does what is expected.

    If the macro does not use any hidden members, trace through the macro by using breakpoints, to see what is going on. Some members in Project 2010 have additional parameters. For example, if you specify a parameter by position, such as Method(,,,"Value"), the parameter could be in the wrong order. When you use only a few parameters in a method that has many, is often best to use named parameters, for example, Method MyParam:="Value".

    Note: The September update of the Project 2010 SDK includes an update of the Project 2010 VBA Help file for local use.

  • Project Programmability and Business Intelligence

    Where is the XML file for modifying the PWA ribbon?


    Some folks have asked about the pwaribbon.xml file and modifying the ribbon in PWA for Project Server 2010. The SDK article Walkthrough: Customizing the PWA Ribbon and Accessing the JS Grid includes that information, although the article can be overlooked if you are not concerned with the JS Grid control. Here is the introductory information in the article about the pwaribbon.xml file:

    Modifying the Project Web App Ribbon with an Elements.xml File

    The Server ribbon for Project Web App is defined in the pwaribbon.xml file in [Program Files]\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\PWARibbon\listtemplates. To modify the Project Web App ribbon, you can use a custom Elements.xml file to add, change, or remove tabs, groups, and controls in the ribbon. For general information about modifying the Server ribbon in SharePoint applications, see Server Ribbon XML.


    You should not modify the pwaribbon.xml file itself. Updates and service packs can replace the pwaribbon.xml file and overwrite your changes. Changes that you make in the pwaribbon.xml file are not supported.

    You can also search MSDN for PWA ribbon. The article is at the top of the list.

  • Project Programmability and Business Intelligence

    Recently updated Project 2010 Solution Starters


    Few months ago we have announced releasing of the Solution Starters for Project 2010. We are still committed to continue evolving them - and we will showcase many of them in the future version of our wonderful Project 2010 Demonstration and Evaluation Virtual Image.

    We have not only released the source code and the deployable package, but also number of WebCasts that introduce the functionality, but also conduct deep dive into the code.

    You can find many of the solution starters in the following location -

    Go ahead to check them out - if you encounter an issue or have a question, please post the issue or question into the related Discussions library and we will follow-up shortly. 


    What's new?

    • Bulk Import Tool - made to ease migration of data from Project Portfolio Server 2007, now enables to update existing project data with new data from PPS. For more information about PPS 2007 migration - please visit Upgrade and Migration Center on Microsoft TechNet.
    • Workflow Visualization Web Part  - we had this Web Part for some time, however we updated it with a newer version that mimics to certain extent the workflow visualization you know from our Project 2010 Demonstration and Evaluation Virtual Image. It's very smart as it builds the whole workflow visualization dynamically based on the pictures you provide and highlights the current workflow stage.
    •  Report Builder Tool - now pulls down some more project workflow related-data.

    Thanks to all who work hard on this - including Sam and ICC!


  • Project Programmability and Business Intelligence

    Converting COM add-ins to VSTO for 64-bit Office apps


    64-bit Office apps--including Project 2010--do not support COM add-ins, which are 32-bit. To use the 64-bit environment, COM add-ins must be ported to a 64-bit add-in by using the Office Development Tools in Visual Studio 2010 (often referred to as Visual Studio Tools for Office, or VSTO).

    There is no direct conversion tool for porting 32-bit COM add-ins to VSTO for 64-bit Office apps. The amount of time to port a COM add-in can vary greatly, depending on the functionality and Project version for which it was designed. A simple add-in designed for 32-bit Project 2010 might take a few hours; something like Solution Starter: Scrum for Project 2003 (although I haven’t done a port) might take several weeks and require a complete redesign, because it uses features that are no longer available in Project and Excel 2003 – and it was written in VB6.


    ·         VSTO in VS 2010 supports only Office 2007 and 2010.

    ·         Carefully check the types when you convert the code (int, long, etc.).

    ·         When doing the port, you can use compiler constants to make the code usable in both 32-bit and 64-bit Office apps. See Tables of VBA Object Model Changes for a VBA example, and for a comparison of types in VB and C#.


    See also (VBA-related, not specifically for add-ins) Working with VBA in Office 2010 (32-bit) and Office 2010 (64-bit).


    You might also want to check out Add-In Express 2010; see, for example, Converting existing Office COM add-in projects to Add-in Express.


  • Project Programmability and Business Intelligence

    September update of the Project 2010 SDK


    The September 2010 update of the Project 2010 SDK download and the MSDN online release are both published.

    They have the same URLs as previous releases:                                                                                             


    ·         SDK Online:

    ·         SDK Download:

    ·         Project Developer Center  

    What's New in the conceptual and how-to topics:

    Following are the major new and updated topics in the Project 2010 SDK, since the RTM release. There were a series of changes related to ASMX web services, Windows Communication Foundation (WCF) services, and claims authentication since the beta release. The Project 2010 SDK in the MSDN online library was updated in July; the last update of the SDK download  was in May. They are in sync again.


    Updates of RTM topics:

    ·         Using Formulas and Graphical Indicators with Custom Fields

    ·         Creating Lookup Tables and Enterprise Custom Fields

    ·         Custom Fields and the Reporting Database

    ·         Overview of WCF and the PSI

    ·         Walkthrough: Developing PSI Applications Using WCF

    ·         How to: Use Impersonation with WCF

    ·         Prerequisites for WCF-Based Code Samples

    ·         Developing Project Server Workflows

    o   How to: Install and Test a Project Server Workflow

    o   How to: Deploy a Project Server Workflow

    ·         Project Server Error Codes now includes a WCF-based code example for getting a list of errors.


    New conceptual and how-to topics:

    ·         Developing PSI Extensions

    o   Creating a PSI Extension for Project Server 2010

    o   How to: Create a PSI Extension to Read Custom Fields in the RDB

    ·         Developing Project Server Web Parts

    o   Walkthrough: Creating a Project Server Web Part with a JS Grid


    In addition, the Class Library and Web Service reference for the PSI has many updated type and member descriptions, and several new code samples for PSI methods.


    What’s New in the Project 2010 SDK download:

    ·         pj14SDK.chm is an HTML Help file that includes the same updated content that is online.

    ·         WINPROJ.DEV.hxs is an update of VBA Help that includes the latest changes in the VBA object model documentation. There are also instructions for replacing the VBA Help file shipped with the Project RTM release.

    ·         Managed code reference samples contains WCF-based solutions for code samples in the managed code reference for the following methods: QueueCreateProject, ReadCustomFields2, and ReadLookupTables. The solutions also use the WriteFaultOutput method for listing errors, which is described in the Project Server Error Codes topic.

    ·         Multi-authentication samples includes the ASMX- and WCF-based solutions for multi-authentication, which are described in the Prerequisites for ASMX-Based Code Samples and Prerequisites for WCF-Based Code Samples topics.

    ·         Project Guide Add-in shows how to use Project Guide files in Project 2010, with a custom ribbon tab. The sample code uses Office development tools in Visual Studio 2010.

    ·         PSI Extensions includes the Hello solution described in Creating a PSI Extension for Project Server 2010 and the ListProjects solution described in How to: Create a PSI Extension to Read Custom Fields in the RDB.

    ·         Web Parts includes two related Web Part solutions:

    o   ListProjects is described in Walkthrough: Creating a Project Server Web Part with a JS Grid.

    o   ListProjects_Sorting extends the ListProjects solution to implement column sorting in the JS Grid control.

Page 2 of 11 (255 items) 12345»