Analysis Management Objects - Microsoft SQL Server 2008 Analysis Services - page 681

foreach (IEnumerable dependencyList in dependencies.Values)
{
foreach (DependencyResult dependency in dependencyList)
{
Console.WriteLine(dependency.Description);
}
}
}
Removing a DataSourceView AMO object will not automatically delete dependent objects,
but will invalidate them instead, as shown in Figure 34.10.
FIGURE 34.10 Removing a DataSourceView AMO object will not automatically delete
dependent objects, but will invalidate them instead.
Creating a Visual Studio Project That Uses AMO
We are going to start by creating a project in Microsoft Visual Studio. You do not have to
use Visual Studio to use AMO to create your application, but your life as a developer will
be easier if you do. Creating an AMO project is similar to creating an ADOMD.NET
project, so we do not go into a lot of detail here. Look back at the “Creating an
ADOMD.NET Project” section in Chapter 33, “ADOMD.NET,” if you need to refresh your
memory.
Before you can start using AMO in your code, you have to register the assembly that
contains AMO—Analysis Management Objects ( Microsoft.AnalysisServices.dll )—and
import the namespace for the AMO classes by adding the using clause for
Microsoft.AnalysisServices :
using Microsoft.AnalysisServices;
Connecting to the Server
When it is working with AMO, the client application can connect to the server and work
with it in connected mode. In connected mode, the client application sends updates to
the server and regularly synchronizes with changes performed by other users. A good