May 2004 - Posts
Sometimes in a WinForm, you need to associate a bit of data with a UI control. Control.
Tag then becomes useful.
I'm sorry, but I disagree. It is my opinion that the Tag property should be buried as soon as possible.
Consider the next person in line to maintain your application. The Tag property is untyped and unnamed, and could cause so much confusion, that it's not worth it.
My solution? Created a derived class for the control and create a property for your information. In my opinion, it's more intuitive.
Tomorrow at 20:00 at the Dan Panorama Hotel in Tel Aviv.
Roy has set it up and Johanna Rothman will be there as an honorary guest.
Wow... Two Roy-Oriented posts in a row. I should write some more original content... :)
I submitted the Object Model Generator's add-in to Roy Osherove's Most Useful/Innovative VS.Net Add-in/Macro contest and am crossing my fingers for it.
This is one of the coolest things I've seen on the blogosphere in a while, I must say.
I talked to Roy a while ago and he's anxious to see more of people's works. He's even set up a post that you can comment on to request an add-in or get ideas for add-ins you could make.
There's loads of stuff on how to create add-ins on CodeProject (1, 2...), MSDN (more like a whole topic) and other places as well.
Let's see what you've got. ;)
[Update: Link to MSDN fixed. Thanks, DrFooMod2]
Just to point out that I found two more tools that allow you to generate an Object Model out of an Xml Schema document.
I looked into both of these tools and found that they are only simple and few additions to xsd.exe's already too-slim of an object model.
No match for the mighty powers of
The Object Model Generator. ;-P
If you know of any other tool in that field, please - let me know.
More tools:
We use Rational's XDE as a design tool that integrates with Visual Studio.NET.
One of its problems is that it takes more or less forever to do anything, let alone the heavier stuff, like reverse engineering.
Someone thought it would be nice to have the option "Reverse Engineer" on more or less every context menu in Visual Studio.NET. It probably would have been, if it had not been directly on top of the "Close" option.
Now, every time my mouse cursor slips when I try to close a window, XDE starts to reverse engineer whatever it was that I wanted to close. At the best times, it might have been just a resource or something, so XDE says "No, you can not reverse engineer this". Thank you very much.
When I mistakenly try to close a source file, XDE decides to think for me, so it reverse engineers my entire project and every other project that this project references.
Conclusion: Think about this when you write your application. Alert the user before you do anything that would take a lot of time.
And someone please tell that to the guys at Rational.
More Posts