This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, I haven't used the product yet but I wanted to have some questions answered about your Lightspeed product. First, if I want to use the "Linq to Oracle" feature in Lightspeed to create classes that are linked to database objects/table, can I create them in Visual Studio 2008 the same way I create them for the "Linq to Sql". What I mean is, can I go into Visual Studio 2008, connect to a database, go to a schema, drap and drop tables into a designer, and have a data context and classes created with the linq notation in them? Or do I have to use some external application that comes with Lightspeed to generate the code and then import that code into my VS 2008 project? Second, on the Lightspeed product page under the Licensing header, it says if "LightSpeed is used as part of a solution developed for someone else, then an additional license will need to be obtained." Does this mean if we use your Lightspeed product to develop an application for a client that we sell to them to install in their systems, then we would have to pay you another licensing fee? If we had a product that ran on our web servers that our customers ran/used through a web browser, would this extra licensing fee apply?
Thanks in advance for the information. -- Joe |
|
|
|
|
Hello Joe, Yes, you can create a LightSpeed model by dragging and dropping Oracle tables onto a designer in the same way as LINQ to SQL. If your project is targeting .NET 3.5 or above (i.e. LINQ is available), the designer will create a "data context" class (we call it a "unit of work", and the class will be named something like MyModelUnitOfWork), with properties corresponding to the entity types (e.g. NorthwindUnitOfWork.Products). These properties are IQueryable so you can then perform LINQ queries against them (e.g. from p in myUnitOfWork.Products where p.Price > 100 select p;). One thing to watch out for is that when you create an instance of the "data context" class, you do this in a slightly different way from LINQ to SQL: you can't just new up an instance directly, instead you need to create a LightSpeedContext<MyModelUnitOfWork> and call its CreateUnitOfWork method. (There is also a command-line tool which you can use to create classes from a database; this may be useful as part of an automated build process, but it does not currently create a LINQ "data context.") You can try this out for free using the Express edition -- the only limitation of Express is that it is limited to 8 model classes at runtime, and in particular the designer is fully functional. I will ask our legal whiz to get back to you on the licensing stuff but my understanding is that if you own the intellectual property in your Web or desktop application then you would not need to pay an additional licence (regardless of it being sold to your customers, installed on external systems or used by external users); but if the work was done under contract for a customer who owned the application/code instead of you then they would need to pay a licence fee. But I'll get someone to clarify this for you. |
|
|
|
|
Hi Joe, I just pinged you via email as well but I'll answer this here in case others find it useful. Basically
the idea is that the license owner is whoever owns the IP to the source
code you are creating. For example, if you were Microsoft and you built a product, you
would own that source code and therefore only buy one license - all
your end users can use that product as much as they want without it costing you more. I hope that helps, John-Daniel |
|
|
|
