Activities of "paulbackhouse"

I managed to complete the upgrade to 0.8.0.3 and finally resolve the EF missing cmdlet problem - fix by the way is rollback EF to 6.1.1 and everything works perfectly with latest ABP stuff :) cmds are back (i.e add-migrations)

anyway, FYI. In the migration script, the Table "AbpUserLoginAttempts" tries to create and index on TenancyName, UserNameOrEmailAddress and Result. It will fail in MySql due to max length exceeding in the index (ref: <a class="postlink" href="http://stackoverflow.com/questions/8746207/1071-specified-key-was-too-long-max-key-length-is-1000-bytes">http://stackoverflow.com/questions/8746 ... 1000-bytes</a>)

To fix, change the length of the column UserNameOrEmailAddress from varchar(256) to varchar(255). 255 is the max default index capacity.

In case you want to put that in next release for MySql users

I have created my menus and all working fine.

In Layout.js abp.nav.menus.MainMenu contains the menu as described.

However, I have some customDataand order requirements. I set some values for order against each MenuItemDefinition object and on one item has set customData.

BUT, abp.nav.menus.MainMenu is no reflecting these new properties at all. They don't come through via the API at all.

My question is why not? I have literally added these properties in the definition but they are not brought through as properties in the JS object.

Example:

.AddItem(
                    new MenuItemDefinition(
                        "Settings",
                        new LocalizableString("Settings", imanageConsts.LocalizationSourceName),
                        url: "/settings/#/",
                        icon: "fa fa-cogs",
                        order: 7,
                        customData: new Dictionary<string, object>() {{ "someKey", new string[] { "soemValue1", "someValue2", "someValue3" } }}
                        )
                );

Hi,

By default all methods are HTTP POST (no problem with this) but I would control over setting methods which should be HTTPGET, HTTPDELETE etc...

I have read you documentation here: [http://aspnetboilerplate.com/Pages/Documents/Dynamic-Web-API]) and followed it. I specifically want to use the interface approach where I can define the attributes on the methods I want to have different HTTP Request methods.

However, it does not work, the calls are always being set to POST.

I then tried changing the naming convension during the initialisation of the dynamic controller api using WithConventionalVerbs but this method isn't even available to me, it it not my preferred route either.

I then tried manually setting the verb against the method in the dynamic controller (which I really don't want to have to do) using this code:

DynamicApiControllerBuilder
    .For<IClientService>("app/ClientService")
    .ForMethod("Get").WithVerb(HttpVerb.Get)
    .Build();

Again, no joy.

So....then I thought, fine, I will live for post until I can find a solution here (i.e. post here) BUT my method is:

public ClientDTO Get(long id) { ... }

This doesn't work in POST when the expected parameter type is anything other than an object - even though the value being passed is 7 and you can direct cast to long once in the method... I am very confused - this cannot be default behaviour can it?

What am I missing here, please help, frustrated and struggling - it is far easier in WebAPIControllers :s

Regards

Paul