I'm using Visio and its UML tools to help convert a VB6 application to a ASP.NET application. In the original VB6 app, enums were placed inside particular classes that they were associated. When I recreated this structure in ASP.NET using VS.NET, it worked fine, but when I reversed engineered it into Visio, it threw errors: enums need to be in there own separate classes. Is this the way it should be done in the .NET world--which I admit I am completely new to.
The only thing worse than being alone, is wishing you were.
The only thing worse than being alone, is wishing you were.