While ABP support seems to slack off, check my question. https://support.abp.io/QA/Questions/291/Are-we-supposed-to-fix-your-bugs-in-your-software-that-we-paid-for-Is-this-a-joke It is the fix for your problem, or at least for @mattjoslin's.
Version 3.0.3 - issue with multi tenant setup on a new project with complex solution name (Abc.CoolProject). Here's the fixes to your templates.
Template: Server.AppService.AppService.txt
public virtual async Task<%%entity-name%%Dto> CreateAsync(%%entity-name%%CreateDto input)
...
%%<if:IMultiTenantEntity>%%new%%entity-name%%.TenantId = CurrentTenant.Id;%%</if:IMultiTenantEntity>%%
// ^ there newWaldo is
...
Solution
public virtual async Task<%%entity-name%%Dto> CreateAsync(%%entity-name%%CreateDto input)
...
%%<if:IMultiTenantEntity>%%%%entity-name-camelcase%%.TenantId = CurrentTenant.Id;%%</if:IMultiTenantEntity>%%
// ^ there waldo is
...
Create an object Waldo. Find Waldo. Wait you can't, dotnet build says. There's no "newWaldo" declared in this scope. Hmm, I wonder where that "new" came from.
Template: Frontend.Mvc.Page.CreateModal.cshtml.txt
@page
@using Microsoft.AspNetCore.Mvc.Localization
@using %%only-project-name%%.Localization
//. ^ complex solution name you say? we don't care about that. here, take only the project name because that will surely be enough.
@using Volo.Abp.AspNetCore.Mvc.UI.Bootstrap.TagHelpers.Modal
...
Solution
@page
@using Microsoft.AspNetCore.Mvc.Localization
@using %%solution-namespace%%.Localization
//. ^ complex solution name you say. cool, here's the whole identifier
@using Volo.Abp.AspNetCore.Mvc.UI.Bootstrap.TagHelpers.Modal
...
Template: Frontend.Mvc.Page.EditModal.cshtml.txt
@page
@using Microsoft.AspNetCore.Mvc.Localization
@using %%only-project-name%%.Localization
//. ^ complex solution name you say? we don't care about that. here, take only the project name because that will surely be enough.
@using %%project-name%%.Web.Pages.%%entity-name-plural%%
...
Solution
@page
@using Microsoft.AspNetCore.Mvc.Localization
@using %%solution-namespace%%.Localization
//. ^ complex solution name you say. cool, here's the whole identifier
@using %%project-name%%.Web.Pages.%%entity-name-plural%%
...
Template: Frontend.Mvc.Page.Index.cshtml.txt
...
@using Microsoft.AspNetCore.Mvc.Localization
@using %%only-project-name%%.Localization
//. ^ complex solution name you say? we don't care about that. here, take only the project name because that will surely be enough.
@inject IHtmlLocalizer<%%only-project-name%%Resource> L
...
Solution
...
@using Microsoft.AspNetCore.Mvc.Localization
@using %%solution-namespace%%.Localization
//. ^ complex solution name you say. cool, here's the whole identifier
@inject IHtmlLocalizer<%%only-project-name%%Resource> L
...
How about the fact that my connection string is not used for any new project I create? I always end up with "Server=localhost;Database=<ProjectName>;Trusted_Connection=True;MultipleActiveResultSets=true". How about that? Should I fix that for you as well? Why should I have to change the templates myself when the we already paid a price product that is supposed to be ready for this task. Do you even test your software before you release it?
Do you consider it fair that I am supposed to waste one of my questions that was included in the support package to report bugs? To fix your bugs even? What is this support meant to include? Is it not meant to be a channel through which developers can ask for your advice as to how to implement/integrate your product? How is me being required to spend one of such question to report YOUR bugs accomplishing me integrating your product with whatever software I am meant to develop?