One quick question is there a new feature Leptpn management options coming into
Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)
* **Steps to reproduce the issue**:
create new solution with
Provide us with the following info:
🧐 Hint: If you are using the
* **Template**: microservice
* **Created
Get the leptonx theme source code via
Can you try to log out and log in again with
.
````
No luck
PS C:\Users\antho>
PS C:\Users\antho>
:22 INF] You are running the second generation of the
Hi
I am unable to open
After logging in still cant open
I renewed on 20 November 2024 order number 245545436
The last time that I used
you mentioned that you haven't added custom code for SMTP and are not directly using SmtpClient, the
(Btw, the related module is included in the AdministrationService, where all core
Use MailKit(https://docs.abp.io/en/
Use MailKit(https://docs.abp.io/en/
Use MailKit(https://docs.abp.io/en/
Use MailKit(https://docs.abp.io/en/
Hi,
I've made some adjustments to my architecture as follows:
- I now have an
that should handle authentication.
- Additionally, I've set up another layered
> - Additionally, I've set up another layered
>
> For the microservice solution, I'll use a shared database, and for each layered
**
However, the EventOutbox table does not contain the published message
* **
Hi, you're right, version selection is currently missing in the new
As a workaround, you can use the old CLI and specify a version using the `--old` flag:
```bash
YourProjectName --version --old
```
Note that this uses ABP's old templating system, not the current
It looks like something **very** important was recently removed from
Where is the ability to select which version is used for building code in the new
```ts
// custom-impersonation.service.ts
import { PermissionService } from '@
Upgrading
Hi, the package Volo.Abp.Studio.Extensions.StandardSolutionTemplates is used by
> Hi, the package Volo.Abp.Studio.Extensions.StandardSolutionTemplates is used by
> > > Hi, the package Volo.Abp.Studio.Extensions.StandardSolutionTemplates is used by
Studio, or run an
> > > > Hi, the package Volo.Abp.Studio.Extensions.StandardSolutionTemplates is used by
working example:
```ts
// form-prop-contributors.ts
import { ePropType, FormProp, FormPropList } from '@
[image.png](/QA/files/3a18b82f84a23f6102d74c053411d802.png)
i have the
Hello,
Yes, I have tested this with version 9.0 of
* **
```
import { ePropType, FormProp, FormPropList } from '@
but this process takes a lot of time or it cannot perform the action:
https://github.com/abpframework/
/modules/openiddict/src/Volo.Abp.OpenIddict.Domain/Volo/
And it initialize [AbpIdentityModelModule](https://github.com/abpframework/
/src/Volo.Abp.IdentityModel/Volo/
https://github.com/abpframework/
a Directory.Packages.props file to manage all NuGet package versions, and I’ve confirmed that every
a Directory.Packages.props file to manage all NuGet package versions, and I’ve confirmed that every
Volo.Abp.AbpApplicationBase.ConfigureServices()
*
* **Steps to reproduce the issue**
Hi,
I recently updated from
8.3.2 to
To troubleshoot, I’ve already tried the following steps:
- Ran `
implemented by checking the DLL
I came across a related GitHub issue: https://github.com/abpframework/
Hi,
I've generated a new solution with
> Hi,
>
> I've generated a new solution with
Run the same following command to regenerate the proxy with the correct module name:
`
So, the problem was in the generated-proxy.json, that was actually generated by
However, in cases where it persists, it may be helpful to verify the generation process within
- **Template**: microservice
- **Created
following issue when trying to generate proxies for angular:
PS D:\repos\projects\abc\apps\angular>
employeeQuery --target employee-query-service
[10:18:53 INF] You are running the second generation of the
Uninstall and install
Uninstall and install
Uninstall and install
–
Provide us with the following info:
🧐 Hint: If you are using the
* **
. **>=9.0.5** will fix the problem, see https://github.com/abpframework/
Or is this problem likely to be fixed in a future release of
- **Template**: app
- **Created
* **
* **
Usually I would update via Upgraade
I just changed to another way:
or has a different signature in the version that is now being used (likely the one compatible with
versions:** (The most common cause for such errors after an upgrade is having inconsistent versions of
Please ensure that all
png)
The event log shows:
[Event ID: 1035]
Application '/LM/W3SVC/2/ROOT' with physical root 'C:\
WebApplicationBuilder builder\, Action\`1 optionsAction\)
at GiftCardIssuance.Blazor.Program.Main(String[] args) in C:\
GiftCardIssuance.Blazor\Program.cs:line 37
[Event ID: 1007]
Application '/LM/W3SVC/2/ROOT' with physical root 'C:\
