Configuring A Development Environment for Project Server 2007

S

Segrest

Hello Everyone,

I have done a fair amount of application development around the Project
Server 2003 product using VBA and VB6. With the release of Project Server
2007 it is a whole new world. The product has transitioned to a .Net 2.0
base and a Visual Studio 2005 development world. I for one won't miss the
old days much, but the learning curve into this new world can be rather steep.

You can write a lot of console or windows applications using PSI without
having to actually integrate them onto the project server system. But now I
am working on a project where a PSI extension (web service) and a couple of
custom web parts will be needed.

I normally setup my development environment on an XP workstation and
construct a separate project server. My experience has been that this
practice can significantly reduces problems at deployment time that may have
been hidden because you were developing on the server itself.

I am beginning to believe that this approach just will not work for the
development of things like PSI extensions and web parts that must by their
nature be integrated with the Project Server. It appears that the Project
development team intends for us to construct a non-production project server,
install all of the visual studio tools on it and then use it for this kind of
development. Then when development is completed, the appropriate bits and
pieces are simply copied and installed on a production server.

I would be very interested to know whether or not my conclusions are on track.

Comments?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top