Base solution for your next web application

Activities of "robertfitch"

Hi,

Thanks for the reference to eventlog.xml, which I wasn't aware of. There, I was able to see the exception details. I am using NetMQ to send events to other processes and apparently there is a problem loading the NetMQ assembly, so I will look into that.

Cheers!

Please note that I am referring to service interfaces in the Application project, not controllers in the WebApi project.

I am still having no success. Inserting: Configuration.Modules.AbpWebApi().HttpConfiguration.MapHttpAttributeRoutes(); as mentioned above did not help.

Maybe this information is useful: It is an ASP.NET Zero application which we purchased from you.

We would like the services we add to become more REST-oriented, which is why the Route-Attribute is important to us.

Thanks and regards, Robert

oops, ignore my comment about camelCase. Of course it is the javascript-method which gets renamed to camelCase, not the url path!

Thanks, but this is not working yet. The only place I find which has access to HttpConfiguration is in Initialize() of the WebApiModule. I have added "MapHttpAttributeRoutes()" there:

        Configuration.Modules.AbpWebApi().HttpConfiguration.MapHttpAttributeRoutes();

        //Automatically creates Web API controllers for all application services of the application
        DynamicApiControllerBuilder
            .ForAll<IApplicationService>(typeof(CosmosMoonApplicationModule).Assembly, "app")
            .Build();

But the api (using e.g. Postman) still only responds to "/GetContacts", not "/get_contacts". I also see this reflected in the generated service proxy:

serviceNamespace.getContacts = function(ajaxParams) {
    return abp.ajax($.extend({
        url: abp.appPath + 'api/services/app/contact/GetContacts',
        type: 'GET',
        data: {}
    }, ajaxParams));
};

Note also that there is no camelCase conversion as claimed. Is there a better place to call "MapHttpAttributeRoutes()" ?

thanks...

Thanks for your quick help, the workaround is now running! regards

Showing 1 to 6 of 6 entries