-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A namespace cannot directly contain members such as fields or methods #79
Comments
There seems to be missing some relevant information from your bug report. What has been installed? |
Hmm, I'll try this out. By |
This is because the custom template of Workaround for now ( @bdelaney and @MilkyWayJoe ) is to simply clear the Custom Tool in the file property window. This is a valid bug report though - afaik the Custom Tool property was automatically cleared in earlier releases. |
Correction: I fixed this as part of #29, but that is pull request is still open. @erichexter or @MisterJames please consider merging #29. |
Im traveling and will be iffline foe the next two weeks. James can you apply the pr?
|
@serra yeah, I wrote it incorrectly here, but I've actually installed |
This error on build out of the Nuget Templates package, ControllerWithContext.tt showing a .cs output and that is source of error.
Used latest Nuget packages (all 3) in an MVC4 project, Empty template.
This occurred after the recommended project close and reopen.
Deleted the ControllerWithContext.cs output file and build works.
After installing the 3 NuGet packages, Package Manager GUI shows 4 packages, all are 1.0.90 version. Makes sense as I look at packages.config file and note what has been installed:
Looking forward to checking it out further.
The text was updated successfully, but these errors were encountered: