NPOI.SS.UserModel.RangeType missing namespace

[Adin-Sijamija]

The RangeType class found at namespace NPOI.SS.UserModel inside the IConditionalFormattingThreshold file does not have a namespace associate with it making It a global namespace, thus blocking any other class that shares the same name with it when the nugget package is added to any project producing the following error "Namespace ' contains a definition conflicting with alias RangeType". We have several projects with their own RnageType classes that conflict with the NPOI one.

The proposed fix is to add a namespace to the RangeType class and add corresponding using references in files that require said class.

[chucklu]

You might try this https://stackoverflow.com/a/1067573/13338936.

by the way, why you use global namespace in your projects?

[Adin-Sijamija]

@chucklu I am not using global namespaces in my project. The global namespace issues comes from NPOI RangeType which is a global namespace and overrides my RangeType, no correlation with NPOI's RangeType class (e.i missing namespace).

As a example XSSFWorkbook has a namespace

While RangeType does not

Inside https://github.com/nissl-lab/npoi/blob/master/main/SS/UserModel/ConditionalFormattingThreshold.cs the RangeType class should be included into the namespace NPOI.SS.UserModel like the interface is.

[chucklu]

Then you could use the RangeType of npoi as global::RangeType.

[Adin-Sijamija]

I am not using NPOI's RangeType at all in my code.

[chucklu]

Could you provide a sample repository? I tried to reference npoi in a new Console project, and I added a class RangeType without namespace, which means it's under global namespace.
I just get a warning CS0436，not the error you provided in screenshot.

[chucklu]

According Compiler Error CS0576, are you sure you did not use NPOI's RangeType？

// CS0576.cs  
using SysIO = System.IO;  
public class SysIO  
{  
   public void MyMethod() {}  
}  
  
public class Test  
{  
   public static void Main()  
   {  
      SysIO.Stream s;   // CS0576  
   }  
}  

[IADTIL]

@chucklu it looks like you have totally misunderstood the problem.

The NPOI code is clearly wrong. It should be an easy fix for anyone involved in developing this code.

[tonyqus]

This looks to be a mistake. I'll adjust the namespace in the next release.