>>>I commented out ErrorView, WarningView, etc. methods and got it to run.
>>
>>Hardly a fix :-}
>>
>
>Agree. The consultants suggests to just comment that particular line instead
>
>routes.MapMvcAttributeRoutes();

Are you using routing attributes in your controllers? You didn't show any but if there are than you need that line.


>
>so I may try that approach.
>
>> >Now it doesn't show the view and shows this new error in Dev. Tools:
>>>
>>>

>>> Uncaught Error: [$injector:modulerr] Failed to instantiate module sysMgrApp due to:
>>>Error: [$injector:modulerr] Failed to instantiate module ui.bootstrap due to:
>>>Error: [$injector:nomod] Module 'ui.bootstrap' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.
>>>http://errors.angularjs.org/1.3.13/$injector/nomod?p0=ui.bootstrap
>>>

>>
>>Pretty self-explanatory. Somewhere you have a dependency on ui.bootstrap but it's not being loaded to the browser.
>
>Strange, I thought I already updated that message. I fixed that error first by loading the angular-ui bootstrap as the original files got deleted. I then got other problems. The reason for the mess is that we're using macadminetheme which incorporates jquery and bootstrap into it and not the very latest. So, later that night I restored these 2 missing files and got the project to run almost without errors except for the new error about number formatting pointing to our custom directives. I left it at that as we probably will upgrade macadminetheme as well first (even though it's not very up to date with its components).