Why are there classes in the root namespace?

I grabbed the trial version to check out the Ftp component, and as soon as I added a reference to the Ftp components, I got a syntax error in several of my files, because they included lines like this: `Imports Dd = My.Long.Namespace.DomainDude` This collides with some class in the root namespace in one of the assemblies from componentpro. (Presumably they're obfuscated names). I can change the namespace aliases in my code of course, but this isn't a great solution to me. Are these classes in the root namespace also present in the release version? Can there be a version where all of the content of the assemblies is properly within the `ComponentPro` namespace?
asked 12/5/2018 9:00:41 PM
  We got that issue. A newer build will be available within today. sysadmin 12/6/2018 3:37:42 AM
add a comment

1 Answers

A new revision will be available within today. ### UPDATE: A new build is now ready to download on our site and nuget.org
edited 12/6/2018 6:58:20 AM
answered 12/6/2018 3:30:39 AM
  Cool. I grabbed the latest version. I see that the classes are still in the global namespace, but now the class names are prefixed by c_. This could still collide with namespaces/classes in my project, but so far none of my classes are prefixed like this. For maximum compatibility, I still think all classes should be within the ComponentPro namespace (or you should obfuscate using unicode characters, like you did in previous versions...) jeff.dammeyer 12/6/2018 5:27:58 PM
add a comment

Your Answer

Not the answer you're looking for? Browse other questions tagged vb-net or ask your own question.