EF doesn't allow us to order by a column that we're not fetching from database. So we need to provide a developer friendly message instead of EF's default exception message for this scenario.

For what reason did you add another layer on top of topshelf for windows service development. any good reason

Description

As a frequent user of the Trendyol online shopping app, I suggest adding a shuffle button to enhance the user experience.

Problem

As a user, I often get bored after spending a significant amount of time in the app and sorting through items based on the same categories. The current recommendation system is helpful, but it can become repetitive and limit my ability to discover new products.

Solution

By adding a shuffle button, users would be able to browse through a wider range of products and discover new items that they might not have found otherwise. The shuffle button would allow the app to render new items on the page based on the same recommendation system, enhancing the overall shopping experience.

Benefits

The addition of a shuffle button would encourage users to spend more time browsing and purchasing, ultimately increasing user engagement and driving sales. I believe that this feature would be a valuable addition to the Trendyol app and would greatly benefit users like me.

Technical Details

To implement this feature, we can create a new button component and add it to the app's main screen. When the user clicks on the button, it would trigger a function that sends a request to the server to fetch new items based on the same recommendation system. The response would be returned in the form of a JSON object, which would then be used to update the UI and render new items on the page.

The implementation would require changes to both the front-end and back-end components of the app.

Steps to Implement

1. Create a new button component in the app's main screen.
2. Define a function to handle the button click event.
3. Send a request to the server to fetch new items based on the same recommendation system.
4. Receive the response in the form of a JSON object.
5. Update the UI and render new items on the page.
6. Test the feature thoroughly to ensure it works as intended.
7. Deploy the feature to production once testing is complete.

Thank you for your time and consideration.

There is a problem in Trendyol.App.EntityFramework.DataContextBase.HandleAuditableEntities method causing NullReferenceException when we use EF's code first migrations from package manager console.

Example stacktrace:
System.NullReferenceException: Object reference not set to an instance of an object.
at Trendyol.App.EntityFramework.DataContextBase.HandleAuditableEntities()
at Trendyol.App.EntityFramework.DataContextBase.SaveChanges()
at Riddick.Migrations.Configuration.AddUsers(DataContext context) in C:\Workspace\Riddick\Riddick\Migrations\Configuration.cs:line 52
at Riddick.Migrations.Configuration.Seed(DataContext context) in C:\Workspace\Riddick\Riddick\Migrations\Configuration.cs:line 23
at System.Data.Entity.Migrations.DbMigrationsConfiguration1.OnSeed(DbContext context) at System.Data.Entity.Migrations.DbMigrator.SeedDatabase() at System.Data.Entity.Migrations.Infrastructure.MigratorLoggingDecorator.SeedDatabase() at System.Data.Entity.Migrations.DbMigrator.Upgrade(IEnumerable1 pendingMigrations, String targetMigrationId, String lastMigrationId)
at System.Data.Entity.Migrations.Infrastructure.MigratorLoggingDecorator.Upgrade(IEnumerable`1 pendingMigrations, String targetMigrationId, String lastMigrationId)
at System.Data.Entity.Migrations.DbMigrator.UpdateInternal(String targetMigration)
at System.Data.Entity.Migrations.DbMigrator.<>c__DisplayClassc.b__b()
at System.Data.Entity.Migrations.DbMigrator.EnsureDatabaseExists(Action mustSucceedToKeepDatabase)
at System.Data.Entity.Migrations.Infrastructure.MigratorBase.EnsureDatabaseExists(Action mustSucceedToKeepDatabase)
at System.Data.Entity.Migrations.DbMigrator.Update(String targetMigration)
at System.Data.Entity.Migrations.Infrastructure.MigratorBase.Update(String targetMigration)
at System.Data.Entity.Migrations.Design.ToolingFacade.UpdateRunner.Run()
at System.AppDomain.DoCallBack(CrossAppDomainDelegate callBackDelegate)
at System.AppDomain.DoCallBack(CrossAppDomainDelegate callBackDelegate)
at System.Data.Entity.Migrations.Design.ToolingFacade.Run(BaseRunner runner)
at System.Data.Entity.Migrations.Design.ToolingFacade.Update(String targetMigration, Boolean force)
at System.Data.Entity.Migrations.UpdateDatabaseCommand.<>c__DisplayClass2.<.ctor>b__0()
at System.Data.Entity.Migrations.MigrationsDomainCommand.Execute(Action command)