found the problem, we had a wrong path indeed, so the server action was not found for node and for asp.net we had the wrong extension ![]()
will fix it with an inline update on monday ![]()
time to watch some football
now and have some beers
![]()
found the problem, we had a wrong path indeed, so the server action was not found for node and for asp.net we had the wrong extension ![]()
will fix it with an inline update on monday ![]()
time to watch some football
now and have some beers
![]()