Programming Styles of .NET and Java Platforms

Namespaces vs Packages

The names of packages in the Java version of Aspose.BarCode is different from the namespaces in the .NET version:

Namespace in Aspose.BarCode for .NET Package in Aspose.BarCode for Java
Aspose.BarCode com.aspose.barcode


Class names are the same between the .NET and Java versions.

Class Name in Aspose.BarCode for .NET Class Name in Aspose.BarCode for Java
BarcodeGenerator BarcodeGenerator
BarCodeReader BarCodeReader
Margins Margins

Enumerations vs Integer Constants

Enumerations in the .NET version were ported to Java as classes with public integer constants.

The enumeration in Aspose.BarCode for .NET Constant in Aspose.BarCode for Java
EncodeTypes.Code128 EncodeTypes.CODE_128
All constants are integer values in Aspose.BarCode for Java whereas in the .NET version, a parameter, return value or property is of an enumerated type.


 public void Save(string fileName, ImageFormat fileFormat)


 public void save(java.lang.String fileName, int fileFormat)

The main reason why we didn’t use Java enum is to stay compatible with J2SE 1.4.x as Java enum appeared only in J2SE 5.0.


Method names follow the accepted programming practices for each platform and therefore differ in the coding style.

Method Name in Aspose.BarCode for .NET Method Name in Aspose.BarCode for Java
The methods are different in the casing only (method names in the Java version start with a lowercase letter).

Properties vs Get/Set Methods

Properties of .NET classes are ported to Java as getter and setter methods. The original name of the method has got and set prefixes added to it.

Property Name in Aspose.BarCode for .NET Getter and Setter in Aspose.BarCode for Java
BarcodeGenerator.CodeText BarcodeGenerator.setCodeText(), BarcodeGenerator.getCodeText()

Indexed Properties

Indexed properties in .NET are ported to Java as get() and set() methods in most cases.