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.:
Chris Boyd
If you have a VBA macro that worked in Project 2007 and doesn't work in Project 2010, here are some things to".
Note: The September update of the Project 2010 SDK includes an update of the Project 2010 VBA Help file for local use., Project Support.
This is a little late, I missed that I didn’t post this. Q&A and demos from the March 12th webcast.
regsvr32 /u C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\shfusion.dll)
For simple information discovery - we have just published a Project 2010 Demand Management resource center that centralizes all information around Demand Management and Portfolio Strategy into one single location.
Many of included links include pure developer resources. We have decided not to fragment the resources between TechNet and MSDN – that’s why you might find also developer-related link to MSDN content in the above TechCenters.
Many of included links include pure developer resources. We have decided not to fragment the resources between TechNet and MSDN – that’s why you might find also developer-related link to MSDN content in the above TechCenters.
This new resource center is the third dedicated resource center for Project 2010 – the full list below:
· Demand Management for Project 2010 -
· Business Intelligence for Project 2010 -
· Upgrade and Migration to Project 2010 -
These centers are part of the Project Server 2010 TechNet TechCenter and their concept is to collect relevant information in one place and to give end-to-end information from getting started quickly to deep dive.
Q: Do I have to have a special product of flavor of Project Server 2010 to get the Demand Management and Portfolio Strategy functionality?
A: All you need to have is Project Server 2010 – all included ready when you need it. You are probably referring to the 2007 release and Project Portfolio Server 2007 that was a standalone product used in conjunction with Project Server 2007 to manage full project life-cycle from initiation through selection to planning and managing the project.
Q: I’m using the Project Portfolio Server 2007. Is there any migration path to Project Server 2010?
A: Yes – there is. Please visit the Upgrade and Migration to Project 2010 - that has a whole section dedicated to migrating from Portfolio Server 2007..
Microsoft EPM University offers.!
The Project 2010 SDK includes a general discussion about updating applications developed for Project Server 2007 to run with Project Server 2010. Because the PSI in Project Server 2010 is a superset of the previous PSI, many ASMX-based applications can run unchanged on a Project Server that uses only Windows authentication -- but all require testing before deployment on Project Server 2010!
The Project Server Programmability page includes the Porting Applications Built for Project Server 2007 section, which links to the Migration and Compatibility of Custom Solutions section in the Overview of WCF and the PSI. In addition to the information on those pages, applications for multi-authentication installations of Project Server 2010 must be updated to handle forms-based and Windows-based authentication in the Claims environment of SharePoint Server.
The ASMXLogon_MultiAuth sample in the recent Code samples from the Project 2010 SDK webcast blog post provides an example, using the information in the Using Claims Multi-Authentication discussion in the Prerequisites for ASMX-Based Code Samples article of the SDK.
Even if your older application works on Project Server 2010, and you use only Windows authentication, it is a good idea to update the web service (ASMX) references and recompile, as described in Migration and Compatibility of Custom Solutions .
--Jim
The
The SharePoint 2010 developer conference presentation files are available in PowerPoint and XPS format. They include developer presentations for integrating with Office 2010 clients. See SharePoint 2010 Presentations: Developer Conference Session Files.
Phil Smail has this great code snippet for providing better error handling with regards to checked out resources:
While working with the PSI I wanted to check out a number of resources. Obviously the situation can arise where some of those resources are already checked out and I wanted to report that information to the client.
Unfortunately the PSClientError object only gives you information that there were resources already checked out but not which ones were checked out. The data is contained with the XML for the Exception so I wrote a helper function to extract this information out
The output from the code looks like the following:
The code is as follows:
using System;
using System.Collections.Generic;
using System.Text;
using System.Net;
using System.Web.Services.Protocols;
using System.Xml;
namespace GetError
{
class Program
{
private const string RESOURCESWEBSERVICE = "/_vti_bin/PSI/Resource.asmx";
static GetError.ResourceWsc.Resource Resource = new GetError.ResourceWsc.Resource();
static void Main(string[] args)
{
String PWAURL = args[0];
Resource.Url = PWAURL + RESOURCESWEBSERVICE;
Resource.Credentials = CredentialCache.DefaultCredentials;
Guid[] restypeGuids = new Guid[2];
//Change these GUIDS to res Guids in your system
restypeGuids[0] = new Guid("{f461c3f7-e0c9-414f-ae1a-41abe862f709}");
restypeGuids[1] = new Guid("{4e5d7702-7748-4a18-bc5d-7beef7004188}");
Console.WriteLine("Trying to check out resources");
try
{
Resource.CheckOutResources(restypeGuids);
}
catch (SoapException ex)
{
String tempxml = ex.Detail.InnerXml;
ExtractError(tempxml);
}
Console.ReadLine();
}
static void ExtractError(String xmlstr)
{
XmlDocument doc = new XmlDocument();
doc.LoadXml(xmlstr);
foreach (XmlNode node in doc.DocumentElement.FirstChild.ChildNodes)
{
String ErrString = "";
if(node.Name.Equals("item"))
{
//We know its one error
XmlNode n = node.Attributes.GetNamedItem("value");
ErrString = "Error: Resource - " + n.Value;
XmlNode childn = node.FirstChild;
if (childn.Name.Equals("error"))
{
XmlNode no = childn.Attributes.GetNamedItem("name");
switch (no.Value)
{
case "CICOAlreadyCheckedOutToYou":
ErrString += " Resource already checked out to you";
break;
case "CICOCheckedOutInOtherSession":
ErrString += " Resource checked out in another session";
break;
case "CICOCheckedOutToOtherUser":
ErrString += " Resource already checked out to another user";
break;
}
}
}
Console.WriteLine(ErrString);
}
}
}
}
The.
Great attendance – thank.
Jan
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:.
Caution
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.
You can also search MSDN for PWA ribbon. The article is at the top of the list. did two Project 2010 sessions at TechEd Europe – Christophe (thanks!) posted the decks on SkyDrive here as he mentioned here
We have also shot two short videos on the 2010 news for Developers and IT Professionals as mentioned here.
Happy holidays!.
Presenters: Steven Haden, Senior Consultant, Microsoft Corporation and Olivier Laymand, Senior Consultant, Microsoft Corporation.
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.
Issues:
· 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.
Christ