Home - Forums-.NET - FlyGrid.Net (Windows Forms) - Single DLL version, plus more licence popup nightmares...

FlyGrid.Net (Windows Forms)

.NET Datagrid - Fast, highly customizable, industry standards .NET data grid control for WinForms

This forum related to following products: FlyGrid.Net

Single DLL version, plus more licence popup nightmares...
Link Posted: 18-Apr-2007 19:47
Hi there,

I thought I'd offer a suggestion, as FlyGrid's multiple-DLL distribution style still frequently causes a large number of frustrating problems within the Visual Studio Forms designer...

Visual Studio's Forms Designer doesn't makes cached copies of FlyGrid.dll's satellite assemblies. That means that I frequently put a FlyGrid on the form, only to have the Form Designer complain when I try to add a column because the version of FlyGrid.Columns.Dll that it finds doesn't necessarily correspond with the FlyGrid.Dll that I'm trying to use. It doesn't matter if they're the identical version, they're a different copy of it, and so it complains.

My life would be made so much easier if there was a single-DLL version of FlyGrid with all of the column types etc included in the ONE library. That way, the forms designer would never get confused. I understand that this means that there would be redundant design time code included in release versions, but for me that would be much less of a negative than the endless battles I have trying to get a simple grid on a simple form and add a simple column.

Could subsequent releases include a single DLL option as well?

Also, I am *still* having problems with the FlyGrid licence system, even after following the demo video and step-by-step instructions you have given me. It works some of the time, but other times it simply doesn't, regardless of whether I remove all references to the FlyGrid libraries and add them again... I have followed the guidelines and your instructions to the letter over and over and I still get licence popups in my software. PLEASE can you do something to make this licence protection less frustratingly restrictive for people who are trying to use their valid licence. I'm getting to the point where I'm tempted to write my own grid component just to avoid the constant popup hassles.

Thanks in advance.

Kind regards,

Dave.
Link Posted: 19-Apr-2007 08:25
Agreed on all counts - this licensing stuff is ridiculous.
Link Posted: 22-Apr-2007 19:03
Yes, Visual Studio has some problems with resolving assemblies and embedding licenses, but if you will use 2 following conditions, license will embedded properly:
1. Specify references to the FlyGrid.Net assemblies to the default FlyGrid.Net binaries (usually it is C:\\Program Files\\9Rays.Net\\FlyGrid.Net\\Bin\\ for VS2003, C:\\Program Files\\9Rays.Net\\FlyGrid.Net\\Bin\\.Net 2.0\\ for VS2005 folders), don't use installing FlyGrid.Net into GAC on developer machine.
2. Place license to the folders mentioned in 1.
3. Rebuild your project.

You can use embedding license as resource into your project instead of 2. In some cases VS doesn't run lc.exe (license compiler utility) to embed license into compiled project.

Or you can distribute license file with your application, but it isn't best way.
Link Posted: 25-Apr-2007 02:43
How about the license popups when using VS 2005?  Every time I open a file in Design mode with a FlyGrid on it, I get a license popup.  I have the path referenced, I have a licenses.licx file, and I even have the .lic file in my project directory.
Link Posted: 25-Apr-2007 15:11
Hi... you have mentioned this solution to me on previous occasions. And while I appreciate the assistance, I have followed the steps you've described many times, and it doesn't work for multiple project solutions with inter-project dependencies.

Even if it did work, it would be extremely inconvenient given the fact that I need to be able to keep latest versions of proprietary DLLs in my version control repository to ensure the integrity of any version of my software that uses a number of third-party libraries. I'm sure this isn't an uncommon requirement from users of 3rd party libraries.

I have had no problems with any of the other 3rd-party DLLs I use... they are all licenced, per developer, just like FlyGrid. Some include multiple DLLs, just like FlyGrid. Some are visual controls used within the Forms Designer, just like FlyGrid. And they all work. Simply. This is how they behave:

* You put the DLLs *anywhere you like*
* You add references to those DLLs from the projects that intend to use them.
* You add the licence file as an embedded resource in the projects that intend to use them.
* You compile, and they work.
* The Forms Designer never gets confused.

I think this problem really needs to be addressed in FlyGrid. I see no good reason that the DLLs must be forced to live in C:\\Program Files\\9Rays.Net\\FlyGrid.Net\\Bin\\.Net 2.0\\ and cannot be located in a directory on the developer machine that is version controlled. I do not have any of my 3rd party DLLs in the Global Assembly Cache, by the way.

I have had other developers write to me since my post saying that they're having the exact same problems, and I think you'll find that your sales will improve if you address this issue.

PLEASE can you look at improving this situation. It is causing me and others much frustration for no actual gain.

Regards,

Dave.
Link Posted: 09-May-2007 17:30
Hi...

In another post you explained the following:

\"You can use embedding license as resource into your project instead of 2 [copying licence file to source/output directory]. In some cases VS doesn't run lc.exe (license compiler utility) to embed license into compiled project.\"

Could you please give more information on how to embed licence into the compiled project? I have added the licence file to the \"Properties\" folder of my project, and set its build action to \"Embedded Resource\", but this does not work - I still get the popup window when I run the program.

What am I doing wrong?

Cheers,

Dave.