-
-
Notifications
You must be signed in to change notification settings - Fork 316
Update Reverse Engineering wiki page #290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Agree, this is something I need to do! If you could make a screenshot / text description of your folder layout, I can try to help (and get the first entry in the wiki update drafted at the same time!) |
assuming that you are running EF Core Power Tools in the Aldente.Journal.Domain, the following values should work: Namespace: Aldente.Journal (and thanks for dog-fooding!) |
@jespersh did you try this out? |
Back in the work seat and tried this out. For the most part it worked as expected. <Project Sdk="Microsoft.NET.Sdk">
...
<ItemGroup>
<Compile Include="..\Aldente.Journal.Persistence\AldenteDbContext.cs" Link="AldenteDbContext.cs" />
</ItemGroup>
...
</Project> This is the only thing I'd even consider an error. Knowing what I know today, then I'd move the generated What I am wondering about is this:
...
public AldenteDbContext(ISecrets secrets)
{
_secrets = secrets;
}
... Maybe a followup issue on this would be appropriate |
1: What is your target framework in Aldente.Journal.Domain.csproj ? 2: The constructor issue - is that something that just happended now? Otherwise it sounds like a feature request, so feel free to post a new issue. 3: "unhandled mysql datatypes (zerofill)." - is that a MySQL provider issue/bug? |
That way I always ended up a DbContext I was in control of because I was always cut/pasting the newly reverse engineered parts.
|
1: Looks like I should only be doing this for .NET Framework projects: https://github.com/ErikEJ/EFCorePowerTools/blob/master/src/GUI/EFCorePowerTools/Handlers/ReverseEngineerHandler.cs#L247 2: That is not how you are supposed to use it !! 😄
|
I'll try and throw together a small example with my usage on how I intend to use it if I had to rework my persistence layer |
Don't spend too much time on it, I am not planning to make any changes to how the DbContext class is layed out, I just reuse the EF Core implementation. |
It'll also mostly be for my own sake to see what I've learned about working with EFCore. That others will benefit for it is a bonus 😄 |
Attempted to fix in latest daily build |
Erik, this is to let you know I love your tool. I am trying out the .NET 5.0 features and I don't know how to tell the tool to move all of the Entity Configuration files to a specified directory and the same for the Result files for Stored Procedures. For the domain entities and dbContext, they are easy to do. |
@alexle1965 Please create new issues for feature suggestions or bug reports. The Entity Configuration proposal is a duplicate of #423 . For the Stored Procedure result files, where would you like them to be placed? - if this matters to you, please create a new feature suggestion with a proposal. |
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->Hi Erik, Once again, thank you for the wonderful tool and I use it all the times. My new project is to migrate a legacy application from Webforms with a lot of stored procedures to .NET Core 3.1.x. I used your tool to do the reverse engineering and all the SProc are generated for me. My issue is that I do not know to invoke the auto-generated stored procedures from the controllers or how they are used. I read through the documentation but I do not see anything about using the SP. Would you be kind enough to provide me guidance of where to go for the documentation? Thank you very much. I love your tool. Alex Le316-371-8179 (mobile)“Be more concerned with your character then your reputation…” From: Erik Ejlskov JensenSent: Friday, November 13, 2020 12:48 AMTo: ErikEJ/EFCorePowerToolsCc: Alex Le; MentionSubject: Re: [ErikEJ/EFCorePowerTools] Update Reverse Engineering wiki page (#290) @alexle1965 Please create new issues for feature suggestions or bug reports.The Entity Configuration proposal is a duplicate of #423 .For the Stored Procedure result files, where would you like them to be placed? - if this matters to you, please create a new feature suggestion with a proposal.—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.
|
@alexle1965 It is documented here: https://github.com/ErikEJ/EFCorePowerTools/wiki/Reverse-Engineering#sql-server-stored-procedures - wonder why you were not able to find it? |
Erik,
Thank you very much. I clicked on the documentation link in Github as well.
Alex Le
316-371-8179
Sent from BlueMail
…On Feb 9, 2021, 8:13 AM, at 8:13 AM, Erik Ejlskov Jensen ***@***.***> wrote:
@alexle1965 It is documented here:
https://github.com/ErikEJ/EFCorePowerTools/wiki/Reverse-Engineering#sql-server-stored-procedures
- wonder why you were not able to find it?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#290 (comment)
|
Looked at https://github.com/ErikEJ/EFCorePowerTools/wiki/Reverse-Engineering as I just noticed the new dialog:

And I got a bit overwhelmed by all the options to be honest.
I think some screenshots of Solution Explorer with all the different options could help people (me) in the wiki.
My solution has a ***.Persistence project with DbContext and a ***.Domain project with entities. So I couldn't figure out this full control thing just by looking at it #197 (comment)
The text was updated successfully, but these errors were encountered: