To make a feasible test, you need to add the following features to your new test project to align with the ABP project:
note that I created the list off the top of my head and there'll be other middlewares that process on an HTTP request. once you add these middleware it'll probably be the same.
Here are my answers:
Per example I couldn't search for a string like "Unknown client or client not enabled" or "Bad Request" ... All found results are only single word..
Elastic Search is being used as the search engine. We can configure it to find exact matches as well.
Your forum is also slow.. if i try to open the open issues for 4.4.2 it take a really lot time to display it.
Other question URLs are not slow. Some issues have very long conversation like this one and it gets some time to load. We can improve this by adding Infinite Scrolling or Pagination.
If you Post a message , there should be a preview button
There's a preview button on top of the box.
Also code highlighting would be great and better to read.
This feature is already included in the next milestone.
We are here developers.. so it should be able to open a post and attach some code samples. but its not possible to attach any files. you could also allow uploading up to 30mb code samples .. so it would be easier to exchange with you.
If you would like to share a code sample you can share it via GitHub link. 30 MB code sample is a big file when you think it only contains text.
You should at least provide a Link like the other above in the forum Howto search here....
Search is simple, it only searches the keywords in the question text and title. We'll improve it.
It would be great if you could find a better way for use... like Github or whateveer forum..
Didn't understand this statement.
I find it not suitable that there is no FeedBack Portal for the commcercial Part of ABP like here for Example : https://www.syncfusion.com/feedback
This forum is for bug reports, feedback and suggestion. We refund your question credit, if you report a bug or suggestion. You can also check out https://support.abp.io/QA/Questions/954/We-are-listening-to-you
I would like to post in such a forum especially Feature Requests for all your modules, for abp suite for example. You could see which feature Request gains the mosts Interest and we could follow better that requests. I did try posting such requests in the past in github, but it seems not to work good for me..
Yes this is possible. I'll create a feature request for this.
I wrote this here and opened a ticket because coudn't find better informations from you.. This is not customer oriented. I hope you are interested in our input as customer how to get things better here for us.
Thank you! Your question credit has been refunded.
Suite works with 4.4.X without any issues (even with unified DbContexts explained here). The issue you face is; You added your project before this migration and migrated your project manually. But Suite still doesn't know the correct DbContext file path. To correct this open Suite and remove the solution (this will not delete any of your entities and metada of your entities) And then add the same solution again. This time Suite will find the correct DbContext file.
Alternatively, you can open the Suite database from %UserProfile%\.abp\suite\appsettings.json
and fix the following nodes:
DbContextModelCreatingExtensionsFilePath
MigrationsMigrationsDbContext
Issue:
The issue raises after .NET 6 migration. There's a new feature that blocks multiple files to be copied to the same target directory with the same file name. See https://docs.microsoft.com/en-us/dotnet/core/compatibility/sdk/6.0/duplicate-files-in-output
Solution #1 (workaround):
You can add the following build property to all your publishable (*.Web) projects' *.csproj
files.
This property will bypass this check and works as the previous .NET5.
<ErrorOnDuplicatePublishOutputFiles>false</ErrorOnDuplicatePublishOutputFiles>
Solution #2:
Exlude the problemmatic files to be copied to the output folder.
In this example we'll exclude these files: compilerconfig.json
and package.json
Add the following lines to your common.props
(located in the root directory of your solution)
<Content Remove="compilerconfig.json;package.json"/>
<None Include="compilerconfig.json;package.json">
<ExcludeFromSingleFile>true</ExcludeFromSingleFile>
<CopyToPublishDirectory>Never</CopyToPublishDirectory>
</None>
Only the following cases enforces license check
Development
I see that you already updated your ASPNETCORE Environment variable. There's only 1 possibility left, you are attached a debugger to the project. Are you running the container from Visual Studio with debugger attached? To check this add the following command to your Program
Console.WriteLine("DebuggerAttached: " + System.Diagnostics.Debugger.IsAttached);
Did you add the Volo.Saas
module with source-code? If yes, did you compile it in debug mode?
Public classes are not being obfuscated. Those are private and protected ones which you'll not use.
a
a
is it possible to share your project with us? info@abp.io
and be aware that the first run of DI takes the longest time (initialization of services) the consistent test can be done after 2nd or 3rd request.