Introduction to Git Extensions

GIT Extensions is a distributed version control system enabling user to robustly manage collection of source files and the changes made in them. The changes made are shown in History of changes. Users can make changes by accessing a Central repository called remote repository and committing the changes to it. It implements classic GIT by using GUI (Graphical user interface), basically driven by a set of dedicated commands, hence maintains the version control system intuitively. So, let us go through a glimpse of functionalities provided by GIT Extensions so that our version control system can be maintained.

Managing repository

There are many options to manage repository through GIT Extensions. It includes viewing the committed logs and changes made in comparison to previous commit, cloning a repository, traversing through the file directory and filtering the committed logs by using custom search input etc.

GIT Extensions can be downloaded from https://github.com/gitextensions/gitextensions/releases/tag/v2.48.05

Generating SSH Keys as one time activity

SSH Keys should be loaded as a one-time activity. SSH keys can be generated while setting up the GIT Extensions.

In order to use a safe development environment with SSH you need to get PuTTY installed as preferred SSH client. PuTTY can be downloaded from http://www.putty.org/

The first thing is to check that Git Extensions is properly configured to use PuTTY as well as all paths are given correctly.

In the Remotes Tab just choose Generate or import key to start the key generator.

It will ask you to move around the mouse in order to generate more random keys. When the key gets generated, save the public and private key in a text file by clicking the Save Public key button.

Since now you are having a key pair, provide the public key to the Github account by copying the Key from the file which you just saved above at your desired location.

Then open your Github account and click on the profile image, followed by Account settings and going to the SSH Keys tab. Finally, paste the public key over there.

You can create a Github account at https://github.com/join?source=header

Now github will get to know which public key it has to use to decrypt. Now you also need to provide the private key to GitExtensions to encrypt. You will find a Load SSH key button in the clone dialog where you can load the private key in PuTTY authentication.

Note: This is a one-time activity and you don’t need to repeat these steps again.

How to Clone a Repository?

Cloning a repository will create a local copy of the repository being cloned by this action.

1. Click ’Clone repository’ link from Common Actions section in the left to clone a repository.
2. Provide the necessary inputs as Repository to clone (highlighted URL at the top tells which repository needs to be cloned), Destination (local hard drive location), Branch (automatically loaded when the local repository address is provided), and Repository type and then click ‘Clone’.
3. The process of cloning starts and the remote files are checked-out to the specified destination i.e. local directory. A green tick mark indicating completion of process will be displayed.

Note: A Red Cross mark with respective errors will be displayed too during occurrence of errors in the process, if any.

How to open a repository?

From the Common Actions section at the left click ‘Open Repository’ link and give the directory address for opening a repository. Then click ‘Open’ button as highlighted in the figure.

It opens the repository and all committed logs will be shown with abstract message associated with them, committed user and the time elapsed when the commit was done (Refer figure). Also, the details like Author, date are shown at the bottom in the commit section.

How to traverse into repository?

Initially click ‘File Tree’ tab. It will show whole repository in the form of a file tree and intended files and directories can be viewed easily. This is the step-wise procedure to traverse a repository by a user.

How to track the changes using Git Extensions?

By clicking the ‘Diff’ tab comparison can be made with respect to the previous commit as shown in the figure.

Note: Newly added lines are marked as ’+’sign and shown with green color and the deleted ones as ’-’ sign and presented with red color.

How to perform Commit & Push?

This action of committing and then pushing the given code to a remote repository is divided into two operations:

1. Committing to Local Repository
2. Committing to Remote Repository

Committing to Local Repository with Git Extensions

This process of committing involves various steps:

1. To start the process click the ’Commit’ icon.The respective fields are displayed in the newly opened commit window (Refer figure):
   • Working directory files.
   • Staged files.
   • Details of the modifications compared to the respective repo code.
   • Input box for the commit message to be entered by the user.
     The top left section will show the working directory files which were modified since the last commit:

     Icon	Meaning
     	This represents all existing files that were edited after last commit
     	This represents files which are removed after last commit
     	This represents new files which are added after last commit

     1. Click any file from working directory file list. The files with their modified changes (highlighted in Red and Green) are displayed on right section. This way we can identify file-wise discrete changes.
     2. When the changes are verified, files can be staged by using the ‘Stage’ option (Refer Figure). These Staged files are ready to commit and provides an easy way for filtering certain files not committed during the previous stage for the users.
        Note: Users can also Unstage a staged file by using the ‘Unstage’ option opposite to Stage icon.
     3. When the verification and staging of all required files is done, you have to provide a suitable message to show current commit action. Commit History screen will show this message. The purpose of commit action can be easily interpreted if an appropriate message is given.
2. Commit the files using ‘Commit’ button. Status of the commit operation is displayed in a dialog window. It will also show all the run- time errors of the process, displaying them with the appropriate stage of the whole process.

Note: Clicking ‘Commit’ lets the files to be committed into the local repository and not into the remote repository.

Committing to Remote Repository 

‘Push’ action is used to move the files of local repository into remote repository. It needs to be ensured by the user that the code which was taken lastly from the remote repository is not modified before you perform push action. There is every possibility that a repository could have been modified when it has been pulled or cloned by another person. This generally happens in a multi-user environment where a lot of branching and merging happens. Hence, it is necessary for a user to perform a Pull before opting for a Pushing action for the committed code.

Pulling the code

1. Open the pull Window by clicking on the ‘Pull’ icon as shown in the figure. Provide the remote repo URL and select the remote branch form there.
2. It is necessary to select the Do Not Merge Option (Do not merge, only fetch remote changes) and ‘Auto Stash’ option.
3. Lastly click the ‘Pull’ button.
   

Pushing the code

As of now, the local repository and the remote repository are in sync, so the user now has to click the ‘Push’ button as shown in the figure so that all the locally committed changes can be pushed to the remote repository.

We hope that this tutorial helps you in getting familiarized with the use of Git using the tool Git Extensions.

The post The Beginner’s Guide for GIT Extensions: How to use GIT to clone repository from GitHub and make changes appeared first on ByteScout.

We are happy to announce that our upcoming ByteScout Cloud API is available to play with through web chat bot (see below) and Telegram bot (@BytescoutBot). The source code for both bots are available on Github

Screenshots:

Webchat Bot	Telegram bot

Web chat online – try it right here!

The post Play with our technology using Web Chat bot or Telegram bot? appeared first on ByteScout.

ByteScout bot for Skype is now up and running!
Add it to your contacts via this link:
https://join.skype.com/bot/122c0906-bb13-47c9-940d-00635db4b5c9
(requires the latest version of Skype for iOS, Android or Windows)

Screenshot:

ByteScout bot is also available on Telegram messenger: add using this link https://telegram.me/bytescoutbot

ByteScout bot is also available as online web chat (see below):

The post Skype bot is up and running now! appeared first on ByteScout.

The post Microsoft Bot Framework chat bot experience comparing to Telegram bot appeared first on ByteScout.

Always wondered why on Earth you would need to really use a chat bot? Here is the answer: the updated version of ByteScout Chat bot is capable of generating a PDF invoices based on short instruction from you in literally 3 seconds!

Just send the following command to ByteScout Chat Bot online or in Telegram, Slack or Skype:

INVOICE 3145, From: John Doe, NY, Some Street, 12 To: Acme, Inc., San Francisco, Some Street 12, 18 Lines: 15 website fixes at 20.00, 32 improving seo at 14.45, 2 fixing bugs with CRM integration at 18.5

And within a few seconds you will get a link to a downloadable and printable PDF invoice:

Sounds cool? Try yourself and let us know what you think!

Are you a developer? Get your free account for ByteScout Cloud API to generate PDF from HTML, generate invoices, generate barcodes and PDF, extract data from PDF invoices, split and merge PDFs and much much more

The post How to create a printable invoice for your client within 3 seconds using ByteScout chatbot! appeared first on ByteScout.

JavaScript is a client side programming language that helps developers add interactivity to their webpages on the client side. Since, JavaScript runs within a client’s browser, it is extremely fast. Typically, JavaScript is typically used to perform client side validations, add dynamic effects and perform animations.

In the inception stages of World Wide Web, the browsers were not sophisticated enough and it was extremely cumbersome to debug JavaScript. However, with time, browsers evolved and JavaScript debugging features were added to browser.

Google chrome also includes detailed debugging tools in the form of Developer tools. This tutorial explains the process of debugging JavaScript code with the help of these developer tools.

Before, dwelling into the details of debugging techniques, let us assume we have an a webpage with following script.

<!DOCTYPE HTML>

<html>

<head>

<title> Debugging Javascript</title>

<script src="script.js"></script>

<script>

DisplayResult(25, 25);

</script>

</head>

<body>

</body>

</html>

It can be seen in the Head of the webpage that the page links to a JavaScript file named “script.js”. Also some JavaScript code has been added in the script tag which calls “DisplayResult”. Since the function is not defined in the webpage, it should be present in the “script.js” file. The contents of the “script.js” file are as follows:

function DisplayResult(input1, input2)
{
document.write("The result is "+AddNumbers(input1, input2))
}

function AddNumbers(num1, num2)
{
var result = num1 + num2;
return result;
}

It can be seen that the file contains two functions: DisplayResult function which is called from the webpage and the AddNumbers function which takes two parameters, add them and returns the result of the addition. AddNumbers function is being called from DisplayResult function.

Now, let us see how we can debug a JavsScript program.

JavaScript Step by Step Debugging

There are two ways to launch Google chrome developer tools.

First is by going to the top-right corner of the browser window and clicking “Customize and control Google Chrome” button. This opens a drop-down list. Select “More tools” option from the list and then select “Developer tools” from the drop-down list which appears. Have a look at the following figure:

The other way to launch Developer tools in chrome is by simply right clicking anywhere on the page and click “Inspect” from the options that populate.

For this tutorial we opened the webpage that we created at the start of the tutorial and then opened developer tools. The following window appears at the bottom of the screen.

You can see that there are several options. If you click “Sources” from the options, you can see your webpage and all the pages that it references. In our case both the “index.html” which is our only page is displayed along with the script that we are using. Click “script.js” file and you will see its contents.

In case of any errors the console window will display them. At the moment there is no error in our JavaScript file. Let us introduce an error.  Change the AddNumbers function of the “script.js” file so that it looks like this:

function AddNumbers(num1, num2)
{
var result = num1 + number2;
return result;
}

Note, in we have changed num2 to number2 but this variable doesn’t exit. If you again open the webpage or refresh it via “Ctrl+R” and open the developer tools, you will see an error. Have a look at the following figure:

If you look at the top right of the above figure, you shall see an error icon with number 1. These shows there are 1 error in the program. If you look at the console at the bottom, the error is shown. On extreme right, the file which contains the error and the line number of the error is also shown which is “script.js” file and line number 8. If you click this file, the contents of the file will be displayed. You can click the error icon to see the detail of the error as shown in the following figure:

Adding Break Points in Chrome Developer Tools

Break points help stop execution of your code at a certain point. Developers can view state of different variable at a certain point of execution with the help of these break points. For instance, if you want to see what variables are passed to “DisplayResult” function you can add break point at the start of that function. To add break point simply clicks on the left grey area of the line at which you want your program to stop execution. The area will turn blue as shown in the following figure:

Now if you refresh the page using “Ctrl + R”, the page will stop its execution at the break point which you set. This is shown in following figure:

Here you can see the contents of variables input1 and input2. You can use F10 key to step over the code, F11 to step into the code i.e. other functions, Shift + F11 to step out of code and F8 to continue executing the code.

Conditional break points can also be added which only hits if a certain condition is met. To do so, right click on the grey area on the left side of the line where you want to add break point and select, “Add conditional breakpoint” option. A text field will appear. Here the condition can be added. For instance, you can add that if the value of the input1 is 20, only then this break point should be hit.

Using Watch in JavaScript Developer Tools

Chrome developer tools also lets developer watch the behavior of a variable using “Add Watch” feature. To add a feature to watch, simple Right click the variable and select “Add to watch” option that appears at the top of the list. Have a look at the following figure:

Once you add a variable to the watch it appears inside a window in the developer tools. You can do whatever you want with the variable. For instance, number ten has been added to the “num2” variable which is under the watch. The developer tools have evaluated the expression and the result has been displayed. Consider following figure:

The post Debugging JavaScript code using Google Chrome Developer Tools appeared first on ByteScout.

Yesterday, the critical security flaw revealed in the popular ImageMagick image processing package. The secury issue allows to execute the code by passing a specifically modified image. This is a serious threat for any service that relies on ImageMagick should protect their installation as soon as possible.

The site dedicated to this “ImageTragick” issue advises to “If you use ImageMagick or an affected library, we recommend you mitigate the known vulnerabilities by doing at least one of these two things (but preferably both!)”:

1. Use a policy file into disable the vulnerable ImageMagick coders (see the detailed instruction and how to verify that policies are set correctly)
2. Verify that all uploaded images are corresponding to expected file formats by checking the file header.

To verify uploaded images and documents you may use some of these ways:

• Write your own code to read so called magic bytes from uploaded files to confirm if the file corresponds to expected file type;
• Use open source modules like these ones:
  • Mime-content-type function (PHP)
  • CarrierWave BombShelter (Rails)
  • ImgHdr.py (Python)
  • FileTypeDetective NuGet package or FindMimeFromData (.NET)

What about Javascript or if you don’t want to use additional module or need to check file before uploading to your server? ByteScout Cloud API provides the solution for this case with its /file/verify REST Web API.

Example:

curl https://bytescout.io/api/v1/file/verify \
-d apiKey=YOUR_API_KEY \ 
-d expected=PNG \
-d simple=true \
-d input=https://upload.wikimedia.org/wikipedia/commons/b/b4/JPEG_example_JPG_RIP_100.jpg

As the passed URL contains JPG image, the request will return:

invalid, detected jpg

If the expected type corresponds to the actual format then it will return the simple short response: ok

You may also get the detailed response including the detected file type and the detected mime type.

Example:

curl https://bytescout.io/api/v1/file/verify \
-d apiKey=YOUR_API_KEY \ 
-d expected=PNG \
-d input=https://upload.wikimedia.org/wikipedia/commons/b/b4/JPEG_example_JPG_RIP_100.jpg

The response for this request will be (JSON):

{
"mime":"image/jpeg",
"detected":"jpg",
"expected":"png",
"success":false,
"filename":"JPEG_example_JPG_RIP_100.jpg"
}

With Cloud API you may verify image files and pdf files files before processing them further and protect from malicious scripts or files masking as images or documents.

Sign up here to create your free account for ByteScout Cloud API.

The post ImageTragick issue: how to verify images and documents to protect from renamed malicious files appeared first on ByteScout.

Our freeware utility for data extraction and PDF manipulation PDF Multitool was reviewed and top-rated by the famous German GIGA.DE :

Der ByteScout PDF Multitool verschafft euch ein Multifunktions-Werkzeug für PDF-Dateien, das es euch ermöglicht, Daten von PDF-Dateien zu extrahieren, PDF-Dateien in CSV, XML, XLS oder TIFF zu konvertieren, Dateianhänge zu extrahieren und vieles mehr.

Weiterhin kann der ByteScout PDF Multitool PDF-Dateien mit eingescannten Bildern in durchsuchbare PDF-Dokumente umwandeln sowie Text von eingescannten Dokumenten auflesen, wobei Englisch, Deutsch, Spanisch, Französisch und mehr unterstützt werden. Das Tool beherrscht außerdem das automatische Finden von Tabellen innerhalb von PDF-Dokumenten sowie das Durchsuchen von PDF-Dateien mittels regulärer Ausdrücke. Seiten innerhalb von PDF-Dateien … 

Read More (German)..

The post PDF Multitool was reviewed and top rated by GIGA.de appeared first on ByteScout.

1. Setting Free Trial Account on Azure

Go to – https://azure.microsoft.com/en-in/pricing/free-trial/.

1.1 Enter email and check I am a new user. Click “Sign in using our secure server”.

1.2 If you already have Microsoft ID, please sign in else create new Microsoft ID clicking “Sign up now”.

1.3 Fill in your email id and create a password.

1.4 After verifying email id, enter your credit card details and complete SMS verification.

1.5 Go to Azure Portal https://portal.azure.com/signin and log in with your Microsoft credentials.

1.6 Now you can browse Azure Portal.

2. Creating and configuring Azure Virtual Machine

2.1 Click on New > Virtual Machines > Windows Server 2012 R2.

2.2 Select Deployment model > Resource Manager.

2.3 Configure Basic settings.

2.4 Choose Virtual Machine size.

2.5 Configure Storage and Network settings.

2.6 Review the summary and click OK.

2.7 Now we will configure Security Group (Network Security Settings).
Go to All Resources and  select Network security group which belongs to the new virtual machine.

2.8 Select Inbound Security Rules.

2.9 Add a new security rule. Select TCP protocol and enter Destination port range number 80.

2.10 Add another security rule. Select TCP protocol and enter Destination port range number 8172. 

3. Connecting to Azure VM remote desktop

3.1 Go to All Resources and select Virtual Machine.

3.2 Click “Connect” and download the remote desktop connection application file (.rdp). 

3.3 Go to the folder where you have saved the .rdp file.

3.4 Right-click on the .rdp file and select Connect.

3.5 Click Connect again to allow remote connection.

3.6 Enter you credentials.

3.7 Check “Don’t ask me again” checkbox and click “Yes”.

4. Setting IIS on Azure Virtual Machine

4.1 Open Server Manager by clicking on its icon on the taskbar.

4.2 Click “Add roles and features”.

4.3 Roles and Features Wizard opens. Click “Next”.

4.4 Select “Role-based or feature-based installation” and click “Next”.

4.5 Select “Select a server from the server pool”, then choose your server and click “Next”.

4.6 Select “Web Server (IIS)” from “Server Roles” list and click “Next”.

4.7 Select following features:
.NET Framework 3.5 Features,
ASP.NET 4.5.

4.8 Click “Next”.

4.9 Let’s select Role Services: select items highlighted on the screenshots below and click “Next”.

4.10 Click “Install” and wait until the installation is complete.

4.11 Click “Close”.

5. Installing Web deploy package on Azure VM

5.1 Go to http://www.microsoft.com/web/downloads/platform.aspx, download, and run Microsoft Web Platform Installer.

5.2. Using the installer search field, find and select Web Deploy 3.6 and click “Add”

5.3 Then click “Install”.

5.4 Accept the Microsoft license terms, then wait until the end of the installation and click “Finish”.

6. Creating ASP.NET MVC Application using VS2015 Web Express

6.1 Start VS2015 Web Express and create a new project.

6.2 Choose ASP.NET Web Application from Templates > Web.

6.3 Select MVC template.

6.4 Your ASP.NET application was created! In the next section, we will show how to deploy it.

7. Deploying ASP.NET MVC Application from VS2015 Web Express

7.1 Right-click on your project name in the explorer panel (it is highlighted on the screenshot) and select “Publish”.

7.2 Select “Custom” publish targetagain.

7.3 Enter Profile name and click OK.

7.4 Go to Azure panel again. Go to All resources and select your virtual machine. Copy and note down the Virtual Machine Public IP Address.

7.5 Now go to IIS Manager panel again. Check the Connections panel on the left and copy the site name under Sites. 

7.6 Return to the VS2015 Web Express and fill in the Connection settings. Here you will need your IP address and site name from previous steps. Then click “Publish”.

7.7 Check the “Save this certificate for future sessions” checkbox, then click “Accept” to accept the security certificate.

7.8 Now a green checkmark should appear near to Validate Connection button. Click “Next”. 

7.9 Set Configuration to Release, check all 3 checkboxes in File Publish Options, and click “Next”.

7.10 Here you can preview the app, but we will just click “Publish” to finish the deployment process.

7.11 In Visual Studio output console you can see the “Web App was published successfully” message and the IP address to access the app.

7.12 Congratulations! This is is your newly deployed ASP.NET application. Now you can play with it further, or try our AWS Web Server Setup Tutorial. 

The post How to setup a new Windows Server with ASP.NET MVC Application on Azure Virtual Machine appeared first on ByteScout.

1. Setting Free Trial Account on AWS

Go to – http://aws.amazon.com/free/.

1.1 Enter email and check “I am a new user”. Click “Sign in using our secure server”.

1.2 Fill form below.

1.3 Fill in your personal or company account details.

1.4 Enter Credit card details and complete identity verification in the next screen.

1.5 Now go to the AWS Console and log in with your AWS credentials.

1.6 You can browse console navigating top side links.

2. Creating and configuring AWS EC2 Instance

2.1 Click on “Launch Instance” button.

2.2 Select Amazon Machine Image (AMI): Microsoft Windows Server.

2.3 Choose an Instance type: General Purpose, t2 micro.

2.4 Configure EC2 Instance Details.

2.5 Add Storage.

2.6 Tag Instance.

2.7 Configure Security Group.

1. Add Http Port – 80
2. Add Web deployment port – 8172

2.8 Review Summary and click “Launch”.

2.9 Create a key pair, download it and store in a secure place.

2.10 Launch Status screen. The instance you created is now launching.

2.11 Now EC2 Instance is ready to use, click on EC2 dashboard icon.

2.12 Then click on Running Instances.

2.13 Here you will see a list of your web servers. Your new IIS web server can be still initializing. We will continue to work with the server in the next section.

3. Connecting to EC2 remote desktop

3.1 Now when the server is initialized, you can connect to it. Click “Connect” button to download remote desktop file (.rdp).

3.2 Click “Download Remote Desktop File” to start downloading, then you will need to click “Get Password” button.

3.3 Click “OK” to save the .rdp file.

3.4 Now click to “Get Password”, then click “Browse” and choose the folder you’ve saved you Key Pair in step 2.9.

3.5 Click “Decrypt Password”.

3.6 Copy your credentials to notepad.

3.7 Right-click on the .rdp file and select Connect.

3.8 Now check “Don’t ask me again” checkbox and click Connect again to allow remote connection.

3.9 Enter your credentials.

3.10 Check “Don’t ask me again” checkbox and click “Yes”.

4. Setting IIS on EC2 Instance

4.1 Open Server Manager by clicking on its icon on the taskbar.

4.2 Click “Add roles and features”.

4.3 Roles and Features Wizard opens. Click “Next”.

4.4 Select “Role-based or feature-based installation” and click “Next”.

4.5 Select “Select a server from the server pool”, then choose your server and click “Next”.

4.6 Select “Web Server (IIS)” from “Server Roles” list and click “Next”.

4.7 Select following features:
.NET Framework 3.5 Features,
ASP.NET 4.5.

4.8 Click “Next”.

4.9 Let’s select Role Services: select items highlighted on the screenshots below and click “Next”.

4.10 Click “Install” and wait until the installation is complete.

4.11 Click “Close”.

5. Installing Web deploy package on EC2 Instance

5.1 Go to http://www.microsoft.com/web/downloads/platform.aspx, download, and run Microsoft Web Platform Installer.

5.2. Using the installer search field, find and select Web Deploy 3.6 and click “Add”

5.3 Then click “Install”.

5.4 Accept the Microsoft license terms, then wait until the end of the installation and click “Finish”.

6. Creating ASP.NET MVC Application using VS2015 Web Express

6.1 Start VS2015 Web Express and create a new project.

6.2 Choose ASP.NET Web Application from Templates > Web.

6.3 Select MVC template.

6.4 Your ASP.NET application was created! In the next section, we will show how to deploy it.

7. Deploying ASP.NET MVC Application from VS2015 Web Express

7.1 Right-click on your project name in the explorer panel (it is highlighted in the screenshot) and select “Publish”.

7.2 Select “Custom” publish targetagain.

7.3 Enter Profile name and click OK.

7.4 Go to EC2 Management Console now and check Instances. Copy and note down Public DNS Address.

7.5 Now go to IIS Manager panel again. Check the Connections panel on the left and copy the site name under Sites. 

7.6 Return to the VS2015 Web Express and fill in the Connection settings. Here you will need your Public DNS address and site name from previous steps. Then click “Publish”.

7.7 Check the “Save this certificate for future sessions” checkbox, then click “Accept” to accept the security certificate.

7.8 Now a green checkmark should appear near to Validate Connection button. Click “Next”. 

7.9 Set Configuration to Release, check all 3 checkboxes in File Publish Options, and click “Next”.

7.10 Here you can preview the app, but we will just click “Publish” to finish the deployment process.

7.11 In Visual Studio output console you can see the “Web App was published successfully” message and the address to access the app.

7.12 Congratulations! You have created and configured AWS EC2 Instance, then you have installed a web server, and also you have created and deployed an ASP.NET application. Now you can continue your experiments with EC2 on yourself, or check our guide on how to set up the same environment and deploy an ASP.NET application on Azure Virtual Machine.

The post How to setup a new Windows Server with ASP.NET MVC Application on AWS EC2 appeared first on ByteScout.

ByteScout updated

1. ByteScout Barcode Generator SDK 4.40.862
2. ByteScout Barcode Generator freeware 4.40.862
3. ByteScout Barcode Reader SDK 8.40.1534
4. ByteScout Barcode Reader Freeware 8.40.1534
5. ByteScout Spreadsheet SDK 2.50.1535
6. ByteScout PDF Generator SDK for JS 1.16.152

on April 12, 2016.

Whats’s new:

Barcode Generator SDK 4.40.862

• fixed bug with barcode placement on rotated PDF page
• added new Barcode.DrawImagesToPDF() method with callback parameter allowing to add different images on each PDF page in one pass
• fixed ValueIsValid() method for DataMatrix symbology

Barcode Generator freeware 4.40.862

• bug fixes and improvements

Barcode Reader SDK 8.40.1534

• improved QR Code decoding
• fixed duplication of detected barcodes in rare cases
• fixed PDF417 error correction
• fixed MinimalDataLength property
• demo Application: Added “Export Results As…” button

Barcode Reader Freeware 8.40.1534

• improved QR Code decoding
• fixed duplication of detected barcodes in rare cases
• fixed PDF417 error correction
• fixed “Minimal decoded data length” option
• demo Application: Added “Export Results As…” button

Spreadsheet SDK 2.50.1535

• improved support of old versions of protected XLS documents
• improved parsing of formulas
• added Spreadsheet.ExportToJSON() and Spreadsheet.ImportFromJSON() methods
• added support of Open XML and OpenDocument files with wrong file extension

PDF Generator SDK for JS 1.16.152

• improved javascript pdf generation
• improved handling of missing/corrupted images: now if .stopOnInvalidImages is true (by default) then script throws BytescoutPDFFatalError exception on invalid images

The post Updated Software: ByteScout Barcode Generator SDK 4.40.862, Barcode Reader SDK 8.40.1534, Spreadsheet SDK 2.50.1535, ByteScout PDF Generator SDK for JS 1.16.152, Barcode Reader Freeware 8.40.1534, Barcode Generator freeware 4.40.862 appeared first on ByteScout.

ByteScout updated software on May, 2016:

1. ByteScout SWF To Video SDK 2.12.1012
2. ByteScout Screen Capturing 2.52.1012
3. ByteScout Image To Video SDK 2.11.1012
4. ByteScout PDF Multitool 7.00.0.2474
5. ByteScout PDF Viewer SDK 7.00.0.2474
6. ByteScout PDF Renderer SDK 7.00.0.2474
7. ByteScout PDF SDK 1.2.0.97
8. ByteScout PDF Extractor SDK 7.00.0.2474
9. ByteScout PDF To HTML SDK 7.00.0.2474

Whats’s new:

SWF To Video SDK 2.12.1012

• minor improvements in SWF to video conversion.

Screen Capturing 2.52.1012

• fixed crash on Run/Pause while recording video on some configurations
• screen video recording minor fixes and improvements.

Image To Video SDK 2.11.1012 

• minor bug fixes and stability improvements in jpeg to video conversion.

PDF Multitool 7.00.0.2474

• greatly improved font rendering quality
• added recent document list to “Open PDF Document” button
• selection can be resized now
• added Extract JSON feature
• improved Table Detector UI
• added debug option “Show Detected Extraction Columns” to the context menu to display the detected columns on the current page. Becomes visible only after running any extraction against the current displayed page
• fixed font rendering issue on 32-bit Windows
• fixed bug in installer causing some files from previous installation were interfering with updates
• other minor improvements and bug fixes.

PDF Viewer SDK 7.00.0.2474

• greatly improved font rendering quality
• fixed bug in installer causing some files from previous installation were interfering with updates
• PDF Multitool: Fixed font rendering issue on 32-bit Windows
• reworked the registration checking. Now the library will not throw an exception, but work in demo mode if you missed or input wrong RegistrationName and RegistrationKey
• PDF Multitool: Added recent document list to “Open PDF Document” button
• PDF Multitool: Selection can be resized now
• PDF Multitool: Added Extract JSON feature
• PDF Multitool: Improved Table Detector UI
• PDF Multitool: Added debug option “Show Detected Extraction Columns” to the context menu to display the detected columns on the current page. Becomes visible only after running any extraction against the current displayed page
• other minor improvements and bug fixes.

PDF Renderer SDK 7.00.0.2474

• greatly improved font rendering quality
• GetPageRect* methods did not take the page rotation into account
• fixed bug in installer causing some files from previous installation were interfering with updates.
• reworked the registration checking. Now the library will not throw an exception, but work in demo mode if you missed or input wrong RegistrationName and RegistrationKey
• fixed font rendering issue on 32-bit Windows
• PDF Multitool: Added recent document list to “Open PDF Document” button
• PDF Multitool: Selection can be resized now
• PDF Multitool: Added Extract JSON feature
• PDF Multitool: Improved Table Detector UI
• PDF Multitool: Added debug option “Show Detected Extraction Columns” to the context menu to display the detected columns on the current page. Becomes visible only after running any extraction against the current displayed page
• other minor improvements and bug fixes.

PDF SDK 1.2.0.97

• added Document.FlattenDocument() method. Performs the flattening: replaces form widgets (radio buttons, checkboxes, text boxes, etc.) with static text to prevent the form changing
• added Page() constructor with UnitOfMesaure parameter to specify the custom page size in any units
• added Watermark object for easy adding of “watermark” text to document pages.

PDF Extractor SDK 7.00.0.2474

• added new DocumentPrinter utility class allowing to print PDF documents silently (without any user dialogs)
• added new JSONExtractor class
• added override for DocumentSplitter.Split() method allowing to specify the output folder for generated files
• fixed multi-threading bug in DocumentSplitter
• TableDetector now respects extraction area set by SetExtractionArea() method
• new properties in extraction classes: ExtractionColumns – contains coordinates of detected columns; CustomExtractionColumns – allows to override the column detection
• GetPageRect* methods did not take the page rotation into account
• fixed bug in installer causing some files from previous installation were interfering with updates
• reworked the registration checking. Now the library will not throw an exception, but work in demo mode if you missed or input wrong RegistrationName and RegistrationKey
• PDF Multitool: Added recent document list to “Open PDF Document” button
• PDF Multitool: Selection can be resized now
• PDF Multitool: Added Extract JSON feature
• PDF Multitool: Improved Table Detector UI
• PDF Multitool: Greatly improved font rendering quality
• PDF Multitool: Added debug option “Show Detected Extraction Columns” to the context menu to display the detected columns on the current page. Becomes visible only after running any extraction against the current displayed page
• PDF Multitool: Fixed font rendering issue on 32-bit Windows
• other minor improvements and bug fixes.

PDF To HTML SDK 7.00.0.2474

• fixed bug in installer causing some files from previous installation were interfering with updates
• reworked the registration checking. Now the library will not throw an exception, but work in demo mode if you missed or input wrong RegistrationName and RegistrationKey
• PDF Multitool: Added recent document list to “Open PDF Document” button
• PDF Multitool: Selection can be resized now
• PDF Multitool: Added Extract JSON feature
• PDF Multitool: Improved Table Detector UI
• PDF Multitool: Greatly improved font rendering quality
• PDF Multitool: Added debug option “Show Detected Extraction Columns” to the context menu to display the detected columns on the current page. Becomes visible only after running any extraction against the current displayed page
• PDF Multitool: Fixed font rendering issue on 32-bit Windows
• other minor improvements and bug fixes.

The post Updated Software: ByteScout SWF To Video SDK 2.12.1012, Screen Capturing 2.52.1012, Image To Video SDK 2.11.1012, PDF Multitool 7.00.0.2474, PDF Viewer SDK 7.00.0.2474, ByteScout PDF Renderer SDK 7.00.0.2474, PDF SDK 1.2.0.97, PDF Extractor SDK 7.00.0.2474, PDF To HTML SDK 7.00.0.2474 appeared first on ByteScout.