Project Server Blogs

   1: namespace Microsoft.SDK.Project.Samples.QueueCreateProject

   2: {

   3:     class Program

   4:     {

   5:         [STAThread]

   6:         static void Main(string[] args)

   7:         {

   8:             try

   9:             {

  10:                 const string PROJECT_SERVER_URI = "h//ServerName/ProjectServerName/";

  11:                 const string PROJECT_SERVICE_PATH = "_vti_bin/psi/project.asmx";

  12:                 const string QUEUESYSTEM_SERVICE_PATH = "_vti_bin/psi/queuesystem.asmx";

  13:  

  14:                 Guid jobId;

  15:  

  16:                 // Set up the Web service objects

  17:                 ProjectWebSvc.Project projectSvc = new ProjectWebSvc.Project();

  18:  

  19:                 ProjectWebSvc.ProjectDataSet projectDs = new ProjectWebSvc.ProjectDataSet();

  20:  

  21:                 projectSvc.Url = PROJECT_SERVER_URI + PROJECT_SERVICE_PATH;

  22:                 projectSvc.Credentials = CredentialCache.DefaultCredentials;

  23:  

  24:                 QueueSystemWebSvc.QueueSystem q = new QueueSystemWebSvc.QueueSystem();

  25:                 q.Url = PROJECT_SERVER_URI + QUEUESYSTEM_SERVICE_PATH;

  26:                 q.UseDefaultCredentials = true;

  27:  

  28:                 projectDs = new ProjectWebSvc.ProjectDataSet();

  29:  

  30:                 // Create the project

  31:                 ProjectWebSvc.ProjectDataSet.ProjectRow projectRow = projectDs.Project.NewProjectRow();

  32:                 projectRow.PROJ_UID = Guid.NewGuid();

  33:                 projectRow.PROJ_NAME = "Its a wonderful project at " +

  34:                    DateTime.Now.ToShortDateString().Replace("/", "") + " " +

  35:                    DateTime.Now.ToShortTimeString().Replac", "");

color: #606060">  36:                 projectRow.PROJ_TYPE = (int)PSLibrary.Project.ProjectType.Project;

  37:                 projectDs.Project.AddProjectRow(projectRow);

  38:  

  39:                 // Add some tasks        

  40:                 jobId = Guid.NewGuid();

  41:                 projectSvc.QueueCreateProject(jobId, projectDs, false);

  42:                 WaitForQueue(q, jobId);

  43:  

  44:             }

  45:             catch (SoapException ex)

  46:             {

  47:                 PSLibrary.PSClientError error = new PSLibrary.PSClientError(ex);

  48:                 PSLibrary.PSErrorInfo[] errors = error.GetAllErrors();

  49:                 string errMess = "==============================rnEr rn";

color: #606060">  50:                 for (int i = 0; i < errors.Length; i++)

  51:                 {

  52:                     errMess += "n" + ex.Message.ToString() + "rn";

color: #606060">  53:                     errMess += "".PadRight(30, ‘=’) + "rnPSCLientError Outrn rn";

color: #606060">  54:                     errMess += errors[i].ErrId.ToString() + "n";

color: #606060">  55:  

  56:                     for (int j = 0; j < errors[i].ErrorAttributes.Length; j++)

  57:                     {

  58:                         errMess += "rnt" + errors[i].ErrorAttributeNames()[j]  " + errors[i].ErrorAttributes[j];

  59:                     }

  60:                     errMess += "rn".PadRight(30, ‘=’);

  61:                 }

  62:                 Console.ForegroundColor = ConsoleColor.Red;

  63:                 Console.WriteLine(errMess);

  64:             }

  65:             catch (WebException ex)

  66:             {

  67:                 string errMess = ex.Message.ToString() +

  68:                    "nnLog on, or check the Project Server Queuing Service";

  69:                 Console.ForegroundColor = ConsoleColor.Red;

  70:                 Console.WriteLine("Er " + errMess);

  71:             }

  72:             catch (Exception ex)

  73:             {

  74:                 Console.ForegroundColor = ConsoleColor.Red;

  75:                 Console.WriteLine("Er " + ex.Message);

  76:             }

  77:             finally

  78:             {

  79:                 Console.ResetColor();

  80:                 Console.WriteLine("rnrnPress any key…");

  81:                 Console.ReadKey();

  82:             }

  83:         }

  84:         static private void WaitForQueue(QueueSystemWebSvc.QueueSystem q, Guid jobId)

  85:         {

  86:             QueueSystemWebSvc.JobState jobState;

  87:             const int QUEUE_WAIT_TIME = 2; // two seconds

  88:             bool jobDone = false;

  89:             string xmlError = string.Empty;

  90:             int wait = 0;

  91:  

  92:             //Wait for the project to get through the queue

  93:             // - Get the estimated wait time in seconds

  94:             wait = q.GetJobWaitTime(jobId);

  95:  

  96:             // - Wait for it

  97:             Thread.Sleep(wait * 1000);

  98:             // - Wait until it is done.

  99:  

 100:             do

 101:             {

 102:                 // - Get the job state

 103:                 jobState = q.GetJobCompletionState(jobId, out xmlError);

 104:  

 105:                 if (jobState == QueueSystemWebSvc.JobState.Success)

 106:                 {

 107:                     jobDone = true;

 108:                 }

 109:                 else

 110:                 {

 111:                     if (jobState == QueueSystemWebSvc.JobState.Unknown

 112:                     || jobState == QueueSystemWebSvc.JobState.Failed

 113:                     || jobState == QueueSystemWebSvc.JobState.FailedNotBlocking

 114:                     || jobState == QueueSystemWebSvc.JobState.CorrelationBlocked

 115:                     || jobState == QueueSystemWebSvc.JobState.Canceled)

 116:                     {

 117:                         // If the job failed, error out

 118:                         throw (new ApplicationException("Queue request failed "" + jobState + "" Job " + jobId + ".rn" + xmlError));

 119:                     }

 120:                     else

 121:                     {

 122:                         Console.WriteLine("Job St " + jobState + " Job " + jobId);

 123:                         Thread.Sleep(QUEUE_WAIT_TIME * 1000);

 124:                     }

 125:                 }

 126:             }

 127:             while (!jobDone);

 128:         }

Popularity: 3% [?]

		
		

		

		Posted by ProjectServerBlogs
		Filed in Uncategorized
		
		No Comments »		

		
		
Free online courses for developers - MSDN Ramp Up
		

		30 January 2009 
		
 
Check out the Ramp Up program (http://www.myrampup.com/) if you have not done already. It has interesting tracks including SharePoint…

Popularity: unranked [?]

		
		

		

		Posted by ProjectServerBlogs
		Filed in Uncategorized
		
		No Comments »		

		
		
Enterprise Project Management (EPM) Solution Webcast Series
		

		30 January 2009 
		
From Christophe’s blog:
Starting February 18th, 2009 at 11 am (EST) we will be running a webcast series every Wednesday that will show how the Microsoft Enterprise Project Management (EPM) Solution and related Microsoft technologies can be deployed to meet varying horizontal scenarios.  
Why should customers attend the webcast series?

Work Smart - Save time by sending your prospects to a recurring live webcast versus having to deliver the demo yourselves
Educate  - Customers will receive a comprehensive overview of each solution and be able to get answers to initial questions
It’s Live - Send your customers to a live webcast rather than to a recording or click-through demo
Better Together - Show the value of integrating the EPM Solution with SharePoint Server and Visual Studio Team Foundation Server




these webcast are targeted at customers not partners.
Reduce Costs: Seven Steps to Optimize Project Portfolio Selection

Microsoft and UMT Consulting Group invite you to join this complimentary webcast to learn how Microsoft’s Enterprise Project Management (EPM) Solution can help identify and select project portfolios that best align with your organizations business strategy whilst optimizing costs.

Registration and Schedule






Capital Planning & Investment Control for Government 
Microsoft and Robbins-Gioia invite you to this complimentary webcast to learn how the Capital Planning & Investment Control (CPIC) Solution can help government agencies improve decision making, and effectively control investments throughout their lifecycle.

Registration and Schedule


Connecting the Worlds of Project Portfolio Management & Application lifecycle Management
Microsoft invites you to join this complimentary webcast to learn how integrating Portfolio Management (PPM) and Application Lifecycle Management (ALM) processes helps to improve visibility across the entire development lifecycle and in turn connect two disparate worlds.

Registration and Schedule







Growth: Transform Your Business with Innovation Management

You are invited to join this complimentary webcast to learn how Microsoft’s Innovation Process Management (IPM) Solution can help organizations to manage the end-to-end innovation process with greater transparency, coordination and discipline.

Registration and Schedule







Maximize Efficiency: Drive ROI by Enhancing Project & Portfolio Execution


 Pcubed invite you to join this complimentary webcast to learn how Microsoft’s Enterprise Project Management (EPM) Solution can help organizations to improve project and portfolio execution, eliminate costly overruns and enhance operational efficiency and agility.

Registration and Schedule




















Popularity: unranked [?]

		
		

		

		Posted by ProjectServerBlogs
		Filed in Uncategorized
		
		No Comments »		

		
		
mpFx: Simon Demo
		

		29 January 2009 
		


Popularity: unranked [?]

		
		

		

		Posted by ProjectServerBlogs
		Filed in Uncategorized
		
		No Comments »		

		
		
Yet Another PWA Hack — Displaying the Project Server Version
		

		28 January 2009 
		
Body:


 
Have you ever wondered which version of Project Server 2007 you’re running? There are a few documented ways to do this, but they require access to the SharePoint Central Administration web site, access to the Project Server machine(s) or SQL Server, or the ability to use developer’s tools. I’ll show you another quick way to add a simple web part to the PWA home page (or any web part page in PWA) which will display the Project Server 2007 version. 
 
If you’re not familiar with manipulating SharePoint pages with web parts, see my primer on the topic (‘Hacking PWA with Web Parts’) here: 
http://www.projectserverhelp.com/Lists/Posts/Post.aspx?ID=7 
Note: this procedure will show the Project Server version for ALL PWA users. 
 
 
Displaying the Project Server Version in PWA 
Follow these steps to display the Project Server version on the PWA home page: 
 
1. Visit the home page in PWA, then select Site Actions > Edit Page in the upper right corner: 
 
 
 
 
2. With PWA home page in edit mode, click the orange ‘Add a Web Part’ button / bar, which spans the entire width of the ‘Header’ web part zone: 
 
 
 
 
3. In the ‘Add Web Parts to Header’ dialog box, select the checkbox next to the ‘Content Editor Web Part’ item, then click the ‘Add’ button: 
 
 
 
 
4. After the ‘Content Editor Web Part’ has been added to the page, pull open the ‘edit’ menu near the upper right corner of the newly-added web part, then select the ‘Modify Shared Web Part’ option: 
 
 
 
 
5. In the ‘Content Editor Web Part’ editing panel which has opened on the right side of the page, click the ‘Source Editor…’ button: 
 
 
 
 
6. In the source editor dialog box, enter the following text, then click the ‘Save’ button: 
 
<span id=resultsarea01>&nbsp;</span> 
<script language=javascript> 
GetVersion(); 
function GetVersion() 
{ 
var pwaurl = "http://servername/pwa/"; 
try 
{ 
var wsURL = pwaurl + "_vti_bin/psi/Admin.asmx"; 
//SOAP Action and XML 
var wsSoapAction = "http://schemas.microsoft.com/office/project/server/webservices/Admin/ReadServerVersion"; 
var wsXML = ‘<?xml version="1.0" encoding="utf-8"?>’; 
wsXML += ‘<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ‘; 
wsXML += ‘xmlns:xsd="http://www.w3.org/2001/XMLSchema" ‘; 
wsXML += ‘xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">’; 
wsXML += ‘<soap:Body>’; 
wsXML += ‘<ReadServerVersion xmlns="http://schemas.microsoft.com/office/project/server/webservices/Admin/" />’; 
wsXML += ‘</soap:Body>’; 
wsXML += ‘</soap:Envelope>’; 
//Create XML Document and get HTTP response using XMLHTTP object 
var xmlDoc = new ActiveXObject("Microsoft.XMLDOM"); 
var httpResponse = getServiceResults(wsURL, wsSoapAction, wsXML); 
xmlDoc.loadXML(httpResponse); 
     var psversionmajor = xmlDoc.getElementsByTagName(’WADMIN_VERSION_MAJOR’); 
     var psversionminor = xmlDoc.getElementsByTagName(’WADMIN_VERSION_MINOR’); 
     var psversionbuild = xmlDoc.getElementsByTagName(’WADMIN_VERSION_BUILD’); 
     var psversionrevision = xmlDoc.getElementsByTagName(’WADMIN_VERSION_REVISION’); 
     var psversion = psversionmajor(0).text + "." + psversionminor(0).text + "." + psversionbuild(0).text + ", rev. " + psversionrevision(0).text; 
     var txt01 = document.getElementById(’resultsarea01′); 
txt01.innerHTML = psversion; 
} 
catch(Exception) 
{ 
// Suppress any excess script errors to avoid user confusion. 
} 
} 
function getServiceResults(url, soap, xml) { 
//Send XML packet to web service and return HTTP response text 
try { 
if (xml.length > 0) { 
xmlHttp = new ActiveXObject("Microsoft.XMLHTTP"); 
xmlHttp.open("POST", url, false); 
xmlHttp.setRequestHeader("SOAPAction", soap); 
xmlHttp.setRequestHeader("Content-Type", "text/xml"); 
xmlHttp.send(xml); 
if (parseInt(xmlHttp.status) == 404) { 
return 404; 
} 
else { 
return xmlHttp.responseText; 
} 
} 
} 
catch(e) { 
alert(e.message); 
} 
} 
</script> 
 
 
 
 
NOTE: The 6th line of the javascript code, var pwaurl = "http://servername/pwa/";, indicates the URL of your PWA site, and needs to be updated in order for the script to work in your environment. Be sure to include the trailing slash on the end! 
 
7. In the ‘Content Editor Web Part’ editing panel which should still be open on the right side of the page, expand the ‘Appearance’ heading by clicking [+], then enter ‘Project Server Version’ as the ‘Title’ of the web part: 
 
 
 
 
8. In the ‘Content Editor Web Part’ editing panel which should still be open on the right side of the page, select ‘Title Only’ for the ‘Chrome Type’ of the web part, then click the ‘OK’ button at the bottom of the panel: 
 
 
 
 
9. (Optional) After the ‘Content Editor Web Part’ editing panel is closed, hover the mouse cursor over the header of the new ‘Project Server Version‘ web part until the 4-way cursor is displayed, click and drag the header until it is positioned below the other web parts on the page (as indicated by the colored ‘I-beam’), then drop the web part into the ‘Footer‘ web part zone: 
 
 
 
 
 
 
 
The new ‘Project Server Version’ web part will now appear at the bottom of the PWA home page: 
 
 
 
 
10. Exit ‘edit mode’ by clicking the ‘Exit Edit Mode’ link near the upper right corner of the page: 
 
 
 
 
The Project Server version is now conveniently displayed at the bottom of the PWA home page: 
 
 
 
 
In Summary… 
 
No Server Access Required, and No Custom Coding Required 
As long as you have the permission to edit PWA pages, you can perform this hack, regardless of whether you have direct access to the server. This will work in hosted environments (such as ProjectHosts) as well! 
 
Be Careful! 
Remember… this hack affects all users, so be sure that there isn’t anyone who will be negatively affected by this change in the PWA interface. 
 
To undo the change, simply delete the ‘Project Server Version’ web part from the page. To learn how this is done, review my PWA web parts primer (‘Hacking PWA with Web Parts’) here: 
 
http://www.projectserverhelp.com/Lists/Posts/Post.aspx?ID=7 
 
Happy hacking! 


Category: Project Server Administration
Published: 1/28/2009 12:35 AM
Popularity: 2% [?]

		
		

		

		Posted by ProjectServerBlogs
		Filed in Uncategorized
		
		1 Comment »		

		

		
 — Next Page »