Hi there...
Ok, I've finally managed to get to the point where, like some of the other posters, I can get the compiled version of my software to run without FlyGrid nag screens (YAY!)... but FlyGrid still nags me every time the forms designer re-syncs with the code (which is often)...
SO, I have a suggestion!!! A suggestion that will make your users love your fantastic product - after all, it's such a pity (given how good the software is) that its licencing annoyances have so many people uttering \"I hate FlyGrid\" on a regular basis (surely that must be bad for sales!).
The suggestion is not my own idea - another great custom control library I use has a very nice system for embedded licence protection... one that is SO easy to use and is flawless in its reliability and tolerance to updated versions.
If FlyGrid implemented a similar mechanism, it would look like this:
FlyGrid flyGrid = new FlyGrid();
flyGrid.EmbeddedLicence = \"\";
It's that simple. By being set in the Windows Forms designer, any nag effects can vanish *after* the control has been created. Admittedly, it requires you to provide the licence string for each instance of the control, but that's easy, plus it allows for multiple versions of the same control to be used concurrently in the same app. If the licence isn't valid, then the control paints itself in a \"DEMO MODE\" state, but it doesn't pop up nag screens. It simply overlays the words \"DEMO MODE\" over the control, rendering it unusable for release products.
I think if FlyGrid used this sort of approach, you would see positive effects, as the forums would no longer scare people away from buying it. I for one would be a hearty FlyGrid advocate
Even if you wanted to still have a nag screen, you could make the top level FlyGrid control popup the nag the first time the first grid tries to paint itself (or some equivalent - perhaps the first time its Parent is assigned), thus allowing the InitializeComponent method a chance to prevent the nag screen before the FlyGrid appears. I still prefer the \"DEMO MODE\" approach, but if you really wanted to stick with the nag screen, it could be achievable to a similar effect.
I hope you are able to consider this option.
Cheers,
Dave.