# Migrated Structure

Coming from a `C# Winforms` project, `WebMAP5` adjust its structure to be implemented with all `Angular` needs and its proper organization of files. Setting up the `front-end` environment begins from understanding how the `back-end` is structured. A solution in a `Winforms Application` has a structure as the following sample:

```markup
<img src="./images/winforms.png" width="250">
```

On the other hand, we have `Angular` structure that needs modules, indexes and their files for each component. To apply this transformation `WebMAP5` took Winforms namespaces as a whole module. Each level of the namespace has its own `index.ts` and a group of essential files for angular: html, css and the typescript file. The diagram below explains it, in this case the app.module.ts corresponds to the startup application project and the other namespaces are modules imported to it: &#x20;

![](/files/-MG5p5OMK-ZOqCOtO3Hj)

## Files Samples

### app.module.ts

On this side is where all namespaces, that becomes modules, are imported. &#x20;

<div align="left"><img src="/files/-MG5pBruPrcgH0HNtbbE" alt=""></div>

### sks.module.ts

This sample of a module imports indexes from sks and sksfake directory. Those indexes comes with other calls until they get to the component.

```markup
<img src="./images/sksModuleTS.png">
```

### Namespace files, usage of import/export between levels and conventions

```markup
<img src="./images/files.png">
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gapvelocity.ai/webmap/general/frontend/documentation/winforms-angular-components/migrated-structure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.