LiveLinq
ComponentOne LiveLinq is a class library that extends the functionality of LINQ in two related directions:
소비자가
1,054,000원
판매가
814,000원
구매제한
최소 1개
제조사
ComponentOneBrand Shop
상품코드
QSC7689
제품구분
처음판
견적요청 주문 장바구니 관심상품등록
※ 현시점 최적가 견적을 받으시려면 '견적요청' 해주세요. (VAT별도)
※ 문의 : 1899-0101
구분 및 가격 정보
(VAT별도)
Part 유형 구분 미디어 OS 언어 제품구분 버전 소비자가 판매가 견적 주문
1 상업 처음판 LP Win 영문 New License 1,054,000 814,000 견적 주문
2 상업 UPG LP Win 영문 Upgrade 818,000 632,000 견적 주문
3 상업 갱신 OLP Win 영문 Renewal 524,000 405,000 견적 주문
위 가격은 부가세 별도 가격입니다. 주문시 부가세 포함되어 결제가 진행됩니다.
견적 및 주문을 진행하시려면 로그인이 필요합니다.
‘주문’이 활성화 되어 있지 않은 제품은 ‘견적요청’을 해주시면 현 시점 최적가로 제공 해드립니다.
Suite 제품 – 본 제품을 포함하고 있는 제품
동일계열제품
요약정보
It makes LINQ faster LiveLinq uses indexing and other optimizations to speed up LINQ queries in memory. Speed gains can be hundreds and even thousands of times on queries with high selectivity conditions. Typical/average gains are lower but still significant, a 10-50 times speedup can be considered typical. It adds support for live views to LINQ A live view is a LINQ query result that is kept constantly up-to-date without re-populating it every time its base data changes. This makes LiveLinq extremely useful in common data-binding scenarios where objects are edited and may be filtered in or out of views, have their associated subtotals updated, and so on. In old jargon, one could say that LINQ queries correspond to snapshots, while LiveLinq view correspond to dynasets. Since live views automatically react to changes, they greatly widen the sphere of declarative programming, not only in data binding and GUI but in many other programming scenarios as well. ComponentOne LiveLinq implements three LINQ varieties: ?LINQ to Objects ?LINQ to XML ?LINQ to DataSet You can retrieve data from a database to a dataset in memory using ADO.NET and then use LiveLinq to DataSet, or you can retrieve objects from a database using LINQ to SQL or Entity Framework, then operate on that data using LiveLinq and then send changes to the database using again Entity Framework or another framework of your choice. LiveLinq and LINQ LiveLinq has the same syntax as the standard LINQ. The only change necessary is to wrap your data source by applying to it an extension method AsIndexed() (for indexing) or AsLive() (for live views). The two areas of LiveLinq functionality, indexing and live views can interoperate but are independent. It is not necessary to define indexes if you need to create a live view. A view is populated initially by executing a query, so, if the query can be optimized using indexing, the view will be populated faster. But after its initial population, changes to the view are made using special optimization techniques (known as Incremental View Maintenance) that don't require the user to explicitly define indexes. Faster LINQ with Indexing LiveLinq contains an indexing framework that it uses for optimizing query performance. For example, by defining an index by ProductID, you can dramatically speed up queries like: from p in products where p.ProductID == 100 because it will use the index to access the requested product directly instead of going through the entire large collection in search of a single product. Same indexes can also be used programmatically, in code, even without LINQ, for various kinds of searches, including range search and others. Declarative programming with Live Views LiveLinq adds the concept of view to LINQ. A view is a query with a resultset that remains live, dynamic after it is initially populated by executing the query. A standard LINQ query is a snapshot, in the sense that its result list does not change when you change the underlying (base) data. So it can't be used for full-featured data binding. A live view is automatically kept in sync with base data, so it enables full data binding to LINQ queries. Moreover, many views are updatable themselves, you can modify properties in their objects and add and delete objects directly in the view, see Updatable Views. So, a view can be modifiable in both directions: changes in base data propagate to the view and changes in the view propagate to base data. Data binding, which is mostly used in GUI, is a very important part of live views functionality, but not the only one. More generally, live views enable a declarative style of programming which we tentatively call "view-oriented programming". Non-GUI, batch processing code can also be made declarative using live views. Enabling technology: Incrementality When a change occurs in base data, live views update themselves in a smart, fast way, not simply repopulate themselves from scratch. The changes are made locally, incrementally, calculating the delta in the view from the delta in the base data. In most cases, it allows to propagate the change from base data to the view very fast. This is a key component of LiveLinq: its enabling technology, based on an area of Computer Science known as Incremental View Maintenance.

  • - 상품 전달: 패키지 제품은 택배로 발송 되고, 라이선스 제품은 전자 다운로드 혹은 메일로 전송됩니다.
    - 배송주소는 등록하신 주소와 다른 주소로 제품을 받기 원하는 경우에만 기록하십시오.
      받으시는 분 성함, 회사명 및 부서명(회사 등일 경우) 주소, 우편번호, 전화번호 및 이메일 주소를 기입해 주십시오.
  • - 세금계산서 발행을 원하시면 [주문]이 모두 완료된 후 사업자등록증 사본을 배정 된 영업담당자 이메일 혹은
      팩스(02-3474-9379)로 보내주십시오.
      (개정 세법에 의해 카드로 결제하신 경우에는 세금계산서 발행이 불가능합니다. 참고하시기 바랍니다.)
  • - 모든 제품의 교환 및 반품은 기본적으로 제조사 정책 기준에 따릅니다.
    - 제품 자체 불량이나 주문한 제품과 다른 제품이 배송된 경우 상품 수령 후 7일 이내에 반품/환불/교환해 드립니다.
    - 교환 및 반품에 소요되는 운송비는 고객분께서 부담하여야 됩니다.
    ※ 교환 및 반품이 불가능한 경우
    - 고객님의 책임 있는 사유로 상품등이 멸실 또는 훼손된 경우. (패키지 제품은 오픈시 반품불가)
    - 포장을 개봉하였거나 포장이 훼손되어 상품가치가 상실된 경우
    - 시간의 경과에 의하여 재판매가 곤란할 정도로 상품등의 가치가 현저히 감소한 경우
    - 복제가 가능한 상품등의 포장을 훼손한 경우