? orus casino? bodog? ruleta? luckia? betano? sportium? spin casino? stakes? 3 reyes? 888? lottoland? coolbet? 777 casino? gana777? betfair? bwin? yak casino? ivy casino? oddschecker? red casino? netbet? william hill? vip casino? rey casino? marathonbet? dafabet? sol casino? 1bet? winland? bet777? parimatch? 18bet? 888casino? campobet? mostbet? ganabet? rushbet? betcris? betsson? lucky? novibet? winner? winpot? betmaster? betmexico? cancun? playcity? strendus? pokerstars? codere? caliente? fun88? bbrbet? 1win? 10bet? betway? pin up? spinbet? 7cslot? pickwin? spin bet? mr fortune? w88? pragmatic? gamdom? crasher? jojobet? betmex? bcasino? foliatti? winner mx? bets 10? big bola? bet master? inbet? 7slots? lucky day? m777? mexplay? luckydays? bet caliente? 1x? plinko

Forum


HomeHomePremiumPremiumDevelopmentDevelopmentUnable to locate a controller in Client Centric ModuleUnable to locate a controller in Client Centric Module
Previous
 
Next
New Post
6/30/2015 8:59 AM
 

Hello,

I've been working on learning how WebAPI works based off of the Angular example. I was trying to create a hello world test and I've run into the error "Message":"Unable to locate a controller for http://hhcms.dnndev.me/DesktopModules/ACT/API/claimmaster/test.  Searched in namespaces: DotNetNuclear.Modules.ACT.Services.Controllers" ACT(angular connection test) being my module. I have both mine and the example module on my site and the Angular.Module works but mine doesn't. I've almost mirrored it only removing code I didn't think I needed. Here's my structure: 

app.js:

I've done a lot of research on this but nothing that seemed to fit. I've checked that my dll's are in the bin folder. What I can't figure out is how one module works and another doesn't on the same site... 

ClientCentricServices.cs:

ClaimmasterController.cs:

Thanks.

 
New Post
6/30/2015 10:49 AM
 

Found my issue. I had copy/pasted the RegisterRoutes method and it had the wrong string path for my controller in it. Changed to:

Now I get the response I was looking for:

Btw I messed something else up that caused all api calls (such as the working ones from the example module) to fail as well. I changed EnableServicesFrameworkTracing in my web.config and instead of changing it to 'true' I typed 'trreu' or something along those lines without realizing it. Stupid mistake but I'll mention it in case it helps someone.

Now I'm on to find what else I can mess up today.

Thanks.

 
Previous
 
Next
HomeHomePremiumPremiumDevelopmentDevelopmentUnable to locate a controller in Client Centric ModuleUnable to locate a controller in Client Centric Module



Try FREE
30 days money back guaranteed