jhipster / jhipster-dotnetcore

JHipster.NET blueprint

generator-jhipster-dotnetcore

JHipster blueprint

Big Picture

JHipster is a well-known platform for generating modern application in java world. JHipster provides a blueprints system that allows to override the default behavior of the generator

JHipster.NET is a blueprint that overrides the back-end part, originally generated in spring boot, by back-end in asp.net core. For the front-end all the common language can be used (angular, react, vue.js).

In alpha version we also have the possibility to choose either Blazor or Xamarin for the front.

This blueprint is an official blueprint of JHipster official-blueprints

Docs

Documentation and information about JHipster.NET are available here

Full documentation and information about JHipster are available here

Analysis of the sample project

https://github.com/jhipster/jhipster-sample-app-dotnetcore

Introduction

This is a JHipster blueprint, that is meant to be used in a JHipster application.

Gitter

https://gitter.im/JHipster-NET/jhipster-dotnetcore

Installation

With NPM

To install this blueprint:

npm install -g generator-jhipster-dotnetcore

To update this blueprint:

npm update -g generator-jhipster-dotnetcore

With Yarn

To install this blueprint:

yarn global add generator-jhipster-dotnetcore

To update this blueprint:

yarn global upgrade generator-jhipster-dotnetcore

Usage

To use this blueprint, run the below command

jhipster-dotnetcore

Using Docker

Build the Docker images:

docker build -t jhipster-generator-dotnetcore:latest .

Make a folder where you want to generate the Service:

mkdir service
cd service

Run the generator from image to generate service:

docker run -it --rm -v $PWD:/home/jhipster/app jhipster-generator-dotnetcore

🚦 What we have now

✅ General App generation

• jhipster-dotnetcore
  • JWT : ✅
  • Oauth2 : ✅

✅ Entity generation

• jhipster-dotnetcore <entity-name>

✅ JDL Entity model support generation

• jhipster-dotnetcore import-jdl my_file.jdl

Running the generated app in a Docker container

1. Build the Docker image of the app

docker build -f "[Dockerfile path]" -t [An image name]:[A tag] "[Application root path]"

2. Run your image in a Docker container

docker run -d -p [A host port]:8080 [Image name]:[Image tag]

3. Open your favorite browser at localhost:[Chosen host port] and enjoy ! 🐳

Docker compose file can be used to start the application with database as a service. To build images, run

docker compose -f docker/app.yml build

To start services, use

docker compose -f docker/app.yml up

In case of Oracle database, see official documentation

License

Apache-2.0 © JHipster.NET

jhipster-dotnetcore's Issues

Mongo support

@ItsInsajd and @AdrianDo Did you work on mongo support ?
I've seen a few commits on your fork. Do you need help ?

Add Monitoring

Like jhipster generator add one monitoring stack like ELK ( https://www.elastic.co/what-is/elk-stack ) or TICK stack ( https://www.influxdata.com/time-series-platform/ )

Add support for Service Discovery and Config Server

Like jhipster generator these features could be added with the library https://steeltoe.io/

Can we add service/dependency injection and repository layers for generated entities as for main generator JHipster ?

I add this issue to see if we can add service (dependency injection) and repository layers for generated entities as for main generator JHipster ?

Cannot read property 'toLowerCase' of undefined

Hi!

I'm clone this repository in my machine and try to exec this blueprint with following commands:

git clone https://github.com/jhipster/jhipster-dotnetcore.git
ren jhipster-dotnetcore generator-jhipster-dotnetcore
cd generator-jhipster-dotnetcore
npm link
cd ..
cd myApp
npm link generator-jhipster-dotnetcore

In the last step, when I select one, some or all modules, I have this exception:

Installing languages: en for server
events.js:167
      throw er; // Unhandled 'error' event
      ^

TypeError: Cannot read property 'toLowerCase' of undefined
    at toNoCase (C:\Users\Roberto Ruiz\Source\Repos\generator-jhipster-dotnetcore\node_modules\to-no-case\index.js:28:17)
    at toSpaceCase (C:\Users\Roberto Ruiz\Source\Repos\generator-jhipster-dotnetcore\node_modules\to-space-case\index.js:18:10)
    at toPascalCase (C:\Users\Roberto Ruiz\Source\Repos\generator-jhipster-dotnetcore\node_modules\to-pascal-case\index.js:18:10)
    at module.exports.configureGlobalDotnetcore (C:\Users\Roberto Ruiz\Source\Repos\generator-jhipster-dotnetcore\generators\languages\index.js:39:43)
    at Object.<anonymous> (C:\Users\Roberto Ruiz\Source\Repos\generator-jhipster-dotnetcore\node_modules\generator-jhipster\node_modules\yeoman-generator\lib\index.js:424:27)
    at C:\Users\Roberto Ruiz\Source\Repos\generator-jhipster-dotnetcore\node_modules\run-async\index.js:25:25
    at new Promise (<anonymous>)
    at C:\Users\Roberto Ruiz\Source\Repos\generator-jhipster-dotnetcore\node_modules\run-async\index.js:24:19
    at self.env.runLoop.add.completed (C:\Users\Roberto Ruiz\Source\Repos\generator-jhipster-dotnetcore\node_modules\generator-jhipster\node_modules\yeoman-generator\lib\index.js:425:13)
    at runCallback (timers.js:705:18)
Emitted 'error' event at:
    at Immediate.setImmediate (C:\Users\Roberto Ruiz\Source\Repos\generator-jhipster-dotnetcore\node_modules\generator-jhipster\node_modules\yeoman-generator\lib\index.js:433:22)
    at runCallback (timers.js:705:18)
    at tryOnImmediate (timers.js:676:5)
    at processImmediate (timers.js:658:5)

Is sufficient data to resolve this issue? My Operating System is Windows 10.

Thanks a lot!

Generating ci-cd in generated app

https://www.jhipster.tech/setting-up-ci/

Generating entities from model

Hi, in original jhipster for java it is possible to generate entities from JDL model.
Is it possible in dotnet blueprint, or was there any idea to let say create cs file with list of classes and then recreate all entities ? I think that would be nice.

Backend test generation

To test that the generated app works, we need to generate the backend tests. These tests are composed of originals JHipster backend tests and more.

Add support for OAuth 2.0 / OIDC Authentication

The main JHipster generator supports OAuth 2.0 / OIDC. It'd be nice if its blueprints did as well.

Add vs code debug support

Overview of the feature request

For debug in vs code jhipster we can add task like :

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "name": "Debug my blueprint",
            "preLaunchTask": "link generator",
            "program": "${workspaceFolder}/node_modules/generator-jhipster/cli/jhipster.js",
            "args": [
                "-d",
                "--skip-checks",
                "--skip-git",
                "--skip-cache",
                "--skip-install",
                "--blueprint",
                "dotnetcore"
                ],
            "console": "integratedTerminal",
            "cwd": "/tmp/debugVsCodeFolder"
        }, {
            "type": "node",
            "request": "launch",
            "name": "Debug my entity",
            "preLaunchTask": "link generator",
            "program": "${workspaceFolder}/node_modules/generator-jhipster/cli/jhipster.js",
            "args": [
                "entity",
                "Bank"
                ],
            "console": "integratedTerminal",
            "cwd": "/tmp/debugVsCodeFolder"
        }
    ]
}

we can take inspiration from https://github.com/jhipster/generator-jhipster/blob/master/.vscode/launch.json

Does not generate react ui code

I have used jhipster on prior projects to generate java backend with react ui.

When I tried to generate a new project for dotnetcore - it only generates angular - not react.

Add SonarQube

In order to evaluate the quality of the generated code, we need to add SonarQube in the generated application.

Add SonarCloud analysis on generator

@deepu105, @pascalgrimaud or @jdubois can you create the project on sonarcloud ?

Migrate to .Net Core 3.0

.Net Core 3.0 is now public with cool a cool feature list:
https://devblogs.microsoft.com/dotnet/announcing-net-core-3-0/

A .net core hipster must use 3.0 to be in the cutting edge 😄

Add possibility to audit entities

Support more databases

One of the features asked by many people is the possibility to choose more databases.
In order to make it, Entity Framework Core will be really helpfull and will facilitate their integration.
Currently, the only choice is a Sqlite database stored in RAM.

Could not import a custom JDL, but console response has successful

Hi again! I'm import a custom JDL (generated in JDL Studio, of course), and the console returns a success log.

PS C:\Users\rruiz\Desktop\test> jhipster import-jdl .\jhipster-jdl.jh --skip-checks
INFO! Using JHipster version installed globally
INFO! Executing import-jdl .\jhipster-jdl.jh
INFO! Options: skipChecks: true, from-cli: true, skip-checks: true
INFO! Found .yo-rc.json on path. This is an existing app
INFO! The JDL is being parsed.
INFO! No change in entity configurations, no entities were updated.
INFO! The JDL has been successfully parsed

But, in the dotnet solution, i didn't watch the models.

NOTE: Without "skip checks", the message logs are similar.

Exists a solution (at least, temporally) for this incident?

Thanks a lot!

Travis build error when running eslint

All travis builds are failing - see https://travis-ci.com/jhipster/jhipster-dotnetcore/builds/134947981 for detailed logs.
Eslint is complaining of 78 problems such as identation, values never used, not defined variables, etc across many of the generator's files.

Adding api /management/info

In the java generator on the url /management/info the info on the profile and banner is return :
exemple of response :
http://localhost:8080/management/info :

{
  "display-ribbon-on-profiles" : "dev",
  "activeProfiles" : [ "dev", "swagger" ]
}

Change the generation path of the frontend entities

Currently, the generation of Angular frontend entities is done on the same paths as in the generation of a Java application. This prevents us from linking the .Net backend to the frontend, from being able to build and run the application and backend tests. We need to rewrite the different generation paths of these entities to suit the .Net C # version tree.

Integration of the needle API

Currently, during a modification of the data model we regenerate all the files of the entities of the backend without using the needles.
In the future we have to integrate these in order for example to add fields in the entities.

Another problem that it could solve:
When generating controllers and tests we sometimes need to access the associated entities. The problem can then occur because at a time T the referenced entities may not have been created yet. So we need to return to the controllers and tests that reference these entities during their creations to add the missing lines of code.

Add posibility to upgrade generated database

Like the jhipster version for java, it uses liquibase to generate changes in the database. It would be nice to add this feature.

EntityFramework does it using "dotnet ef migrations add Update_1"

Bug with internationalization support

Currently, we have a problem with the support of internationalization.
When enabled and the choices of a native language and additional languages made, the corresponding files are generated. The problem occurs when launching the application in the browser. The language choice tab doesn't appear !

Test not working with authorize attribute

We notices two integration tests are not working due to authorized endpoints.

Installation error

This does not work
npm install -g generator-jhipster-jhipster-dotnetcore

also tried
npm install -g https://github.com/jhipster/jhipster-dotnetcore.git

Error details
events.js:183
throw er; // Unhandled 'error' event
^

Error: ERROR! The generator-jhipster-jhipster-dotnetcore blueprint provided is not installed. Please install it using command npm i -g generator-jhipster-jhipster-dotnetcore.
at Environment.error (/usr/local/lib/node_modules/generator-jhipster/node_modules/yeoman-environment/lib/environment.js:176:40)
at module.exports.error (/usr/local/lib/node_modules/generator-jhipster/generators/generator-base.js:1427:18)
at shelljs.exec (/usr/local/lib/node_modules/generator-jhipster/generators/generator-base-private.js:790:22)
at /usr/local/lib/node_modules/generator-jhipster/node_modules/shelljs/src/exec.js:127:9
at ChildProcess.exithandler (child_process.js:282:5)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at maybeClose (internal/child_process.js:925:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)

generator-jhipster-dotnetcore@latest' is not in the npm registry.

Hi,

I am following the instruction on the ReadMe page, but I try to install the dotnetcore generator, I get the error blow. If it is not available in npm registry, can I clone the project and link it as you would do for Development.

npm install -g generator-jhipster-dotnetcore
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/generator-jhipster-dotnetcore -
Not found
npm ERR! 404
npm ERR! 404 'generator-jhipster-dotnetcore@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/ahmeddini/.npm/_logs/2019-08-12T15_42_53_460Z-debug.log

add --skip-client and --skip-server options

Allow to generate only frontend or backend app by adding --skip-client/--skip-server options

build error - No matching version found for [email protected]

can you publish the new npm package [email protected] ?

build system

appreciate the work you do here,
i suggest the cakebuild as the build system,
but i think the gradle ecosystem has something for dotnet too.

Use github actions intead of travis

Like main jhipster generator we can migrate travis build to github actions

Error when Creating Jhipster .Net Core solution.

`Creating Jhipster .Net Core solution.

events.js:183
throw er; // Unhandled 'error' event
^

TypeError: dotnet.newSln(...).then(...).catch(...).finally is not a function
at module.exports.end (/usr/local/lib/node_modules/generator-jhipster-dotnetcore/generators/server/index.js:176:29)
at Object. (/usr/local/lib/node_modules/generator-jhipster-dotnetcore/node_modules/generator-jhipster/node_modules/yeoman-generator/lib/index.js:424:27)
at /usr/local/lib/node_modules/generator-jhipster-dotnetcore/node_modules/run-async/index.js:25:25
at new Promise ()
at /usr/local/lib/node_modules/generator-jhipster-dotnetcore/node_modules/run-async/index.js:24:19
at self.env.runLoop.add.completed (/usr/local/lib/node_modules/generator-jhipster-dotnetcore/node_modules/generator-jhipster/node_modules/yeoman-generator/lib/index.js:425:13)
at runCallback (timers.js:794:20)
at tryOnImmediate (timers.js:752:5)
at processImmediate [as _immediateCallback] (timers.js:729:5)`

Publish the generated app

one time per day ? or each commit ? publish the generated app to
https://github.com/jhipster/jhipster-sample-app-dotnetcore

Only Java files are being generated

Tested commit 90d3406 and it generates C# code.
But with the latest commits jhipster only creates java files. Seems that the dotnetcore generator is not called. Others are having related issues.
I'm using Windows 10, Node v10.16.0 LTS and jHipster v6.1.2

@danielpetisme Thanks a lot, was able to "npm link" inside this repository cloned to my local disk (on MacOS). Then I created a folder for my app and went in there (cd ), did "npm link generator-jhipster-dotnetcore" which created a folder "node_modules" inside. After running "jhipster -d --blueprint dotnetcore" I see that the blueprint is picked up (as evidenced in launch sequence of jHipster: "INFO! Options: d: true, blueprint: dotnetcore, from-cli: true") but it generates Java application nevertheless. Is there some questionnaire answer that I choose that screws things up? (I chose monolithic with Postgres, no distributed cache, with Angular)
Note: I have "dotnet" available as part of 2.2.300 SDK installed on my MacOS.

same errors. it is still generating java files.
Please update readMe with more details

Having the same issues, jhipster generates only java files

Originally posted by @ivanmonteiro in #2 (comment)

Entity field types nullable or not?

In the Java version, the types proposed for the fields of the entities are nullable but one can add to these fields an Required annotation.
In C #, equivalent types are not nullable unless you add the suffix "?" (example: int?). Similarly, the [Required] annotation can be added to the fields.
The question raised here is to know if we should keep the default behavior of the types (not nullable) or add the suffix "?" to get exactly the same behavior as the Java version.

Update the Docker build

Verify the docker build is following the recommmandations of
https://dev.to/dotnet/how-you-can-dockerize-a-net-core-app-4h96?ocid=AID2417799_TWITTER_oo_spl100000934921659

Minor: Package.json not found (wrong location) and 'rimraf' not recognized

Hi!
When I finish the set-up to auto-generate solution, I observe some issues in the process.

First: The solution cannot find a package.json file
(Console lines)

I'm all done. Running npm --prefix src/Enfoke install for you to install the required dependencies. If this fails, try running the command yourself.
npm ERR! code ENOLOCAL
npm ERR! Could not install from "" as it does not contain a package.json file.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\rruiz\AppData\Roaming\npm-cache\_logs\2019-08-23T16_02_25_612Z-debug.log
Application successfully committed to Git.

If you find JHipster useful consider sponsoring the project https://www.jhipster.tech/sponsors/

Creating Enfoke .Net Core solution.

Client application generated successfully.

(Log debug file)

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   '--prefix',
1 verbose cli   'src/Enfoke',
1 verbose cli   'install' ]
2 info using [email protected]
3 info using [email protected]
4 verbose npm-session 74f4ce41e8434954
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 silly fetchPackageMetaData error for file: Could not install from "" as it does not contain a package.json file.
8 timing stage:rollbackFailedOptional Completed in 1ms
9 timing stage:runTopLevelLifecycles Completed in 26ms
10 verbose stack Error: ENOENT: no such file or directory, open 'C:\Users\rruiz\Desktop\test\package.json'
11 verbose cwd C:\Users\rruiz\Desktop\test
12 verbose Windows_NT 10.0.18362
13 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "--prefix" "src/Enfoke" "install"
14 verbose node v10.16.3
15 verbose npm  v6.9.0
16 error code ENOLOCAL
17 error Could not install from "" as it does not contain a package.json file.
18 verbose exit [ 1, true ]

Second: rimraf is not recognized as an internal or external command
(Console lines)

> [email protected] cleanup C:\Users\rruiz\Desktop\test\src\Enfoke
> rimraf bin/aot && rimraf wwwroot/*

'rimraf' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] cleanup: `rimraf bin/aot && rimraf wwwroot/*`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] cleanup script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\rruiz\AppData\Roaming\npm-cache\_logs\2019-08-23T16_02_29_910Z-debug.log
INFO! Congratulations, JHipster execution is complete!

(Log debug file)

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   '--prefix',
1 verbose cli   'src/Enfoke',
1 verbose cli   'run',
1 verbose cli   'cleanup' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'precleanup', 'cleanup', 'postcleanup' ]
5 info lifecycle [email protected]~precleanup: [email protected]
6 info lifecycle [email protected]~cleanup: [email protected]
7 verbose lifecycle [email protected]~cleanup: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~cleanup: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\rruiz\Desktop\test\src\Enfoke\node_modules\.bin;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\dotnet\;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Users\rruiz\AppData\Local\Microsoft\WindowsApps;;C:\Users\rruiz\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\rruiz\AppData\Roaming\npm
9 verbose lifecycle [email protected]~cleanup: CWD: C:\Users\rruiz\Desktop\test\src\Enfoke
10 silly lifecycle [email protected]~cleanup: Args: [ '/d /s /c', 'rimraf bin/aot && rimraf wwwroot/*' ]
11 silly lifecycle [email protected]~cleanup: Returned: code: 1  signal: null
12 info lifecycle [email protected]~cleanup: Failed to exec cleanup script
13 verbose stack Error: [email protected] cleanup: `rimraf bin/aot && rimraf wwwroot/*`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
13 verbose stack     at EventEmitter.emit (events.js:198:13)
13 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:198:13)
13 verbose stack     at maybeClose (internal/child_process.js:982:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid [email protected]
15 verbose cwd C:\Users\rruiz\Desktop\test
16 verbose Windows_NT 10.0.18362
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "--prefix" "src/Enfoke" "run" "cleanup"
18 verbose node v10.16.3
19 verbose npm  v6.9.0
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] cleanup: `rimraf bin/aot && rimraf wwwroot/*`
22 error Exit status 1
23 error Failed at the [email protected] cleanup script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Greetings!

Extract JHipsterNet, generate a nuget and use it as dependencies on generated app

Error using entity generator

When running jhipster entity author the cli displays the field and validation questions and then the following error occurs and no entities are generated:

`
INFO! Using JHipster version installed globally
INFO! Executing jhipster:entity autor
INFO! Options: from-cli: true
info Using blueprint generator-jhipster-dotnetcore for entity subgenerator

The entity autor is being created.

[removed questions/answers to improve readability]

events.js:174
throw er; // Unhandled 'error' event
^
Error: The generator-jhipster-dotnetcore blueprint provided is not installed. Please install it using command npm i -g generator-jhipster-dotnetcore.
at Environment.error (C:\Programas\nvm\v10.16.3\node_modules\generator-jhipster\node_modules\yeoman-environment\lib\environment.js:176:40)
at module.exports.error (C:\Programas\nvm\v10.16.3\node_modules\generator-jhipster-dotnetcore\node_modules\generator-jhipster\generators\generator-base.js:1465:18)
at shelljs.exec (C:\Programas\nvm\v10.16.3\node_modules\generator-jhipster-dotnetcore\node_modules\generator-jhipster\generators\generator-base-private.js:839:22)`

The error message tells me to install this generator globally, so I installed it globally again but the same error keeps happening. Is the entity generatior supported?

Send an email when creating an account

In the Java version, when creating an account, a user receives directly in his mailbox a confirmation email. We want to replicate this behavior in the .Net version. Another question then arises, where to store the templates of the mails ?

Fix npm packaging

The npm package was not publish alter build see https://www.npmjs.com/package/generator-jhipster-dotnetcore

Unable to run generated app - build with error: 'certFilename' does not exist in the current context

Unable to run generated app using the latest version.

Program.cs(82,165): error CS0103: The name 'certFilename' does not exist in the current context
Program.cs(82,193): error CS0103: The name 'CertValidationCallback' does not exist in the current context TestDB.csproj

See last commit 54cd2b3

Modify the prompts of the generator

We need to change the prompts to only offer the available features. Another change to be made is when creating an entity, the proposed data types must be C # types instead of Java.

Does not create a .sln file

When I tried to generate a new scaffold, it takes me through the wizard, but at the end, I could not find a .sln file. Without this file, importing into Visual Studio seems incomplete/incorrect.

This blueprint is not compatible with the latest version of JHipster v6.6.0

When I try to generate a sample app with this blueprint I have this error:

ERROR! Error: The installed generator-jhipster-dotnetcore blueprint targets JHipster v>=5.4.0 and is not compatible with this JHipster version. Either update the blueprint or JHipster. You can also disable this check using --skip-checks at your own risk

Installed JHipster version: 6.6.0

Database support

When I try to generate a monolithic .net core application I was not asked for any option to choose database.The code generated is against SQL Lite with Entity framework as the ORM.

Can you please let me know what are the database supported for .net core and also how can we get option to choose the database during code generation.

Entities import - CRUD operation doesn't work

Motivation for or Use Case

Import entities with 'jhipster import-jdl'. The CRUD operations doesn't work. I Have this error

System.InvalidOperationException: Endpoint MyCompany.Controllers.TestEntityController.CreateTestEntity (test-import) contains authorization metadata, but a middleware was not found that supports authorization. Configure your application startup by adding app.UseAuthorization() inside the call to Configure(..) in the application startup code. The call to app.UseAuthorization() must appear between app.UseRouting() and app.UseEndpoints(...). at Microsoft.AspNetCore.Routing.EndpointMiddleware.ThrowMissingAuthMiddlewareException(Endpoint endpoint) at Microsoft.AspNetCore.Routing.EndpointMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.StaticFiles.DefaultFilesMiddleware.Invoke(HttpContext context) at Hellang.Middleware.ProblemDetails.ProblemDetailsMiddleware.Invoke(HttpContext context)

Reproduce the error

• Generate a new App With blueprint
• mkdir netcore-import && cd netcore-import
• npm link generator-jhipster-dotnetcore
• npm link generator-jhipster
• jhipster -d --blueprint dotnetcore

• Import JDL file: jhipster import-jdl app.jh

`entity TestEntity {
title String required
content String required
date LocalDate required
}

paginate * with pagination
`

• Run APP

dotnet run --verbosity normal --project ./src/TestImport/TestImport.csproj

• Try to list and Add new Entity
  https://localhost:5001/

Suggest a Fix

• Remove @this.UseAuthorization(); from SecurityStartup.cs
• Add @this.UseAuthorization(); to MvcStartup.cs

           @this.UseRouting();
            @this.UseAuthorization();
            @this.UseEndpoints(endpoints =>
            {
                endpoints.MapControllers();
            });

Add Docker deployment support

We would like to add the ability to deploy the generated app to a Docker container and for this we need to write a Dockerfile for the project.

clientApp files in root app folder

files of angular client app (package.json, tsconfig, node_modules etc) exist in main root app together with c# models, controllers ets.
Shuouldn't be moved to clientApp ?

Add frontend tests

Change or not the location of the frontend unit test generation to suit the tree structure of a C# .Net project.
Moreover, by modifying the generation path of the front end, it will certainly be necessary to modify the path of the imports in the unit tests. Similarly, it is necessary to modify the different files necessary for the execution of the tests, for example : the script of the command "npm test" in the file package.json.

Join dotnet foundation

https://github.com/dotnet/foundation/blob/master/guidance/new-projects.md

Check all requirement and ask to join dotnet foundation