Activities of "aaron"

1. Dependency warnings Can you first try to run VS as administrator, then open the project and see if that resolves the warnings? Otherwise, here's a workaround: https://github.com/aspnetboilerplate/aspnetboilerplate/issues/2493#issuecomment-331009271

Please let me know if the first method works for you.

2. Styling Can you check if there are errors in the F12 console?

Can you show your test case?

Here is an example that sends a parameter to a stored procedure to delete a user:

public async Task DeleteUser(EntityDto input)
{
   await Context.Database.ExecuteSqlCommandAsync(
       "EXEC DeleteUserById @id",
       default(CancellationToken),
       new SqlParameter("id", input.Id)
   );
}

Using Stored Procedure, User Defined Function and Views in a Custom Repository with ASP.NET Boilerplate: https://www.codeproject.com/Articles/1199648/Using-Stored-Procedure-User-Defined-Function-and-V

Source code is published on Github: https://github.com/aspnetboilerplate/aspnetboilerplate-samples/tree/master/StoredProcedureDemo

You need to add security definitions and requirements, or authentication helpers.

Add swagger security definitions and requirements: module-zero-core-template/pull/108

• The 'proper' way.

• If you have a way of getting accessToken, e.g. login with Postman.

• If you are running IdentityServer, you can configure oauth2 login. Add swagger authentication helpers: module-zero-core-template/pull/87

• The 'helper' way.

• If you are running Swagger on the same site as your MVC application - supports csrfToken.

• If you want an in-browser solution to login and manage the accessToken in the site cookie.

• If you want to support multiple behaviors - also supports accessToken from Postman, etc. You can adopt either (or both). This may come in future releases.

That's actually the signInToken.

As @ismcagdas mentioned, you can create another module in your public app. It may accept signInToken. You can use the approach in src/MyCompanyName.AbpZeroTemplate.Web.Public/Controllers/AccountController.cs#L55-L61.

Can you check that you are using v2.1.1/v3.0.0 of Castle.Windsor.MsDependencyInjection nuget package?

Hi, can you try deleting the bin folder in the Web project and rebuilding the solution?

ComponentRegistration.UsingFactoryMethod was modified in Castle.Windsor v4.0.0 and WindsorRegistrationHelper.cs is interpreted as passing in a Converter instead of Func. This might have to be fixed on Volosoft's side, so hang on.

Can you try if removing both references allows you to:

• deploy with azure, and
• build locally?

Install in Core project (EntityFrameworkCore project depends on Core project).