Open RollsChris opened 4 months ago
even the documentation has this for the expected project output:
│ .env
│ .gitignore
│ deployment.debug.template.json
│ deployment.template.json
│
├─.vscode
│ launch.json
│
└─modules
└─filtermodule
│ .gitignore
│ Dockerfile.amd64
│ Dockerfile.amd64.debug
│ Dockerfile.arm32v7
│ Dockerfile.windows-amd64
│ filtermodule.csproj
│ module.json
│ Program.cs
The short answer is that they're trying to remove the need for (at minimum) the various Dockerfiles, since that's an extra maintenance burden for customers that's rarely customized and can usually be provided by built-in or other tools (eg, buildpaks). The problem is that the deployment templating tools don't recognize it yet, so the module just isn't included/built.
ahh ok, a bit annoying. Not sure i like that feature of dotnet publish hiding the Dockerfiles etc. But is what it is
Any news on this? whats the work around?
@RollsChris - In an un-released version of the tool done recently they pinned an old version of the template that performs the generation
Hey, do you know when its being released?
Description
Running "iotedgedev solution init --template csharp" does not generate module.json or Dockerfiles for the example filtermodule.
Expected behavior
I expect to see:
Actual behavior
None of the above exist in the module folder
Steps to Reproduce
Run "iotedgedev solution init --template csharp"
Environment
Default from "iotedgedev "container image