Localization and Globalization testing

Globalization is the process of designing and developing applications that function for multiple cultures.

Localization is the process of customizing your application for a given culture and locale.

Globalization focuses your applications capibilities on users as a generic user-base, whereas localization focuses on subsets of users in a given culture or locale. So you can think of globalization as a strategic venue, where as localization is tactical.

MSDN Globalization vs. Localization

Localization makes our software acceptable for a particular culture or locale that makes users to accept the adaptable software. For example Adobe Pdf is used in many languages. It is available in Japanese, Chines or even English :)

Localization testing checks how well the build is translated into a particular target language in given geaographic locale.

Globalization makes our software function in any culture/locale. The goal is to detect potential problems in application design that could hamper globalization. We work to make sure that the code can handle all international support.

For instance, we should support text data in the ANSI (American National Standards Institute) format. Unicode support should be tested. We should handle strings in each language. Right to left and Left to right scripts shall also be tested with.

Difference between Nuget and Chocolatey

NuGet is designed to allow you to easily add code libraries to your project. Things like JSON.NET, Entity Framework, etc.

Chocolatey is actually built on top of the NuGet package system, but it is designed to fill a different need. Chocolatey wraps up applications and other executables and makes it easy to install them on your computer. For example, tools like Git and Notepad++, etc. can be easily installed with a command like: cinst git.

To know more about chocolate and how to install it please refer my earlier blog post on W3LC : http://www.w3lc.com/2017/11/what-is-chocolatey-and-how-to-install.html

https://chocolatey.org/packages has a list of all the applications that can be installed.

If you have an open source project which is a library that is to be used in other developers' projects, then you should submit it to NuGet.

If it is an application that users would normally install, then create a Chocolatey package that users can easily install and update from the command line.

Details of different Package manager tools and where does Chocolate fits in:

OneGet has been renamed to Package management. It's core provides you with discovery and installation/uninstallation of various packages. OneGet is often referred to as a "package manager manager".

OneGet is a part of WMF 5 installation. Think of this as the "central concept" in the big picture. Now let's talk about packages.

Packages are fetched through package providers. E.g. PowerShellGet is one package provider for OneGet. Powershell gallery is a package source of of PowershellGet (PSGet). A provider can have multiple sources where it can search for it's packages.

E.g for the nuget-package provider; you can easily add the sources to the public nuget gallery and register your own e.g. myget source so it can be used when searching for packages.

Chocolatey is just another example of a package provider. Earlier it had to be installed and was a seperate module with it's own logic. The new Chocolatey provider conforms to the new framework of installing / managing packages.

So on a more conceptual level; a package provider itself contains information on how to install and search it's sources (sources can be registered/unregistered for each and every provider); whilst OneGet (Package management, package manager manager) works on the level above, managing package providers and interfacing this all for you.

OneGet glues it all together; while the providers itself knows how to handle packages based on it's registered sources.

Hope this explains it on the conceptual level.

See also this nice blogpost here explaining a few things more in detail:https://blogs.technet.microsoft.com/packagemanagement/2015/05/05/10-things-about-oneget-that-are-completely-different-than-you-think/

If you want to play around with package providers and sources :

 Get-PackageProvider # -Shows package providers installed on your machine)
 Find-PackageProvider # -Find online package providers you can pull down and install)
 Get-PackageSource # -List all package sources, with it's provider name)
 Register-PackageSource # -Register new package source for a provider)

Pen drive show empty even when data exists : SOLVED : Hidden files/ Virus Security

This is a common symptom when your computer, hard drive or the PD is infected with a malware. You are 100% sure that the disk contains data but that is not visible in the file explorer.

Now there can be multiple ways ti identify and fix it. They are mentioned as following:

1. Simplest is to check if the files are hidden and your explorer settings do not allow you to view hidden files.
To overcome this go to the file/folder settings View -> And select the 'Show System or Hidden files'

2. You definitely have to eventually scan the disk by Antivirus. Do that and the disk will become clean again

3. There is a short DOS level command that could help you overcome the situation.

Steps:

a. Open the DOS command. For the newbies, its a Black command terminal window
You can start it by goint to Start -> Run ->cmd

b. Change your working drive to the target drive. For eg. if your pendrive or disk is E: drive run the following command on DOS terminal
That is, type the following command and press Enter

E:\>attrib -h -r -s /s /d e:\*.*

Now this magical command will not display anything on the terminal. But your work will be done!

This will recursively make all your files and folder on the target drive as Non-hidden.

So now go to File System explore of Windows and open the drive. Voila! Your items are now visible!