ArcGIS Engine Developer Guide

.NET APPLICATION PROGRAMMING INTERFACE
End Try
End Sub
[C#]
private void doSomthing_Click(object sender, System.EventArgs e)
{
using (WebObject webobj = new WebObject())
{
ServerConnection serverConn = new ServerConnection("doug",true);
IServerObjectManager som = serverConn.ServerObjectManager;
IServerContext ctx = som.CreateServerContext("Yellowstone","MapServer");
IMapServer mapsrv = ctx.ServerObject as IMapServer;
IMapServerObjects mapo = mapsrv as IMapServerObjects;
IMap map = mapo.get_Map(mapsrv.DefaultMapName);
IFeatureLayer flayer = map.get_Layer(0) as IFeatureLayer;
IFeatureClass fclass = flayer.FeatureClass;
IFeatureCursor fcursor = fclass.Search(null, true);
webobj.ManageLifetime(fcursor);
IFeature f = null;
while ((f = fcursor.NextFeature()) != null)
{
// Do something with the feature.
}
}
}
ctx.ReleaseContext();
The WebMap, WebGeocode, and WebPageLayout objects also have a ManageLifetime
method. If you are using, for example, a WebMap and scope your code in a using
block, you can rely on these objects to explicitly release objects you add with
ManageLifetime at the end of the using block.
Note that .NET Support is a separate option in
the ArcGIS installation; this needs to be selected
during installation on both the development and
target machines for .NET customizations to
succeed. If you did not install .NET Support
originally, you can run the installation program
again and choose the Modify option to add
features to your ArcGIS installation.
178 • ArcGIS Engine Developer Guide
Deploying .NET ArcGIS customizations
All ArcGIS Engine and Desktop customizations require an ArcGIS installation on
all client machines. The ArcGIS installation must include the ESRI primary
interop assemblies, which the setup program installs in the global assembly cache.
For example, deploying a standalone GIS application that only requires an
ArcGIS Engine license requires an ArcGIS Engine installation on all target machines.
Standalone applications
Deploying standalone applications to either ArcGIS Engine or Desktop clients
involves copying over the executable to the client machine. Copying over the
executable can be as simple as using xcopy or more involved such as creating a
custom install or setup program. Note that aside from the ArcGIS primary
interop assemblies and the .NET Framework assemblies, all dependencies must
also be packaged and deployed.