User Guides | Flexcel Studio for the .NET Framework Documentation

Total Page:16

File Type:pdf, Size:1020Kb

Load more

User Guides In this section we cover the concepts that you need to know in order to use FlexCel effectively. The documents here are not a full reference for every type and method in FlexCel: If you are looking for the reference documentation in the methods and classes, you can find it in the API Documentation tab. In this section: Installation Guide Because before using FlexCel you need to install it. Getting started An introduction to start using FlexCel quickly. API Developer Guide How to use the FlexCel API to read and write Excel files. Reports Developer Guide How to create Excel files by replacing tags in a template. Reports Designer Guide How to design a template to be used with FlexCelReport. Reports Tag Reference A list with all the tags available in a report. Performance Guide How to get the most of FlexCel performance wise. PDF Exporting Guide How to use FlexCel to export Excel files to PDF. HTML Exporting Guide How to use FlexCel to export Excel files to HTML. FlexCel Studio for the .NET Framework 7.11.0.0 Page 1 of 2 iOS Guide Special considerations when working in iOS. Android Guide Special considerations when working in Android. Windows Phone, Store and Universal apps Guide How to use FlexCel inside Universal apps, and the limitations on it. Mono Guide How to use FlexCel with Mono. .NET Core Using FlexCel with .NET Core. FlexCel Studio for the .NET Framework 7.11.0.0 Page 2 of 2 FlexCel Installation Guide Choosing how to install FlexCel You can install FlexCel in 2 different ways: 1. If installing in Windows, you can just run the setup.exe downloaded from our website. It will install all the examples, the dlls, the NuGet packages and the docs. 2. If installing in macOS, we don't have an automatic setup, but you can download the NuGet packages from our website, register them, and use them. You should still install the full FlexCel with setup.exe in a Windows machine to be able to see and run all the examples. Registering the FlexCel NuGet packages If you installed FlexCel via setup.exe, then you don't need to do anything else: Setup should have registered the FlexCel NuGet packages for you. If you downloaded the NuGet packages directly, then you need to put them in a private NuGet repository. IMPORTANT Because FlexCel is not open source, the FlexCel NuGet packages must be put inside a private repository that only people with a license can access it. Please don't put them in a public repository like nuget.org. There are many ways to put FlexCel in a private repository, and depending on your needs you might find some better than others. You can read about it here: https://docs.microsoft.com/en- us/nuget/hosting-packages/overview However, the simplest way is just to add the folder where the FlexCel NuGet packages are to the NuGet feeds. Even when https://docs.microsoft.com/en-us/nuget/hosting-packages/overview mentions putting them in a network share, there is no need to share the folder. You can use a simple not shared folder, and this is what the FlexCel Setup does. To do it manually when you are not using Setup.exe follow the steps below: 1. If you want to install from inside Visual Studio, go to Menu->Tools->NuGet Package Manager->Package Manager Console. If you don't have Visual Studio, you can install NuGet following the instructions in https://docs.microsoft.com/en-us/nuget/guides/install- nuget 2. Either from the Package Manager console, a command line prompt or a terminal, type: nuget sources Add -name flexcel.tmssoftware.com -Source <path-to-where-the- flexcel-package-is> FlexCel Studio for the .NET Framework 7.11.0.0 Page 1 of 4 So if for example the FlexCel package is at C: \Users\adrian\Documents\TMSSoftware\FlexCelNET\nuget your screen should look as follows: NOTE You can also visually manage your package sources by going to Menu->Tools->NuGet Package Manager->Package Manager Options: But in this guide we preferred to focus on the command line way, because it allows you to register nuget sources even if Visual Studio is not available. For uninstalling the source, just go to the package manager options and remove it, or type: nuget sources Remove -name flexcel.tmssoftware.com Referencing the FlexCel NuGet packages Once you have the nuget sources set up, either because you used setup.exe or because you set them up manually, you need to reference them from your project. To do that, right-click your project, and select Manage NuGet Packages: FlexCel Studio for the .NET Framework 7.11.0.0 Page 2 of 4 Once in the package manager, follow the steps: 1. Select Browse 2. Select All as the package source. 3. Search for FlexCel 4. Select the TMS.FlexCel package. 5. Press Install. NOTE In step 2, you could have selected "flexcel.tmssoftware.com" as source instead of "All", to be able to find FlexCel faster. But if you selected flexcel.tmssoftware.com it wouldn't be able to resolve dependencies to other packages in nuget.org. So to be safe, make sure to select All and search for FlexCel, instead of selecting the flexcel.tmssoftware.com feed NOTE Normally the only package you need to install is TMS.FlexCel. This package includes almost all the functionality in FlexCel. But when doing WinForms apps, there is an Excel previewer available in the TMS.FlexCel.WinForms package that you might also want to use. For WebForm apps, there is also a viewer which is available in the TMS.FlexCel.WebForms package. The extra packages only work in Windows and in WinForms or WebForms apps. For all other kinds of apps, the only package that you need and can install is TMS.FlexCel. FlexCel Studio for the .NET Framework 7.11.0.0 Page 3 of 4 Manually Referencing FlexCel If you prefer not to work with nuget packages, FlexCel setup also installs the dlls directly. Instead of adding the NuGet package, you can just right click in the "References" entry in your project, select "Add Reference" and manually add the FlexCel.dll that is needed for your platform and framework type. NOTE In FlexCel for .NET Core you can't manually reference the assemblies and the only choice is via NuGet. FlexCel Studio for the .NET Framework 7.11.0.0 Page 4 of 4 Getting Started with FlexCel Studio for the .NET Framework 0. Before starting: Choosing how to install and reference FlexCel When installing FlexCel, there are 2 options: 1. Download the exe setup. This is the preferred way to install FlexCel in Windows, since it will install the NuGet package, the libraries, the examples and docs. 2. Download the NuGet packages. This includes only the NuGet packages (which are also included in the exe setup), but doesn't include example code or docs, and won't register the NuGet source in your machine. This is the preferred way to install FlexCel in platforms different from Windows, and you can find more information on how to install it on the installation guide. Once you have FlexCel installed, you need to decide how to reference it. There are 2 ways you can reference FlexCel: 1. Install via NuGet packages. This is a standard installation same as any other NuGet installation, but with the difference that FlexCel is not stored in nuget.org How to install via NuGet is detailed step by step in the installation guide 2. Install by manually referencing the assemblies. This is possible in all platforms except in .NET Core, where the only option is via NuGet. How you decide to reference the assemblies is up to you: .NET is moving from a monolithic framework to a framework "on demand" via NuGet, and so we would recommend you to use NuGet too. But if you prefer to reference the assemblies directly, you can do that too. TIP If you are unsure, just install the exe setup and use the FlexCel NuGet packages. 1. Creating an Excel file with code The simplest way to use FlexCel is to use the XlsFile class to manipulate files. To get started, create an empty Console application and save it. Add the TMS.FlexCel NuGet package to your application or add a manual reference to FlexCel.dll Then replace all the text in the file by the following: FlexCel Studio for the .NET Framework 7.11.0.0 Page 1 of 9 using System; using FlexCel.Core; using FlexCel.XlsAdapter; namespace Samples { class MainClass { public static void Main(string[] args) { //Create a new empty Excel file, with default formatting as if it was created by Excel 2019. //Different Excel versions can have different formatting when they create //an empty file, so for example //Excel 2003 will have a default font of Arial, and 2019 will use Calibri. //This format is anyway the starting format, you can change it all later. XlsFile xls = new XlsFile(1, TExcelFileFormat.v2019, true); //Enters a string into A1. xls.SetCellValue(1, 1, "Hello from FlexCel!"); //Enters a number into A2. //Note that xls.SetCellValue(2, 1, "7") would enter a string. xls.SetCellValue(2, 1, 7); //Enter another floating point number. //All numbers in Excel are floating point, //so even if you enter an integer, it will be stored as double. xls.SetCellValue(3, 1, 11.3); //Enters a formula into A4. xls.SetCellValue(4, 1, new TFormula("=Sum(A2:A3)")); //Saves the file to the "Documents" folder.
Recommended publications
  • Microsoft Macro Assembler Version 5.1.PDF

    Microsoft Macro Assembler Version 5.1.PDF

    Microsoft. Macro Assembler Version 5.1 • For the MS® OS/2 or MS-DOS® Operating System Microsoft Macro Asset bier version 5.1 puts all the speed and power of assembly-lar uage programming within easy reach. Make your programs run faster by linking assembly-language subroutines to your Microsoft QuickBASIC, BASIC compiler, C, FORTRAN, and Pascal programs. Technical Highlights If you're accustomed to programming beyond the level of documentation the correct model for your subroutine, in a high-level language like Microsoft supplied with previous versions of just use the MODEL directive and choose QuickBASIC, BASIC compiler, QuickC, Microsoft Macro Assembler. This totally the model you need. To start your data C, FORTRAN, or Pascal, Microsoft revised guide provides a complete and segment, just add a DATA directive; Macro Assembler version 5.1 is the bridge well-organized explanation of Microsoft to create a stack, add a STACK directive; you've been looking for to the assembly- Macro Assembler and the instruction and to begin writing instructions, use language environment. You can, for sets it supports. the CODE directive. example, use the powerful graphics func- What's more, the Mixed-Language High-level language interface tions of Microsoft QuickBASIC or the Programming Guide included with Micro- macros help you declare your subroutines, efficient math functions of Microsoft soft Macro Assembler version 5.1 con- set up stack parameters, and create local FORTRAN and then add time-critical tains complete, easy-to-follow instructions variables. In addition, version 5.1 offers routines in Microsoft Macro Assembler. on how to call assembly-language sub- MS-DOS interface macros that make it Easier to learn and use.
  • Ironpython in Action

    Ironpython in Action

    IronPytho IN ACTION Michael J. Foord Christian Muirhead FOREWORD BY JIM HUGUNIN MANNING IronPython in Action Download at Boykma.Com Licensed to Deborah Christiansen <[email protected]> Download at Boykma.Com Licensed to Deborah Christiansen <[email protected]> IronPython in Action MICHAEL J. FOORD CHRISTIAN MUIRHEAD MANNING Greenwich (74° w. long.) Download at Boykma.Com Licensed to Deborah Christiansen <[email protected]> For online information and ordering of this and other Manning books, please visit www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact Special Sales Department Manning Publications Co. Sound View Court 3B fax: (609) 877-8256 Greenwich, CT 06830 email: [email protected] ©2009 by Manning Publications Co. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books we publish printed on acid-free paper, and we exert our best efforts to that end. Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15% recycled and processed without the use of elemental chlorine.
  • Opening Presentation

    Opening Presentation

    Mono Meeting. Miguel de Icaza [email protected] October 24, 2006 Mono, Novell and the Community. Mono would not exist without the community: • Individual contributors. • Companies using Mono. • Organizations using Mono. • Companies using parts of Mono. • Google Summer of Code. Introductions. 2 Goals of the Meeting. A chance to meet. • Most of the Novell/Mono team is here. • Many contributors are here. • Various breaks to talk. Talk to others! • Introduce yourself, ask questions. Talk to us! • Frank Rego, Mono's Product Manager is here. • Tell us what you need in Mono. • Tell us about how you use Mono. 3 Project Status Goals Originally: • Improve our development platform on Linux. As the community grew: • Expand to support Microsoft APIs. As Mono got more complete: • Provide a complete cross platform runtime. • Allow Windows developers to port to Linux. 5 Mono Stacks and Goals. MySMQySQLL//PPosstgtrgesrsess EvEovolluutitioonn# # ASP.NET Novell APIs: MMoozzillala Novell iFolder iFolder, LDAP, Identity ADO.NET ApAapchachee MMonoono DesktoGpTK#: GTK# OpNoevenlOl LfDfAiPce GCneomceil# Windows.Forms JavaJa vCa oCommpaatitbilbitiylity Google APIs Microsoft Compatibility Libraries Mono Libraries Mono Runtime (Implementation of ECMA #335) 6 Platforms, CIL, Code Generation. 7 API space Mono 1.0: July 2004 “T-Bone” Mono 1.2: November 2006 “Rump steak” Mono 1.2 bits. Reliability and C# 2.0, .NET 2.0 scalability: • Complete. • With VM support. • ZenWorks and iFolder • Some 2.0 API support. pushed Mono on the server. • IronPython works. • xsp 1.0: 8 request/second. • xsp 1.2: 250 Debugger: request/second. • x86 and x86-64 debugger. GUI • CLI-only, limited in scenarios (no xsp).
  • Visual Studio for Mono Development

    Visual Studio for Mono Development

    Visual Studio for Mono Development By Francisco “Paco” Martinez Overview ●Introduction ●Mono and Gtk# installers for Windows ●VSPrj2Make: An add-in for Visual Studio ●Distributing your Creation ●What's Next? ●Q&A Demo I Creating a quick Gtk# editor application using Visual Studio and Glade. Introduction ●Background Even if most of the coding and advances of Mono takes place on Linux, there are many Windows and .NET developers that may only have access to computers that run Windows and/or feel most comfortable developing in a Microsoft centric world. Another convincing argument for using the Visual Studio IDE is the benefits of its integrated debugger that permits step-by-step iterations anytime during the coding process. Introduction (continued) ●Prerequisites – The OS: Windows 2000 or Windows XP – Visual Studio .NET 2003 (standard ed. or better) – Gtk# Installer for .NET Framework SDK – VSPrj2Make Visual Studio Add-in – One or more versions of the Mono Combined Installer for Windows Introduction (continued) ●Other Useful Tools – Gtk# Windows Help for Visual Studio – MonoLaunch – GRE Installer for Gecko# – Inno Setup and InstallerMaker – Cygwin and/or Msys Mono and Gtk# Installers for Windows ●Mono Combined Installer for Windows – Does not require .NET SDK or Redistributable – Does not require Cygwin – Contains sufficient libraries (GNU, GTK+ and GNOME) to satisfy the managed libraries that bind to them. – Does not touch the Global PATH or other environment variables – this is key to permit coexistence of different versions on the same
  • JOE LAM Website: | E-Mail: Joe@Joe-Lam.Com | Phone: (201) 887-7588

    JOE LAM Website: | E-Mail: [email protected] | Phone: (201) 887-7588

    JOE LAM Website: http://joe-lam.com | E-mail: [email protected] | Phone: (201) 887-7588 SUMMARY Microsoft Build Hackathon winner with 9+ years’ professional experience in software development. Ample Experience in managing development teams in various sizes, including project planning, scheduling, and resource allocation. Providing technical guidance and designing system/application architectures on mission critical enterprise projects. Responsible for all aspects of the software development lifecycle and deliver innovative solutions for business needs. TECHNOLOGIES Microsoft Application Development with .Net Framework 4.5.2 in C# ASP.Net (WebAPI, SignalR, MVC, Web Service), WPF (Telerik, DevExpress), Windows Service, Silverlight, WCF, WF, MSMQ, LINQ, Expression Tree, Lambda Expression, RegEx, MEF, TPL, GDI+, Serialization Enterprise Library, Prism, Unity, Reactive Extensions, PostSharp, MS Build, MS Test, NUnit, moq, Protocol Buffers Web Application Development with HTML5, CSS3 and JavaScript ES5 in W3C Standards React, TypeScript, AngularJS, Knockout, jQuery, RequireJS, Lo-Dash, toastr, Bootstrap, Ajax, HighCharts, Google Charts Database Development with SQL Server in T-SQL and MDX ADO.Net, Entity Framework, Sync Framework, SSIS, SSAS, SSRS TECHNIQUES Multi-paradigm programming (OOP, AOP, Functional, Concurrent, EDP, Data-driven, Generic, Reflective, Dynamic), Design Principles (SOILD, SoC, DRY, KISS), IoC, Design Patterns, Data Structures, System & Application Architectures, UI/UX Design, Single Page Application, Responsive Web Design,
  • The Unicode Cookbook for Linguists: Managing Writing Systems Using Orthography Profiles

    The Unicode Cookbook for Linguists: Managing Writing Systems Using Orthography Profiles

    Zurich Open Repository and Archive University of Zurich Main Library Strickhofstrasse 39 CH-8057 Zurich www.zora.uzh.ch Year: 2017 The Unicode Cookbook for Linguists: Managing writing systems using orthography profiles Moran, Steven ; Cysouw, Michael DOI: https://doi.org/10.5281/zenodo.290662 Posted at the Zurich Open Repository and Archive, University of Zurich ZORA URL: https://doi.org/10.5167/uzh-135400 Monograph The following work is licensed under a Creative Commons: Attribution 4.0 International (CC BY 4.0) License. Originally published at: Moran, Steven; Cysouw, Michael (2017). The Unicode Cookbook for Linguists: Managing writing systems using orthography profiles. CERN Data Centre: Zenodo. DOI: https://doi.org/10.5281/zenodo.290662 The Unicode Cookbook for Linguists Managing writing systems using orthography profiles Steven Moran & Michael Cysouw Change dedication in localmetadata.tex Preface This text is meant as a practical guide for linguists, and programmers, whowork with data in multilingual computational environments. We introduce the basic concepts needed to understand how writing systems and character encodings function, and how they work together. The intersection of the Unicode Standard and the International Phonetic Al- phabet is often not met without frustration by users. Nevertheless, thetwo standards have provided language researchers with a consistent computational architecture needed to process, publish and analyze data from many different languages. We bring to light common, but not always transparent, pitfalls that researchers face when working with Unicode and IPA. Our research uses quantitative methods to compare languages and uncover and clarify their phylogenetic relations. However, the majority of lexical data available from the world’s languages is in author- or document-specific orthogra- phies.
  • Sandcastle Kingdoms Free Download Document Your C# Code with XML Comments

    Sandcastle Kingdoms Free Download Document Your C# Code with XML Comments

    sandcastle kingdoms free download Document your C# code with XML comments. XML documentation comments are a special kind of comment, added above the definition of any user-defined type or member. They are special because they can be processed by the compiler to generate an XML documentation file at compile time. The compiler-generated XML file can be distributed alongside your .NET assembly so that Visual Studio and other IDEs can use IntelliSense to show quick information about types or members. Additionally, the XML file can be run through tools like DocFX and Sandcastle to generate API reference websites. XML documentation comments, like all other comments, are ignored by the compiler. You can generate the XML file at compile time by doing one of the following: If you are developing an application with .NET Core from the command line, you can add a GenerateDocumentationFile element to the <PropertyGroup> section of your .csproj project file. You can also specify the path to the documentation file directly using DocumentationFile element. The following example generates an XML file in the project directory with the same root filename as the assembly: This is equivalent to the following: If you are developing an application using Visual Studio, right-click on the project and select Properties . In the properties dialog, select the Build tab, and check XML documentation file . You can also change the location to which the compiler writes the file. If you are compiling a .NET application from the command line, add the DocumentationFile compiler option when compiling. XML documentation comments use triple forward slashes ( /// ) and an XML formatted comment body.
  • PETER STEPHENS Current Technical Pursuits: Agile Practices, Cloud

    PETER STEPHENS Current Technical Pursuits: Agile Practices, Cloud

    PETER STEPHENS 512.778.6322 / cell 865.567.7173 1955 County Road 202 www.diligentsoftware.com/resume Liberty Hill, TX 78642 [email protected] Current Technical Pursuits: Agile Practices, Cloud Computing and Amazon Web Services, Cloud Automation, ASP.NET MVC, REST based web services, JavaScript and jQuery CURRENT SKILLS • Microsoft.NET Framework versions 1.0 – 4.5 » C#, LINQ, XML , Networking, Regular Expressions, Multithreading , Task Parallel Library, Encryption, etc. » Websites: ASP.NET WebForms and MVC » Thick Client: Windows Presentation Foundation (WPF) » Web Services: WCF, Web API (REST and RPC) , and OData • Cloud Computing » Amazon Web Services : EC2 , S3 , RDS , SQS, SNS, Cloud Formation, Route 53, etc. » Rackspace Cloud • Automation : Powershell, MSBuild, and T4 templating • Agile Practices : Continuous Integration with Team City and CruiseControl.NET, Test Driven Development (TDD ), NUnit, Rhino Mocks, MOQ, Autofac, and ReSharper • Microsoft SQL Server versions 7 – 2008. Extensive use of T-SQL , C# stored procedures, C# functions, management and database optimization • HTML , CSS , JavaScript , jQuery , HTTP, Web Design, SEO , and Microsoft Expression Studio, Report Viewer Control based RDLC reports • Domain Specific Languages: Irony • Deployment: WIX , InstallShield, and WebDeploy • Source Control : Git and Mercurial, Beyond Compare, KDIFF OPEN SOURCE AND SOCIAL • Stack Overflow: http://stackoverflow.com/users/72860/peter-stephens • Twitter: https://twitter.com/#!/peterastephens • Bitbucket: https://bitbucket.org/pstephens/
  • Logview Studio Linux Preparation with Mono

    Logview Studio Linux Preparation with Mono

    LogView Studio Linux Preparation with Mono 2014 by Dominik Schmidt [email protected] © 2014 Dominik Schmidt / Holger Hemmecke I LogView Studio Table of Contents Part I Linux Prepare 1 1 SSH Co..n..n..e..c..t. ........................................................................................................................ 1 2 Raspbe..r.r.y.. .P..i. ......................................................................................................................... 4 System Prepar..a..t.i.o...n.. ............................................................................................................................................... 5 Mono .......................................................................................................................................................... 6 Install Mono......................................................................................................................................................... 7 Compile Mon..o.. .f.r..o..m.. .T..A...R....................................................................................................................................... 8 Compile Mon..o.. .f.r..o..m.. .G...I.T........................................................................................................................................ 9 Testing ......................................................................................................................................................... 10 3 Cubie.t.r.u..c..k.. .........................................................................................................................
  • Software License Agreement (EULA)

    Software License Agreement (EULA)

    Third-party Computer Software AutoVu™ ALPR cameras • angular-animate (https://docs.angularjs.org/api/ngAnimate) licensed under the terms of the MIT License (https://github.com/angular/angular.js/blob/master/LICENSE). © 2010-2016 Google, Inc. http://angularjs.org • angular-base64 (https://github.com/ninjatronic/angular-base64) licensed under the terms of the MIT License (https://github.com/ninjatronic/angular-base64/blob/master/LICENSE). © 2010 Nick Galbreath © 2013 Pete Martin • angular-translate (https://github.com/angular-translate/angular-translate) licensed under the terms of the MIT License (https://github.com/angular-translate/angular-translate/blob/master/LICENSE). © 2014 [email protected] • angular-translate-handler-log (https://github.com/angular-translate/bower-angular-translate-handler-log) licensed under the terms of the MIT License (https://github.com/angular-translate/angular-translate/blob/master/LICENSE). © 2014 [email protected] • angular-translate-loader-static-files (https://github.com/angular-translate/bower-angular-translate-loader-static-files) licensed under the terms of the MIT License (https://github.com/angular-translate/angular-translate/blob/master/LICENSE). © 2014 [email protected] • Angular Google Maps (http://angular-ui.github.io/angular-google-maps/#!/) licensed under the terms of the MIT License (https://opensource.org/licenses/MIT). © 2013-2016 angular-google-maps • AngularJS (http://angularjs.org/) licensed under the terms of the MIT License (https://github.com/angular/angular.js/blob/master/LICENSE). © 2010-2016 Google, Inc. http://angularjs.org • AngularUI Bootstrap (http://angular-ui.github.io/bootstrap/) licensed under the terms of the MIT License (https://github.com/angular- ui/bootstrap/blob/master/LICENSE).
  • Metadefender Core V4.13.1

    Metadefender Core V4.13.1

    MetaDefender Core v4.13.1 © 2018 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 13 Key Features of Metadefender Core 14 1. Quick Start with Metadefender Core 15 1.1. Installation 15 Operating system invariant initial steps 15 Basic setup 16 1.1.1. Configuration wizard 16 1.2. License Activation 21 1.3. Scan Files with Metadefender Core 21 2. Installing or Upgrading Metadefender Core 22 2.1. Recommended System Requirements 22 System Requirements For Server 22 Browser Requirements for the Metadefender Core Management Console 24 2.2. Installing Metadefender 25 Installation 25 Installation notes 25 2.2.1. Installing Metadefender Core using command line 26 2.2.2. Installing Metadefender Core using the Install Wizard 27 2.3. Upgrading MetaDefender Core 27 Upgrading from MetaDefender Core 3.x 27 Upgrading from MetaDefender Core 4.x 28 2.4. Metadefender Core Licensing 28 2.4.1. Activating Metadefender Licenses 28 2.4.2. Checking Your Metadefender Core License 35 2.5. Performance and Load Estimation 36 What to know before reading the results: Some factors that affect performance 36 How test results are calculated 37 Test Reports 37 Performance Report - Multi-Scanning On Linux 37 Performance Report - Multi-Scanning On Windows 41 2.6. Special installation options 46 Use RAMDISK for the tempdirectory 46 3. Configuring Metadefender Core 50 3.1. Management Console 50 3.2.
  • Công Nghệ Thông Tin Và Truyền Thông

    Công Nghệ Thông Tin Và Truyền Thông

    DANH MỤC TÀI LIỆU CHUYÊN NGÀNH CÔNG NGHỆ THÔNG TIN VÀ TRUYỀN THÔNG Danh mục tài liệu bao gồm những tài liệu về: Khoa học máy tính; Công nghệ phần mềm; Kỹ thuật máy tính, Hệ thống thông tin, Truyền thông và mạng máy tính Bạn đọc có thể tham khảo những tài liệu này tại phòng đọc chuyên ngành 411; 419; 526; 304 STT TÀI LIỆU KHOA HỌC MÁY TÍNH Công nghệ thông tin : Tổng quan và một số vấn đề cơ bản / Phan Đình Diệu, 1 Quách Tuấn Ngọc , Nguyễn Thúc Hải... KHXG: QA75.5 International journal of computer and engineering management / Assumption 2 University. KHXG: QA75.5 3 Advances in information storage system. Volume 7 / Bharat Bhushan editor. KHXG: QA75.5 .A102-i V.7-1996 4 Advances in information storage system. Volume 8 / Bharat Bhushan editor. KHXG: QA75.5 .A102-i V.8-1998 Foundations of information and knowledge systems : third international 5 symposium, FoIKS 2004 : Wilheminenburg [sic] Castle, Austria, February 17-20, 2004 : proceedings / Dietmar Seipel, Jose Maria Turull-Torres (eds.). KHXG: QA75.5 .F435-o 2004 Hội thảo khoa học quốc gia lần thứ hai về nghiên cứu, phát triển và ứng dụng Công 6 nghệ thông tin và truyền thông : ICT.rda' 04. Hà Nội ngày 24-25/9/2005 / Vũ Đình Cự, Đỗ Trung Tá KHXG: QA75.5 .H452t 2005 2010 IEEE-RIVF international conference on computing and communication 7 technologies: Research, innovation and vision for the future : Vietnam national university, Hanoi Vietnam: November 1-4, 2010 / Tu Bao Ho,...[et.al.].