| boo |
| Member |
|
| Virginia, USA |
|
|
| None Specified |
|
| Sunday, October 5, 2008 |
| Thursday, December 18, 2008 6:44:38 PM |
10 [0.05% of all post / 0.00 posts per day] |
|
I have a new project I'm trying to create from an existing Visual Studio project. I've only imported the bare bone projects I need, everything else is just 'unknown externals'. So all that is here is classes.
When I go to save, I get 'Out of Memory'. So basically I'm dead in the water.
The memory usage by UModel before saving is 537M, during save it gets to about 850M and then gives me the 'Out of Memory' pop-up.
Very frustrating. Is there anythign I can do or am I just contrained to work on small projects with UModel.
|
If this is a repost I apologize, I submitted this before and was kicked out to the support help page...guess when your session expires they just abandon you...
So we're all on the same page; this solution that now has a problem has been working fine for months. No other changes were made to the solution when this issue cropped up other than adding new unit tests and code (no other new projects were added).
In our solution, we using MSTest (the testing tool that comes with Visual Studio) and our test editor has several test lists for organizing those tests.
On the day we re-opened Visual Studio after adding our existing UModel project to the solution we started getting this weird error whenever we opened the test list from Visual Studio: "The parameter cannot be null or empty. Parameter name: filename" and we get a duplicate VSMDI file (the file that holds the test lists) created.
Now I know this sounds like a Visual Studio MSTest bug (and given how many things were broke in 2008 that worked in 2005, I don't blame anyone who thinks that), but the fact that this showed up right after adding UModel to the solution has got me wondering if there's some sort of hook UModel has made into the IDE that has caused this.
So I removed the UModel project from the solution and the problem went away.
I tried to recreate in another solution and had no problems of course, so I'm just simply asking has anyone ever had some sort of weird IDE bug after adding an existing UModel project? Like I said, I'm willing to bet it's Visual Studio; but I got to ask to satisfy my curiosity.
Thanks much!
|
I swear if I delete an entire namespace of classes one more time from hitting the delete key trying to remove something off a diagram I'm going to pull my hair out.
Yes, I understand I need to use 'Shift-Delete', but it's a really hard habbit to break - delete by default should *not ever* remove an object/namespace/class/etc from your code (because of synchronization) - I'm sure there is a preference for this somewhere...I want UModel to always just remove from diagram unless I explicitly go to the model window and hit delete there.
|
I'm doing a VB project and VB, unlike C# creates a lot of 'noise' - in other words auto-generated classes that I really don't care about being documented (particularly those in the 'My' namespace). Anyway, while I've figured out how to generate documentation for just one component of the project (which you could do multiple components instead of 'ALL' or 'ONE'), I haven't figured out how you can tell UModel - "don't generate documentation on this class, or this namespace, or anything that meets the expression \bMy\b.
Is this possible or is this an upcoming feature?
On a whole different subject...
Also, there seems to be no symbols on the class diagram for me to be able to tell that the class is public, private, or internal.
Also, on the sequence diagram how do you specify that your acting against a static instance...I can see where you can set the classifier to static, but you get no visual representation of this.
Thanks!
|
|
Put me in too!
|
|
I can email you a screen shot if you'd like. Perhaps it's just a training issue. I'm doing what you say, and that's how I got the 'disabled' items in my context menu.
|
Another item 'found' by accident. If I have anything to say about this product while evaluating it, is that it needs some *serious* attention made to the help file.
Here is how to actually set the specific type for a class template:
In 'Model' view, drill down in the class Template to T:Class. In the properties window, right-click and 'Add constraining classifier'. Super simple once you know how to do it.
|
According to UModel help, I should be able to specify the generic type for a class. As instructed, I right click on the template in the class diagram and select show, but all the items in the context menu are disabled (including 'Bound elements' which the help file says I need to click to specify the specific type of class).
Please help. Thanks.
|
I found it accidentally in the help document under 'Minimalist UModel project - starting from scratch ' which funny enough was using Java as the root; but same difference.
What you need to do is to have all your C# work in a *new* package; don't use the default 'Component View' package. You'll probably be doing this anyway, unless you did like I did and put it *under* 'Component View' - which now I know you shouldn't do.
Anyway, when you add the new component, right click on it, select 'Code Engineering', then select 'Set as C# namespaces root' - then follow any prompting to import the C# library.
That's it. Nice and simple. Then if you want to, for pretty picture's sake, you can do a Package Diagram showing the dependencies in the root; but that's just if you feel like it.
|
I'm evaluating tools (this does seem to be one of the top one's that I can actually afford), but I'm on the fence.
I 'kind-of' figured out how to add the C# profile (seemed a lot more complicated than it need be). Problem is now I want to show a custom delegate for the application in my class diagram. I see the C# profile as a delegate, so to me I should just be able to add a class and then stereo type is as a delegate and all will be happy in the world; no such luck though; can't seem to stereo type anything that simple.
I followed the help file and and the C# profile to a class diagram along with the top level component view (Root) and tried to use that 'ProfileApplication' button to get the two to see each other but I got the 'NO' icon when drag onto the C# profile widget on the class diagram.
The ability to add delegates to a class diagram, and events (which is the other problem I'm having) to the class is essential in the tool I decide to purchase and this isn't very intuitive at this point - I'm willing to call it a training issue, but I need someone here to point me in the right direction.
Thanks! Brian
|
|