Before creating your COBOL cloud service, you need to decide on the structure of the solution, its projects, its roles and any existing COBOL code. You also need to decide how to handle your data, as blobs, table storage, Azure SQL Database or Azure Files, and whether you can use queues.
You can structure your solution with multiple projects and then add references to those projects in the required roles (see the project's References).
Your Microsoft Azure service can have one or more web and worker roles. These roles can interact with the runtime environment by using the Microsoft Azure Managed API. The bulk of your existing source code and business logic probably belongs in one or more separate projects in the solution. Some of the code might belong in the web or worker roles projects.
The solution can include the following:
You need to identify any existing COBOL code that is restricted to native COBOL and migrate it so that it can be built as .NET managed code.
You can handle your data using BLOBs, table storage, queues, or Azure SQL Database.
To handle queues, you might need code to:
To handle table storage, you might need code to: