DapperLib / DapperLib/DapperAOT

How to obtain generated code without Visual Studio

Open
#155 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
472
Forks
43
Avg merge
1d 4h
Merged PRs (30d)
18

Description

I am trying to use Dapper.AOT on Linux and develop my C# application in Visual Studio Code. I have both the C# and C# Dev Kit extensions installed. While there is a list with Dependencies and Analyzers in VS Code where Dapper.AOT.Analyzers shows up, it cannot be expanded further so I cannot see the generated code.

I am wondering if there is a different way to obtain the generated code, possibly via the dotnet CLI, or if there is an option which could output the generated files during a Debug build.

Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Dapper.AOT.Analyzers behavior in Visual Studio Code and the dotnet CLI/build options mentioned in the report. Determine whether generated code can be viewed or emitted during a Debug build, then document the supported workflow and its expected output.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, vscode
Domain
developer-experience, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.