VB.NET namespace issue regarding explict (named) vs. implicit (global or root) namespaces -


I have a solution that includes many projects that all use the same root namespace. If no code files explicitly give the namespace name, then we say that the root namespace is ExampleRootNamespace .

Now a problem comes into play, when I want to add a name clearly named to one of the code name files. I want to be able to separate this code from the other assembly to be able to run FxCop against it. That's why I got the namespace interface in the code file. Add something like CSV .

This is the reason for any code that needs to be asked to import this code into for example. Interface. CSV . So far, so good. I can also run FxCop against assembly now the problem is that in other assemblies I can not say things like now: 

  public example frmInputBoolean example example. RootNameSpace.frmFormTemplate

Visual Studio is now asking me to rename the namespace: 

  public class frmInputBoolean Inherits Global.ExampleRootNameSpace.frmFormTemplate

There are hundreds of errors related to this, so my questions are:

1) Why is the name of the root name giving the name of the root name due to the first time with the program originally? is?

2) Are there any problems without this problem changing name?

I also want to add that in relation to ExampleRootNamespace.Interfaces.CSV I am not referring it anywhere in the codebase. I am currently referring to this from just one unit testing project, so I do not know why adding this name space causes a problem.

Try to use in C #> use the operator with your namespace . 

  using ExampleRootNamespace = newExampleRootNamespace; 
 
 
 Unfortunately, I do not believe that VB.NET has an easy solution for you

Comments

Post a Comment