Setting up a Development Environment

This section discusses how to set up a machine or set of machines to create a development and test environment for building your integrations.While directions are given for setting up environments for the individual System Center products, commonalities are noted wherever they occur.

Configuration Manager Development Environment

Installation of a ConfigMgr Administrative console

If you debug administrative UI components, you can install just the Administrative console on your development machine and link to a remote ConfigMgr server (but keep in mind that multiple devs accessing a single ConfigMgr server may run into conflicts if writing information back to the server). ConfigMgr setup allows you to install just the Administrative console if you've already installed a server.
Notes about using a remote admin console setup:
  • The root\SMS WMI class does not exist on a console-only installation. MOF files / WMI changes must still be done at the site server
  • In order to use a remote console, the appropriate permissions must be configured on the site server to allow remote access. This requires that both machines be joined to the same domain or have a trust established so that the user account on the developer machine can be added to the SCCM site server permissions.
  • You must add your user account to the SMS Admins group on the site server
  • You must configure DCOM access to allow remote access for your user account
  • You may need to configure your firewall to allow the traffic to and from the server

Debugging UI Development with Visual Studio 2008

Debug mode is especially useful for viewing contents of ConfigMgr properties stored in PropertyManager.You can use this technique to ensure that properties being passed to your code is what you expected.

Note: these directions assume you either have the site server or the admin UI local to the development environment
From Visual Studio and within your project:
  • Right-click your project and select Properties
  • Select Debug on the left tab of the project properties
  • Under Start Action, select Start external program and type: C:\Windows\system32\mmc.exe
  • Under Start Options, type the following into the Command line arguments textbox (you need to change the path depending on where you installed the program, and surround with quotes if the path contains spaces):
	<SCCM INSTALL DIR>\AdminUI\bin\adminconsole.msc  
  • Save the properties
  • Make sure that when the code is built that the appropriate assemblies and symbol files are copied to the target directories in the SCCM console structure. This is best done through a post-build command. You can set this through the Build Events section of the project properties, under Post-build event command line.
  • Click Debug > Start Debugging (alternatively, if you want to just debug one part of your solution, you can select a project in the Solution Explorer, right-click and select Debug > Start new instance
  • The project should build, execute your post-build command line, then launch the Admin UI.
  • Use the UI as you need to hit any breakpoints in your code. You can now use the locals or watch window to see object values while going through the UI.

Last edited Feb 12, 2009 at 7:06 PM by rhearn, version 1


No comments yet.