Check if devon4net cobigen guide is valid

[isandesh1986]

Check if devon4net cobigen guide is valid https://devonfw.com/website/pages/docs/devonfw-guide_devon4net.wiki_cobiGen.asciidoc.html

you might want to get in contact with @jmsanmu

if this tutorial remains valid, we should try to create a tutorial within devonfw-tutorials/tutorials to keep continuous quality and let it be tested automatically.

[quantumfate]

1. The first link in the mentioned guide on this part is broken.

2. The link that references the tutorial for setting up an .NET environment is broken. 2.1 I think I found the correct source. Take a look here

3. The link to the picture that references Devon4Net.WebAPI.Implementation's repositories is broken.

[quantumfate]

TL;DR the guide is not valid anymore because it's outdated

It took me a while to follow the guide because resources are missing. I adapted the guide inside the devon IDE even though the source I linked refers to installing the dotnet sdk outside the devon IDE on the user's system.

The goal of this guide is to generate files with cobigen. So installing the devon ide along with cobigen is necessary. Installing dotnet on your system doesn't make sense.

I found the dotnet setup guide that the mentioned guide is referring to. It instructs the user to setup vscode and .net sdk outside of the devon ide and that shouldn't be done when you intend to use cobigen, right? Because the dotnet sdk will be configured and installed automatically by running the command devon dotnet.

This also makes the step obsolete to run dotnet new -i `Devon4Net`.WebAPI.Template because this will be done by setting up the dotnet sdk in the devon IDE. Take a look at the dotnet command.

After I managed to install the templates with dotnet new Devon4NetAPI I noticed cobigen created a new directory upon generation because the existing template directory name that was created by the mentioned command is different than the directory name that cobigen writes the output to. I used a workaround by editing the input's directory name matching the cobigen output's directory name. Editing the x-rootpackage like mentioned in the guide and in the cobigen api plugin does actually not influence this behavior.

It doesn't matter if the output is generated correctly or not because in both cases the input created by devon dotnet new Devon4NetAPI has a lot of issues itself but mostly wrong imports.

The errors in the base project are the only criteria that need to be fixed for this guide to be valid. @maybeec @isandesh1986