I'm trying to create a class model for some pages and controls in my website. However when I drag any of them to the class diagram I get an error "Some of the selected types cannot be added to the class diagram. From a previous post there was a comment saying you cannot model these types.
Is this still true, and if so does anyone know of a work around I also tried reverse engineering to Visio, but the model only shows the true classes, again not the pages or controls. We used the reverse engineering alot in VS 2003 to show class diagrams, and the sequence diagrams for our more complex processes.
Thanks
Sara
Problem with Class Designer and Pages and Controls
Ellswogs
Hi Sara
It's Nev.
I'm about to embark on realising a vision that has been present and driving me, sometimes round the bend, for years. Its the same vision that bought me into contact with you actually, as well as all them others who I have totally forgotten. Yes. I would like very much for you to be the person that does my web site but you're not the only web designer in the world and nor is that the only reason I'm sending you this email. If you think or feel that is the only reason, then I was definately wrong to contact you at this time.
I hope you and Ben are really well and/or headed there.
Very best regards,
Nev xx
B-soft
Nev
I don't know who you are, you must think I am someone else.
Regards
Sara
grantmi
Class Designer\Class Diagram does not support the viewing of Web Forms or Web UserControls. If you try and add a Web Form or Web UserControl to a class diagram you will get the following error: “No types were found in the selection”. The reason for this limitation is that Web Forms or web UserControls are only instantiated on access in ASP.Net, so when the file is closed, it's not considered "accessed" and therefore nothing in it is displayed. Unlike normal project where all code is built into a single dll/exe, the code in a web project is divided into multiple compilation units. There is one compilation unit for each code folder ("App_Code" and its sub code folders as specified in web.config), and there is one compilation unit for each page file (those exist outside of "App_Code" folder, forms, master pages, etc.) All compilation units, except for those in code folder, are created on access and destroyed afterwards, so they're not supported by ClassDesigner in this release. As a result, you can only view types defined in code folder (under "App_Code" folder), which are always visible in ClassView coincidentally. As a side note, this is why ClassDesigner files are under "App_Code" folder.
As a workaround you could try using a Web Application Project.
http://msdn.microsoft.com/asp.net/reference/infrastructure/wap/default.aspx
Thanks
Brian [MSFT]
Microsoft Developer Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Mamta M
Hello
If you are just wanting documentation you could try prototyping with a Web Application Project. This would get you the class diagrams that you want and then do the implementation using the new 2005 design.
ThanksBrian [MSFT]
Microsoft Developer Support
This posting is provided "AS IS" with no warranties, and confers no rights.
ELB
Kenneth Wohlers
Thanks Brian
I thought that might be the anwser, but was hoping there was something I didn't know about. It's a real problrm for us because we now have to manually create the classes in Visio to complete our documentation. We want to stay with the new web site project since it has some advantages over the web project we used to use in 2003.
Thanks
Sara