tags:

views:

144

answers:

8

I just have a point of curiosity. I'm working with SSRS and calling its SOAP methods. I've got stubs generated / Web references created and that's all working fine and I can make web service calls OK.

The problem: the two classes generated from the WSDLs, ReportService2005 and ReportExecution, have some overlapping class definitions, such as ParameterValue, DataSourceCredentials, ReportParameter.

In C#, is there a way of saying, "For this block of code in the method, use this namespace?"

Pseudo / mostly build-error code:

use-this-namespace (ReportService2005)
{
    ParameterValue[] values = null;
    DataSourceCredentials[] credentials = null;
    ReportParameter[] parameters;
}

I understand that I can just write out of the full name, ReportService2005.ParameterValue[] values = null. Or I can alias the two classes at the top before my class/controller declaration. It's just something I'm curious about.

+1  A: 

Unfortunately not. There's no such syntax to address this need.

Dinah
+2  A: 

I don't think you can do that. You must specify Fully Qualified name to do that.

decyclone
A: 

AFAIK it can't be done

Yassir
+7  A: 

As others have written, I don't think this is possible. But what you can do, is to alias the full namespaces instead of each single class you want to use, e.g:

using rs = ReportService2005;
using re = ReportExecution;

// ...

rs.ParameterValue[] values = null;
rs.DataSourceCredentials[] credentials = null;
rs.ReportParameter[] parameters;
re.ParameterValue v2 = ...;
M4N
I would probably use a more expressive name than `rs` and `re` though...
Svish
+1  A: 

If the overlapping classes are identical (not just named the same) and share the same XML namespace, etc., then you may be able to take advantage of the wsdl.exe tool's sharetypes feature to generate both of your web service proxies so that they share the same type definitions for those overlapping classes.

http://msdn.microsoft.com/en-us/library/7h3ystb6%28VS.80%29.aspx

Check out the "/sharetypes" option to see if that works for your situation.

Dr. Wily's Apprentice
Oh I didn't realize. I've been using VS2010's Web Reference tool. I'll give it a try.
Jason
I believe the VS proxy generator (the web reference tool) actually uses the wsdl.exe tool behind the scenes. If that option works for you, then great. The downside is that if your web services change, then you will need to run the command again instead of just right-clicking on the web reference in visual studio and choosing "Update". However, that shouldn't be too bad. You could put the command in a batch file or a build script to simplify the process.
Dr. Wily's Apprentice
+1  A: 

While not relevant for working with Namespaces, or C#, VB.NET supports the With keyword which can be used as a shortcut for accessing members of an object:

SomeReallyLongName.Property1 = 1
SomeReallyLongName.Property2 = 2
SomeReallyLongName.Property3 = 3
SomeReallyLongName.Property4 = 4
SomeReallyLongName.Property5 = 5

Can be rewritten as:

With SomeReallyLongName
    .Property1 = 1
    .Property2 = 2
    .Property3 = 3
    .Property4 = 4
    .Property5 = 5
End With

It's not in C#, as you can get very close to the same behavior using other approached:

  • Using shorter variable names
  • Using imports-aliasing (Such as Martin suggested)
STW
Oh, interesting. Although I don't use VB.NET, still cool to know. Thanks.
Jason
+1  A: 

What you can do, is mark your class as partial:

public partial class MyWebServiceClass

in your main source file, and create a second source file with the method where you want to use the other namespace

// MyWebServiceClass.usingMethods.cs

using ReportService2005;
public partial class MyWebServiceClass
{
    // methods...
}
maxwellb
Granted, you still can't mix default namespaces within one method, so use the other suggestions here, but this way, you can separate methods if you want to have a default namespace for one or two methods only, say.
maxwellb
+1  A: 

Another little-known C# feature that might interest you, and is similar to Martin's answer, is essentially aliasing a class in the Imports blocks:

using ListOfDictionary = System.Collections.Generic.List<System.Collections.Generic.Dictionary<string, string>>;

and declare it as

ListOfDictionary list = new ListOfDictionary();

Note This feature, and sample, were found in another question; specifically: http://stackoverflow.com/questions/9033/hidden-features-of-c/3031174#3031174

STW