Unable to build solution with Rider

OS: Windows 10
IDE: Rider version 2022.3.1
Package verision: 2.9.4-preview.2

Hello!
I'm switching from deprecated Tinkoff package Nunit.Allure to your package Allure.Nunit version 2.9.4-preview.2.
Upgrading to this package caused an error in my Rider, and I'm unable to build solution with it.

Because it uses AspectInjector inside - build fails with `Aspect Injector processing has failed. See other errors`
During a little dig into - found that there is no AspectInjector.exe inside build folder - `.nuget\packages\aspectinjector\2.8.1\build\_bin\win-x64` .

Tried to download .exe from nuget, added to build folder.

Then build fails with
```
aspectinjector\2.8.1\buildTransitive\netstandard2.0\AspectInjector.targets(102,5): error MSB4062: The "Microsoft.Build.Tasks.GetFrameworkSdkPath" task could not be loaded from the assembly Microsoft.Build.Tasks.Co
re, Version=[15.1.0.0](http://15.1.0.0/), Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a. Confirm that the declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft
.Build.Framework.ITask. [D:\Git\unite-services-tests\src\APITests\APITests.csproj]
```

Tried to add Microsoft.Build.Tasks.Core according version - but there are no results, and error stays same.

Did you faced same issue? If you need any additional information, feel free to contact me

Start by reproducing the Rider build failure on Windows 10 with Allure.Nunit 2.9.4-preview.2 and AspectInjector 2.8.1. Inspect the referenced AspectInjector.targets file, its build\_bin\win-x64 directory, and the APITests.csproj error context. Done means the solution builds in Rider without manually adding AspectInjector.exe and without the MSB4062 error.

Written by the indexing model from the issue text.