How should I organize common ArcWeb Service objects if I am using .NET?
If you are using the same objects in different ArcWeb Services, you need to include the common classes definitions under a common namespace. Keeping common objects under a common namespace will help prevent the Ambiguous reference error. It is recommended that you do this in a new file, but you can also use an existing reference file. Make sure you include the attribute associated with each class when moving classes, and keep in mind you have to delete the common classes from the reference classes every time you update your Web references. If you have defined them in a new file, include a reference to this common namespace in the reference classes. For .NET quick-start tutorials, see C#.NET With Public Services, C#.NET With Restricted Services, VB.NET With Public Services, VB.NET With Restricted Services, ASP.NET With Public Services, and ASP.NET With Restricted Services.
If you are using the same objects in different ArcWeb Services, you need to include the common classes definitions under a common namespace. Keeping common objects under a common namespace will help prevent the Ambiguous reference error. It is recommended that you do this in a new file, but you can also use an existing reference file. Make sure you include the attribute associated with each class when moving classes, and keep in mind you have to delete the common classes from the reference classes every time you update your Web references. If you have defined them in a new file, include a reference to this common namespace in the reference classes. For .NET quick-start tutorials, see C#.NET With Place Finder Sample, C#.NET With ArcWeb Services, VB.NET With Place Finder Sample, VB.NET With ArcWeb Services, ASP.NET With Place Finder Sample, and ASP.NET With ArcWeb Services.
