Developer forum

Hi Hans

Yes.

The problem is related to this line in the exception:

'Services' is an ambigous reference between 'Dynamicweb.Content.Services' and 'Dynamicweb.Services'

The problem comes from Dynamicweb 9.15 which contains changes to the API that instructs where they will be when upgrading to Dynamicweb 10 - causing the Razor compiler to be confused wether to use the new or the old Services class (9.15 contains both locations). Usually not a problem.

In Rapido though, this happens because some templates contains both of the namespaces where these services are:

@using Dynamicweb
@using Dynamicweb.Content

This comes from the includes.

The easy fix to this (untested as of now) is to add this in the top of templates causing the issue:

@using Services = Dynamicweb.Content.Services;

or

@using Services = Dynamicweb.Services;

From your exception I can see you need to add it here:

Sorry about the inconvenience.