I have a project with some interfaces that contains some type alias in it, for example like below:
namespace UsingTest
{
using MyType = System.Collections.Generic.List<int>;
public interface IUsingTest
{
MyType GetList();
}
}
How can I use MyType in another project like below? (without need to redefine type alias)
namespace UsingTest
{
public class UsingClass : IUsingTest
{
public MyType GetList()
{
throw new NotImplementedException();
}
}
}
Note: if I want write the above code in the same project, as you can see in How do I alias a class name in C#, without having to add a line of code to every file that uses the class?, I need just declare MyType as global using in the interface file. But this technique does not work between multiple projects.
global usingbetween projects (by tweaking the.csproj), but it's probably better if you don't do this at all. Either declare a more specific type that is shareable (by wrapping theList<int>as a property in another class, for example, or using inheritance, but that's not as appropriate for generic collections) or don't use an alias if the only goal is to save keystrokes (you don't get any more stringent type checking, andList<int>is still very general).Coreproject which is used by all projects. Inside of thisCoreproject you can keep all global additives to your code (think of extension methods for example). This way you can easily manage them/ not pollute te projects themselvesList<int>. It is not much longer thanMyType, and it would take much less effort to understand. Lack of global alias can be an issue when using much more complicated generic types, but such types tend to be difficult to understand anyway, so might be good to avoid anyway.Dictionary<string, List<(int thingA, string thing B)>>or suchlike that isn't memorable on its own it starts paying off to introduce actual classes to represent them, rather than aliases. As a bonus, you can give these more specific names for the methods and properties than the generic methods. You can still fairly easily use the generic collections as the backing storage fields for those classes.