Can't bind to 'matMenuTriggerFor' since it isn't a known property of 'button'. ("">

Bug, feature request, or proposal:

this is for beta11

What is the expected behavior?

should bind submenu to button

What is the current behavior?

does not do that

What are the steps to reproduce?

try to bind [matMenuTriggerFor]="someSubMenu"

Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U

What is the use-case or motivation for changing an existing behavior?

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Material beta 11

Is there anything else we should know?

[josephperrott]

Can you provide a reproduction of the issue?

Based on the error you are receiving it appears that you are not importing MatMenuModule

[crisbeto]

It looks like you could be on an older Angular version. Can you update to 4.4.3?

I did it fixed the error!

However, now it does not like

import {MatSnackBar} from '@angular/material'

suggestions?

[crisbeto]

What error are you getting?

Module '"path/to/node_modules/@angular/material/material"' has no exported member 'MatSnackBar'.

[crisbeto]

You should be able to import MdSnackBar.

I thought it was called MatSnackBar with the prefix changes

[crisbeto]

We're still in the process of renaming a lot of things. See #7241.

So for the time being, should I be using MdSnackBar?

But my module is MatSnackBarModule?

[crisbeto]

Yes, it is a little confusing but it will be sorted out by the time we hit stable. Your IDEs autocompletion should be able to give you the proper import names.

Okay, is MdSnackBar now considered a service?

I dont understand why an npm package is provided that renames everything to Mat from Md, however this is not stable. This may ruin alot of peoples code.

[axtho]

It does ruin a lot of code. I also though that the tool would grab what is changeable, but it seems that it converted too much (i have similar issues with Modules like mat-option not liking [value] and styles being completely off). There should be a warning about using this service.

[josephperrott]

Closing as the issue was resolved by updating to @angular/angular@4.4.3