# CSharpSECSTools

**Repository Path**: idkook/CSharpSECSTools

## Basic Information

- **Project Name**: CSharpSECSTools
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2025-09-02
- **Last Updated**: 2025-09-02

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# CSharpSECSTools

**CSharpSECSTools** is a project for those that are working primarily in the realm of shop floor automation in the semiconductor industry.
If you do not work in that industry or you are not familiar with the [SEMI Standards](www.semi.org/en/standards)
**E4**, **E5**, **E30**, **E37**, el al, this project is probably not for you.

This project provides some tools / API libraries that will help
in writing software for equipment interfaces and / or equipment simulators.

## Get the code

Use the `git clone` command to get the code.

`git clone https://github.com/dkaip/CSharpSECSTools CSharpSECSTools`

This will create a `CSharpSECSTools` directory in your current directory

## Building

Currently, this project may be built using `dotnet` version 6.0.108. The unit tests are run using NUnit.3.13.3.  I expect that any more recent NUnit (i.e. NUnit.3.13.3+) will work as well.

`dotnet build --configuration Debug` may be used to build debug versions of the files.

`dotnet build --configuration Release` may be used to build release versions of the files.

`dotnet clean --configuration Debug` may be used to clean debug versions of the files.

`dotnet clean --configuration Release` may be used to clean release versions of the files.

`dotnet test --configuration Debug` may be used to run the unit tests on debug versions of the files.

`dotnet test --configuration Release` may be used to run the unit tests on release versions of the files.

`dotnet build` or `dotnet clean` or `dotnet test` will produce, clean, or test debug versions.

## Documentation

Find the documentation WEB site here [CSharpSECSTools](https://dkaip.github.io/CSharpSECSTools).

There is documentation in the source files
so that IntelliSense capable editors/IDEs will be able to provide support for method completion, etc.
In addition there is documentation in the `DocFx` folder.

The documentation in this folder can be processed with `docfx` to produce a WEB site that will
be generated in the `docs` folder.  The command to do this is `docfx docfx.json` which should
be executed within the `DocFx` folder.

As stated the resulting output documentation will end up in the `docs` folder.  Running the command
`docfx serve` in the `docs` folder will serve the WEB site at localhost:8080 unless something
else is already using that port.

Please refer to the documentation available for DocFx for more information.

## Usage Notes

At the moment the SECSItems and SECSItemTests should work properly.  I have modified code 
in FixedBufferSimulatorConsole, SECSCommUtils, and EquipmentSimulatorSupportStuff so that
the project should at least compile (with some warnings) until I have the time to implement
and test those items.

## Miscellaneous

This version of this repository should be functionally the same as the Baseline version.  Since MonoDevelop seems to no longer be available for my platform I have switched to using Visual Studio Code for the editor and using the `dotnet` command from the command line.  I have also done modifications so that the build environment is for .NET 6.  As for code differences, I had to fix a couple of unit tests since `dotnet` seems to allow a little more precision for floating point numbers.  I removed the visibility of some "internal" classes and methods that should not have been public.  Some documentation was added as well.

## Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

## License

[Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0)