Feedback Desired

In further thinking about GenX, I wanted your opinion. Do you think that a .NET utility that has nothing to render should still have design-time support? Personally, I don't think that it should, but I've been wrong before and I'd like to hear what you think. Please send me an e-mail or leave me some comments and tell me what you think.

2 Comments

  • Not really having much of a clue what GenX does, I'll lead with a qualified yes.





    If you're talking about being able to set properties at design time, maybe even a custom properties dialog window thingy ala VB6, then I'd be voting a definate yes. It makes it easier to just "fiddle" to get used to the component. Using a custom properties dialog also helps guide the user through the job of setting up the component.





    Although, (get ready for a flipflop), that'd make it a bit like the VB6 equivalent of using an ocx that had no runtime visual component and could have been done just as easily as a dll. Which I could never really see the point of :)





    Its a definate maybe :-)

  • Well, see, that's exactly why I'm torn. GenX.NET outputs an Excel file to the server. It doesn't have a UI whatsoever, it just has some properties that are set, usually in code. Now, should I give something like this design-time support, JUST so that I can make it easier to use... or should it always be manipulated programmatically?

Comments have been disabled for this content.